-
Notifications
You must be signed in to change notification settings - Fork 234
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
Cutscenes being skipped leads to incorrect time of day in some cases #1902
Comments
Sometimes it can be a bit weird to handle this since it might depend on the speed that you advance through the cutscene. IMO the most egregious case currently in the release (and it's been this way for forever) is Zelda's Lullaby not setting it to noon. The one for going adult is a bit weird since nothing really happens when you go adult for the first time. And what if you start as adult, should it still make it noon the first time you swap or the first time you go adult again? But if there's ever a light medallion check in ToT I might suggest getting that make it noon. |
I want to point out also that beating dungeons setting time of day might actually cause some non-repeatable access in rare cases. |
It's worth noting that #2034 currently contains code that explicitly sets time of day in blue warps to emulate the vanilla behavior. We may want to consider removing that code to address the nonrepeatable access. |
With #2287, we have eliminated the last instance of nonrepeatable ToD access that could cause softlocks, by making blue warp ToD changes repeatable. We should avoid reintroducing nonrepeatable ToD access, so changing ToD when going adult for the first time or checking
|
I would like to be able to select any starting time of day. (I've heard there are some weird edge cases right around the transition between days and nights. Does anybody know what the specifics of those are? There might need to be some logic adjustments to be able to handle those.) |
That could be a decent way of solving this. Maybe just changing the dropdown to a 0–23 slider to allow selecting any full hour would work without having to exhaustively check if these edge cases exist. |
This is not a new bug. I'm just opening this issue for documentation purposes.
Some events that normally set the time in vanilla due to a cutscene either set it to the incorrect time or don't set it at all in OoTR due to cutscenes being skipped.
Additionally, the "Default (10:00)" starting time option in the gui is a bit of a misnomer since in vanilla you don't get control over Link until noon. This is because by the time this setting was added, people were already used to 10:00 being the "default" starting time of day in Randomizer. So "default" doesn't refer to vanilla, but OoTR.
The text was updated successfully, but these errors were encountered: