Make ami_permian_cutscene obtainable after seeing the event#1443
Merged
AcrylonitrileButadieneStyrene merged 1 commit intoJul 21, 2026
Merged
Conversation
Switch 426 prevents the minigame (and by extension the event) from being done again on the same file; it's also set directly after the cutscene so it's fine to use it as the only condition.
AcrylonitrileButadieneStyrene
merged commit Jul 21, 2026
6a46865
into
ynoproject:master
2 checks passed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Switch 426 prevents the minigame (and by extension the event) from being done again on the same file; it's also set directly after the cutscene so it's fine to use it as the only condition.
(I've tested both cases (fresh and post-event).)