Skip to content

Preserve cluster jewel notables when changing enchantment#9513

Open
EtherealCarnivore wants to merge 2 commits intoPathOfBuildingCommunity:devfrom
EtherealCarnivore:cluster-enchant-preserve-mods
Open

Preserve cluster jewel notables when changing enchantment#9513
EtherealCarnivore wants to merge 2 commits intoPathOfBuildingCommunity:devfrom
EtherealCarnivore:cluster-enchant-preserve-mods

Conversation

@EtherealCarnivore
Copy link
Contributor

@EtherealCarnivore EtherealCarnivore commented Mar 2, 2026

3.28 adds a currency that changes a cluster jewel's enchantment without touching existing mods. Right now, changing the enchant in the crafting UI re-validates all affixes against the new skill tag and drops any that can't roll on the new base.

Changed the affix list filter in UpdateAffixControl to keep the currently-selected mod in each slot even if its spawn weight is zero for the new enchant.

  • Tested by crafting a Large phys cluster with notables, switching the
    enchant to spell damage, and confirming the notables stay.

  • Full testsuite passes (194/194, the one failure in TestTradeQueryCurrency_specis pre-existing).

Keep currently-selected affixes in the dropdown even when they
can't naturally spawn on the new base. In 3.28 you can change
a cluster jewel's enchantment without losing existing mods,
so the affix list filter now skips the spawn weight check for
whatever mod is already selected in each slot.
@EtherealCarnivore EtherealCarnivore marked this pull request as draft March 2, 2026 17:54
Grey out notables in the affix dropdown that only appear because
they are currently selected but have zero spawn weight on the
active enchantment. This makes it clear which mods were carried
over from a different cluster jewel enchant.
@EtherealCarnivore EtherealCarnivore marked this pull request as ready for review March 2, 2026 18:26
@EtherealCarnivore
Copy link
Contributor Author

Update: Added a [Retained] label (greyed out) to cluster jewel notables in the affix dropdown that are carried over from a previous enchantment but have zero spawn weight on the current one. This makes it visually clear which mods were from a different enchant base vs. naturally available on the current one.

Discussed with LocalIdentity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant