Improved Gem pages, Type-catch quest pages, requirements fix #220
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.
Gem Pages have been updated for the monotype gem buff, made the information more useful (% means nothing when different mons/encounter types give different numbers of gems), and return the two best locations per region, rather than 1 gym + 1 route (as routes are generally terrible)
Gem pages were often used as a proxy for locating specific types for a type-catch quest, however they were poor due to not taking into consideration catch chances, added a tailor-made page for this use:
While there are some similarities with the Dungeon Tokens table, I went for simplicity of fetching the current day/weather conditions and calculating from there, and also chose three key datapoints for the catch chance modifiers rather than listing every combination
Finally, added the requirement override which makes all requirements show as incomplete, so the various "less than" requirements that are completed by default now show:
