PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding-PoE2

Option to hide or mark passive tree nodes that I'm not interested in

Open
#1,726 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
1.9k
Forks
451
Avg merge
21h 16m
Merged PRs (30d)
68

Description

Check for duplicates
  • I've checked for duplicate open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?

Windows

Is your feature request related to a problem?

There are entirely too many passive nodes on this tree. It would be immensely helpful to visually identify nodes that I am not at all interested in for my current build. I frequently find myself re-reading passives I've already looked at, wasting time and mental energy.

Node power helps, but more or less ignores a lot of utility passives and makes the tool run much slower.

Describe the solution you'd like

I would love the ability to hide or otherwise mark passive tree nodes that I am not at all interested in when trying to plan out builds.

Suggested Implementation:

HOTKEY + clicking a node signifies a node as "Not interested" via visual modification. Either color, opacity or icon.
Automatically marks all nodes past it that can't be pathed to from elsewhere.
Marked nodes can still be moused over for tooltips.
Button to clear all marked nodes.

Describe alternatives you've considered

Bonus points for multiple modes of marking. Ex. No, Maybe and Yes. For highlighting nodes that need further consideration, or nodes I definitely but need to figure out to path to.

Additional context

No response

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

The issue names no files, tests, or entry points. Start by locating the passive-tree UI entry point and its existing node interaction and rendering behavior; done requires defined marking modes, path-dependent hiding or marking, tooltip access, and a way to clear all marks.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
desktop, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.