Repository navigation
Add 3.30 skill trees - #10437
Merged
Merged
Add 3.30 skill trees#10437
Conversation
nexus671
added a commit
to nexus671/PathOfBuilding-AI-Edition
that referenced
this pull request
Nov 12, 2026
|
Small thing I hit on this branch: importing a character over an already-loaded build drops 4 notables (29 vs 25). Into a new build it's fine. Repro: load spec/TestBuilds/3.13/OccVortex.xml, then import SampleCharacter. Missing: Thrill Killer, Tempest Blast, Arcane Focus, Soul Siphon. Dev gives 29 both ways. |
Member
|
@jabberwock I believe that is a pre-existing issue on dev, but if you drop an example I can look into it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the problem being solved:
Adds the new 3.30 trees.
9f3eb0f also fixes the wording for the new "within _ metres" lines by converting the new forms to be like the old nearby form. The range information isn't actually processed in PoB, and I don't think it could be since PoE1 doesn't have a simple presence concept unlike PoE2. Feel free to revert that if it's not correct.
The only real thing that needed changes here was removing the GGG tooltip tags from some of the mastery effects.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
Before screenshot:
After screenshot: