-
Notifications
You must be signed in to change notification settings - Fork 703
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
Pokemon Emerald: Some dexsanity locations contribute evolution items #3187
Open
Zunawe
wants to merge
15
commits into
ArchipelagoMW:main
Choose a base branch
from
Zunawe:emerald-dexsanity-evo-items
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
If a species evolves via item use (Fire Stone, Metal Coat, etc.), use that as it's vanilla item instead of a ball
github-actions
bot
added
the
waiting-on: peer-review
Issue/PR has not been reviewed by enough people yet.
label
Apr 21, 2024
Zunawe
added
the
is: enhancement
Issues requesting new features or pull requests implementing new features.
label
Apr 21, 2024
…we/Archipelago into emerald-dexsanity-evo-items
Exempt-Medic
approved these changes
Aug 2, 2024
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.
The code LGTM. Tested through generations and looking at spoiler logs to see that all evo items were added to the pool a number of times equal to the number of Mons that evolve by that method.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
is: enhancement
Issues requesting new features or pull requests implementing new features.
waiting-on: peer-review
Issue/PR has not been reviewed by enough people yet.
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.
What is this fixing or adding?
Evolving pokemon isn't (currently) in-logic for dexsanity, but it's still common enough to do. But for some pokemon that evolve via item use, it can be difficult or impossible to find the relevant items.
This changes the "vanilla item" that dexsanity locations contribute if the species evolves by using those items. So with a
shuffled
item pool, there will always be enough evolution items to evolve all included species. And withdiverse_balanced
there will at least be a slightly higher concentration of evolution items.Also technically fixes a bug where
_str_to_evolution_method
was missing theITEM
method, which resulted in the value beingNone
for pokemon with evolution items. This value was never read anyway, so the bug had no effect.How was this tested?
Generated a game with a
shuffled
item pool and checked the counts for a few evolution items.