-
Notifications
You must be signed in to change notification settings - Fork 671
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
Core: Minimal-Items Accessibility Fix #1888
Merged
Berserker66
merged 7 commits into
ArchipelagoMW:main
from
Alchav:accessibility_check_tweak
Feb 13, 2024
Merged
Core: Minimal-Items Accessibility Fix #1888
Berserker66
merged 7 commits into
ArchipelagoMW:main
from
Alchav:accessibility_check_tweak
Feb 13, 2024
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
…accessibility_check_tweak # Conflicts: # BaseClasses.py
…accessibility_check_tweak # Conflicts: # BaseClasses.py
ThePhar
added
is: bug/fix
Issues that are reporting bugs or pull requests that are fixing bugs.
affects: core
Issues/PRs that touch core and may need additional validation.
labels
Jun 25, 2023
Got an example yaml I can get it to reproduce? I can try to run through this later. |
With
|
agilbert1412
approved these changes
Feb 10, 2024
agilbert1412
added
the
waiting-on: core-review
Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer.
label
Feb 10, 2024
Berserker66
approved these changes
Feb 13, 2024
Jouramie
pushed a commit
to Jouramie/Archipelago
that referenced
this pull request
Feb 28, 2024
TheLX5
pushed a commit
to TheLX5/Archipelago
that referenced
this pull request
Mar 2, 2024
TheLX5
pushed a commit
to TheLX5/Archipelago
that referenced
this pull request
Mar 2, 2024
EmilyV99
pushed a commit
to EmilyV99/Archipelago
that referenced
this pull request
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects: core
Issues/PRs that touch core and may need additional validation.
is: bug/fix
Issues that are reporting bugs or pull requests that are fixing bugs.
waiting-on: core-review
Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer.
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?
The promises of
locations
accessibility ensuring "everything can be reached and acquired" anditems
accessibility ensuring "all logically relevant items can be acquired" imply that anitems
player may have locations they cannot reach, but that their own advancement items will always be reachable.This is largely what the accessibility check ensures, except that if an
items
player has locations that are not reachable, aminimal
players' unnecessary advancement items may be placed in theitems
player's unreachable locations and this will cause the accessibility check to fail.Currently the Dexsanity option in Pokémon Red and Blue allows for logically inaccessible locations. In some cases they may be locations that you can in fact reach or that you may have to make a specific choice in order to reach, but need to be out of logic because it may be possible to permanently miss them. Right now this option forces accessibility off of
locations
(unless other options are set specifically that will prevent any from being out of logic) but in my WIP update, I am instead deleting the unreachable locations iflocations
accessibility is chosen.This PR tweaks the accessibility check to allow
items
players' locations to containminimal
players' advancement itemsHow was this tested?
After seeing an accessibility check failure due to a
minimal
player's advancement item landing on an inaccessibleitems
player's location, re-generated with same seed using this change.