Don't ever look up wishlist for definition-only items #10840
Merged
Conversation
This file contains 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.
We had an issue where vendor items would load with no live perk info, and thus fall back to definitions, which have every possible perk. This would match every wishlist entry, and that would then get cached in the wishlists cache. Then when the real live info loaded, the cache wouldn't get invalidated.
This changes to ignore wishlist status on definition-based perks entirely, and skip the cache.
Before:
After:
I also fixed #8327 by plumbing the vendor next refresh date into the item IDs. This means when the vendor refreshes, the wishlist cache should get new entries.
Fixes #8327