Path of Building: Offline Build Planner [v1.4.71]

"

Mr_Cee wrote:

"

XSLDX wrote:

too bad the new 3.4 tree destroyed all previous passive trees and I can't find a way to rcover or export the trees even though the data is still there...

Can't you implement a way to load the passive tree in a specified version just as the original on this page does? Or at least a way to export the tree data from a saved build for viewing elsewhere?

+1

It would be really helpful if 'old' passive trees could be 'frozen' with their appropriate legacy tree. (only other idea to solve this would be a selection for the targetted POE patch state, like it was on the edge of 3.0 where we could choose between 2 - but it would greatly increase the amount of space and data needed for all different skilltree states).

The 'best' (only?) actual way to handle this is to use the 'old' POESkillTree tool from Emmitt where you can keep multiple instances with each needed tree edition data. I think there even was a way to handle older trees inside one of the never versions, but I cant figure it out yet (not used for a long time now). I also never tried the handling of item data for builds with it, and it seems to be much less informative about gem data etc.

"

XSLDX wrote:

"

Mr_Cee wrote:

"

XSLDX wrote:

too bad the new 3.4 tree destroyed all previous passive trees and I can't find a way to rcover or export the trees even though the data is still there...

Can't you implement a way to load the passive tree in a specified version just as the original on this page does? Or at least a way to export the tree data from a saved build for viewing elsewhere?

+1

It would be really helpful if 'old' passive trees could be 'frozen' with their appropriate legacy tree. (only other idea to solve this would be a selection for the targetted POE patch state, like it was on the edge of 3.0 where we could choose between 2 - but it would greatly increase the amount of space and data needed for all different skilltree states).

The 'best' (only?) actual way to handle this is to use the 'old' POESkillTree tool from Emmitt where you can keep multiple instances with each needed tree edition data. I think there even was a way to handle older trees inside one of the never versions, but I cant figure it out yet (not used for a long time now). I also never tried the handling of item data for builds with it, and it seems to be much less informative about gem data etc.

Yes, multiple versions would take a lot more space but there is another solution. It is already a built in functionality, it just doesn't work in the right order. When you load up a build tree you have the option to export the treelink for this website(that already does support old trees), but loading an old build already turns the full tree data that is stored in the file into a 2node templar... It screws up the tree before you can access the export function. If you just could export the tree directly without opening the build you would be able to retrieve the full legacy passive tree to be viewed in the offical webtree. We don't need all the cool dps calculations for a legacy tree, all we want is to know where that templar went after the first two points so we can make a new tree that looks just like it, maybe one or two points off the original path, but compatible with the new game version. And then we can unpack those dps calculations again so that we can continue improving our build to become more powerful than we could ever have imagined :)