PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Skill pathing breaks on imported trees

Open
#7,405 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Lua
Stars
5.4k
Forks
2.4k
Avg merge
1d 12h
Merged PRs (30d)
26

Description

Check version
  • I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
  • I've checked for duplicate open and closed issues by using the search function of the issue tracker
How is Path of Building expected to behave?

After importing a tree through the manage trees interface, the newly imported tree should be used for pathfinding purposes.

How does Path of Building behave?

After importing through the manage trees interface, the new tree always paths the first allocation after import to the closest class start node, ignoring already allocated nodes.

How to reproduce the issue
  1. Create new build
  2. control + M or open through dropdown in tree tab
  3. Import build, use the link to the official site provided. The issue does not persist when importing the entire build through the import/export tab.
  4. Hover over a node that's closer to the class start you didn't go to than the one already allocated. The example tree provided sees the issue if you hover over the right mana and life node above witch. You can also click to allocate that path. The issue disappears once you've done so.
Character build code
https://www.pathofexile.com/fullscreen-passive-skill-tree/AAAABgMABREtLJyOvpLB37AAAA==
Screenshots

Correct behaviour on manually created tree
image

Incorrect behaviour on imported tree
image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the manage trees interface and its tree-tab import flow, then compare it with the import/export tab path that does not reproduce the issue. Verify that pathfinding after importing uses the imported tree and respects already allocated nodes, including the provided Witch-node scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.