PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Point based power report calculations
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
when using the power report it can sometimes take a while(sometimes 2-3 minutes) while it looks at every single node.
Describe the solution you'd like
when using the power report it should only calculate the nodes that are either anointable or within reach from any active node for the remaining amount of skill points you have available. (option to toggle between default(as it is now) or the point/distance based calculations would allow people to choose how they wish to view the power report)
could also add a 3rd option to tell it to only calculate x distance from active nodes so even if the user only has 5 points left they could tell it to calculate as though they had 10 points left.
Describe alternatives you've considered
No response
Additional context
the system already knows how far each node is from an active node so hopefully it wouldn't be to difficult to add flag to the nodes to tell it to calculate nodes that are only "remaining skill points" away from an active node.

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 file, test, or entry point is named. Start by locating the power report calculation and the existing node-distance logic, then determine how remaining skill points and anointable nodes are represented. Done means the report can apply the requested point- or distance-based filtering, with a clear choice between the proposed calculation modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100