You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2021. It is now read-only.
Resetting into the Sirena 5 casino (either with Z or C-down + X) after defeating King Boo without grabbing his Shine causes weird side effects the next time the fight area is entered: King Boo immediately makes his “canceled cycle” sound while the center of the roulette is still above him, said center stops in the air, and the fight starts like that. In that state, resetting again before King Boo shows up will make the same thing happen next time.
This doesn’t happen upon loading into Sirena 5 with C-down + Z at the end of the fight, or if King Boo’s Shine has already been collected.
This is probably related to #2 and the Manta glitch with some states or flags not resetting properly when reloading a level.
Might also be that these things can happen in stages which have a special behaviour defined in the dol rather than the scene itself. (Rollercoaster, Manta, Boo/Slots).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Resetting into the Sirena 5 casino (either with Z or C-down + X) after defeating King Boo without grabbing his Shine causes weird side effects the next time the fight area is entered: King Boo immediately makes his “canceled cycle” sound while the center of the roulette is still above him, said center stops in the air, and the fight starts like that. In that state, resetting again before King Boo shows up will make the same thing happen next time.
This doesn’t happen upon loading into Sirena 5 with C-down + Z at the end of the fight, or if King Boo’s Shine has already been collected.
Videos:
Causing the glitch: https://twitter.com/Qbe_Root/status/933752355249586176
Further exploration of the effects: https://twitter.com/Qbe_Root/status/933727730255921152
The text was updated successfully, but these errors were encountered: