-
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
SM64ex: Logic and Generation Fixes #3135
SM64ex: Logic and Generation Fixes #3135
Conversation
Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
… to the pillars and ground pounding on top of them in basic logic. Shell is considered capless method. Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
Signed-off-by: Magnemania <[email protected]>
@@ -246,6 +247,7 @@ class RuleFactory: | |||
|
|||
token_table = { | |||
"TJ": "Triple Jump", | |||
"DJ": "Triple Jump", |
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.
Is this supposed to be Triple Jump?
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.
"Triple Jump" the item unlocks both "DJ (Double Jump)" and "TJ (Triple Jump)" in the logic. Doesn't serve a purpose in the rules currently, but it lets anyone looking at the file know that DJ requires Triple Jump.
This was going to be part of a greater logic rework that replaced TJ with DJ in some rules to future-proof the logic for when DJ gets the option to be randomized separately, but that's a big feature addition
Signed-off-by: Magnemania <[email protected]>
What is this fixing or adding?
can_reach
to remove accessibility check errors. Ignored the legacy entrance dependencies on the Bowser in the Fire Sea entrance (entrance entrance rule depends on a location) as that rule has been around for several versions and has never been reported causing a failure.How was this tested?
100 generations with everything randomized, and 100 generations with everything randomized except moves. Went over a few spoiler logs by eye.
(This was originally going to be part of a larger logic polish-up, but I wanted to get these fixes through in time for the big async, as the accessibility check issues could become relevant when generating and the strict move requirements issue could create extremely difficult checks without player consent)