PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding-PoE2

Add an option to always show "secret" tree nodes

Open
#2,056 0 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?

I know of two secret/hidden passive tree nodes that only show up if you meet their conditions:

  • "The Hollowkeeper" (take both "First Teachings of the Keeper" and "First Principle of the Hollow")
  • "Path of the Renegade" (take "Redblade Discipline", "Brinerot Ferocity", and "Mutewind Agility")

These are really cool! Discovering The Hollowkeeper in-game during my 0.5 monk run was a neat surprise.

But in PoB, currently you can't plan your build around these conditional nodes unless you already know they exist, and you can't search for them if they're hidden.

Describe the solution you'd like

It would be nice to have a configuration option to show secret nodes.

Ideally, this would show the hidden node with a clear visual indicator that it's conditional (e.g. greyed out or lower opacity), and the tooltip would list the nodes you need to take for the node to become available.
As a stretch goal, clicking on it would automatically path to the prerequisite nodes, but maybe this would be a bit complex.

For example, The Hollowkeeper tooltip could read:

The Hollowkeeper

Requires:

  • First Teachings of the Keeper
  • First Principle of the Hollow

50% reduced effect of Curses on you
35% reduced Effect of Non-Damaging Ailments on you

I think this could be kept separate from the Oracle's Unseen Path nodes. I definitely agree they were cluttering up the tree (#1742). (Maybe there could be a separate config option for Unseen Path? But that's outside the scope of this feature request.)

Describe alternatives you've considered

No response

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

Start by locating the passive-tree rendering and configuration entry points, then find the data and current conditional handling for The Hollowkeeper and Path of the Renegade. Done means an option reveals secret nodes with a clear conditional indicator and prerequisite details in their tooltips; the automatic-pathing stretch goal is outside the required scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.