-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Add support for adding vestigial implicits #10156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
LocalIdentity
merged 16 commits into
PathOfBuildingCommunity:dev
from
vaisest:add-vestigial
Aug 23, 2026
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
d5a4f37
Add support for adding vestigial implicits
vaisest 7b2bc85
Prevent adding item to itself as vestigial
vaisest f1f33eb
Cleanup
vaisest 9499715
Fix shavs + Infernal Mantle mod id
d216f5d
Fix equality comparison
vaisest a2d1c4e
Add "Core drop pool" filtering to vestigial implicits and unique db
vaisest 9a6bdbf
Fix (hopefully) all the rest of the core drop pool uniques
vaisest e4368a7
Fix stasis prison and typo
vaisest 8d5422c
Regen modcache
vaisest c1c33b9
Cleanup
vaisest c424d0e
Remove delve implicits
vaisest e111723
Move popup code to its own module and remove various bits of dead code
vaisest ab60d68
Fix random sorting on vestigial mods
vaisest 9ce2b01
Fix mod double up
8c39baa
Fix tooltip to show stat difference of replacing the implicit
5a0c149
Merge branch 'dev' into add-vestigial
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codex found a possible data-contract edge case here: this condition appears to treat missing
Sourcemetadata as a positive core-pool match. At the merged head, The Hateful Accuser, The Queller of Minds, and The Selfish Shepherd have noSourceline, so they match this filter even though Nameless Rings are obtained from Rituals.This seems to establish false positives in the global Unique DB filter, although it does not by itself show that the audited Vestigial armour receiver set is incorrect. Would it make sense to distinguish explicit core-pool metadata from unknown metadata—for example with
Source: Drops anywhere—and cover a restricted item with missingSourcein a regression test?