Search in Classifieds
Search in Groups
Search in Polls
Search in Members
Search in Members
Search in News
Search in Polls
Search in Businesses
Search in Contests
Search in Events
Search in Music Albums
Search in Music Songs
Search in Quotes
Search in Site Team
Search in Jobs
Search in Products
Search in Products
To continue using the site you need to read the revised version and agree to the policies
Informativa ai sensi degli articoli 13 e 14 del Regolamento UE n. 2016/679 (“GDPR”) Ultimo aggiornamento: 06.03.2019.
Finalità del trattamento Base giuridica del trattamento
To continue using the site you need to read the revised version and agree to the policies
Informativa ai sensi degli articoli 13 e 14 del Regolamento UE n. 2016/679 (“GDPR”) Ultimo aggiornamento: 06.03.2019.
Finalità del trattamento Base giuridica del trattamento
To continue using the site you need to read the revised version and agree to the policies
Informativa ai sensi degli articoli 13 e 14 del Regolamento UE n. 2016/679 (“GDPR”) Ultimo aggiornamento: 06.03.2019.
Finalità del trattamento Base giuridica del trattamento
To continue using the site you need to read the revised version and agree to the policies
Informativa ai sensi degli articoli 13 e 14 del Regolamento UE n. 2016/679 (“GDPR”) Ultimo aggiornamento: 06.03.2019.
Finalità del trattamento Base giuridica del trattamento
4 minutes, 38 seconds
-92 Views 0 Comments 0 Likes 0 Reviews
Patch 0.5.5h gives Path of Exile 2 players a reason to recheck Expedition Runeforging recipes after moving characters between league types. If an SSF character had already unlocked a recipe, reviewing its progression alongside your POE 2 Orbs can help separate a genuine recipe issue from a normal crafting requirement.
The update focuses on recipe unlocks that could disappear during Hardcore-to-Softcore or Solo Self-Found-to-non-SSF migration outside the Runes of Aldur leagues. The published change has a specific scope, so careful records are essential when comparing the original character with the destination version.
Record the Migration Before Checking Recipes
Start by writing down the source league and destination league exactly as shown in the character selection or migration interface. Include whether the move involved Hardcore, Softcore, SSF, or a combination of those modes. Also record the migration option selected, since different transfers can affect which character data is carried forward.
Next, note the complete name of the Expedition Runeforging recipe that was available before the transfer. Capture the character level, the relevant Expedition progress, and the date or approximate time of the migration. These details make the comparison more useful if several characters share similar progression.
Compare the Destination Character
Log into the destination character and open the Expedition Runeforging interface. Search for the recorded recipe rather than relying on its position in the list. A recipe that was previously available should appear as unlocked if the migration falls within the situation addressed by patch 0.5.5h.
If the recipe is missing, check whether the destination character is using the expected league state and whether the migration completed fully. Reloading the character selection screen can also help confirm that the current data is not from an interrupted session. Avoid spending materials until the recipe status is clear.
Screenshot Template
Use one screenshot showing the source character and league, followed by a second image showing the same recipe on the destination character. Add a short note with these fields: Source league, destination league, migration option, recipe name, source status, destination status, and approximate migration date.
Separate Missing Data From Normal Progression
Not every unavailable recipe indicates a migration problem. Some recipes remain locked because the original requirement was never completed, even if the character had collected related materials or had seen the recipe listed elsewhere.
For example, a character may have completed an Expedition encounter but still lack the required Runeforging milestone. In that case, the recipe should remain locked after migration. Record the missing requirement separately and compare it with the original character's actual unlock state before reporting a discrepancy.
What the Published Fix Does Not Confirm
Patch 0.5.5h does not automatically prove that every earlier migration has been repaired. Its wording is limited to certain recipe unlock losses involving the stated transfer paths and leagues outside Runes of Aldur. Older cases may still require individual verification.
Players checking a previous migration should preserve screenshots, avoid deleting the destination character, and compare several recipes when possible. A consistent pattern is stronger evidence than one missing entry, especially when the recipe's requirement history is uncertain.
The most reliable check is a side-by-side record of the original unlock, the migration details, and the destination recipe state. When preparing a report, keep your POE 2 Orbs for sale purchases and other unrelated account activity separate from the recipe evidence so the progression history remains easy to evaluate.
As a Free User, you can earn Credits and try out all the features before upgrading to the next level.
We are a secure Business Community with a growing number of active companies; we are ready to assist you with any needs you may have, share the latest updates, and help you expand your network of direct contacts.

Share this page with your family and friends.