PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Thread of Hope may cause Passive pathing to take a route that is not the shortest
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
-
What happened?
Having Thread of Hope socketed caused adding a passive node that was 1 node away from the existing tree to path through another node instead, using 2 passive points. Removing Thread of Hope prevents the issue from happening. -
What steps will reproduce the bug?
Allocate a node instead of Thread of Hope's radius that is connected to your base tree. Allocate another node and the automatic pathing may not take the shortest path. -
Does it reproduce every time?
Yes -
Provide a build code:
Tree: http://poeurl.com/dlah
Full PoB: https://pastebin.com/LFP1wjYa -
Screenshots:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the issue. First reproduce the behavior with the linked Tree or Full PoB while Thread of Hope is socketed, then trace the passive-node automatic pathing logic; done means the selected route consistently uses the shortest path in this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100