Repository navigation
Conversation
|
Related issue: #7843 |
|
Tested last night on my scattered builds and it worked. I was dreading to share the build so it made my life much more easier. I think it's a great feature to have. One thing I noticed is it overwrites the existing layouts if imported one has layouts with matching name. For example: It might be nice to tell user that this will overwrite matching layouts, or letting the user pick which layout to import since the name suggests only one layout will be imported. |
That's a good point. I had not considered what happened if you imported a build with existing loadouts. I'll see what I can do, the picker makes sense to me. |
- Loadouts with matching names are not overwritten anymore. New loadouts are renamed with a (1) suffix - New popup allows the user to selective import loadouts from the target build

Adds the ability to import a build (from a code or link) into a new Loadout, without erasing existing data from the current build. If the imported build has existing loadouts, a popup will allow the user to choose which to import. Loadouts whose names clash with an existing loadout will be renamed by adding a suffix to its name
This PR also fixes a bug where loadouts using older passive tree versions were not automatically selected in the dropdown because their version-prefixed display names (e.g "[3.28] Day 1") did not match the raw tree titles ("Day 1").
Description of the problem being solved:
I often want to follow existing builds from poe.ninja. To do this, I import the build snapshots in some key moments (e.g day 1, day 3, week 1, and so on). Currently, consolidating all this into the same POB was very annoying, requiring manual work.
This PR aims to add a way to solve this by allowing the user to import a build into a new loadout, without touching the existing build data.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
Before screenshot:
After screenshot:
Importing a build with no existing loadouts (e.g from pob.ninja)

Importing a build with existing loadouts now allows the user to choose which loadouts to import

The popup also warns about existing loadouts with conflicting names
