Don't output rarity of unique beasts #183
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
lvlvllvlvllvlvl
merged commit 3b6dce3
into
Project-Path-of-Exile-Wiki:dev
1 check passed
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.
Abstract
When exporting bestiary components, don't include a 'rarity' key if the value is 'Unique'
Action Taken
See https://discord.com/channels/872882365406523452/873440137558757407/1244104304114274314
This was causing issues with The Black Morrigan, the only currently capturable creature that has a unique rarity. Unique monsters captured during bestiary league are treated as rares for the purpose of recipes, suggesting that the 'unique' rarity is no longer relevant for bestiary recipes.