Draft: Add passive tree progression timeline#1930
Conversation
7664f35 to
1b0ad8e
Compare
Nope, it's rewriting maxroll_example.mp4
I actually not have actual case for this one. Probably not issue at all, i just saw this behavior and it's confusing me.
Now i'm also cannot reproduce it xD. I run pob runtime through Proton, maybe this some way affect |
|
Not sure I am a fan of it scrapping the tree if you scrub and make another selection, I would love to hear others opinion on what the default behavior should be. This could be in the form of what maxroll has, where the default behavior is to 'scrap' the tree in favor for the new path unless you actively hit "Edit history" which then appends at the scrubbed point. @LocalIdentity do you have a take on this? |
1b0ad8e to
dbc509b
Compare
|
I think trying to keep it be familiar to what Maxroll has is the best bet with a edit history button if you do want to wipe the tree |
|
I'll look into adding the edit history button and changing the default behavior to replacing |
|
Let me know if this feels more intuitive 👍 |







This PR adds passive tree progression similar to tools like Maxroll's PoE2 planner
Intention of the feature is to give the underlying support for exporting to the new .build format.
Build creators have the ability to respec without swapping to a new tree as well as editing the history via scrubbing through the timeline and placing new nodes.
Any feedback is much appreciated, i tried to cover all the bases I could think of.