Blood moon - Revision history

Leoetlino: /* Panic Blood Moons */

2022-05-25T21:10:55Z

Panic Blood Moons

← Older revision		Revision as of 21:10, 25 May 2022
Line 13:		Line 13:

	== Panic Blood Moons ==		== Panic Blood Moons ==
	Panic Blood Moons occur when the game is running out of memory<ref>Debug play reports refer to the event as a "BloodyMoon ForMemory" at 0x71007A95B4 (Switch 1.5.0)</ref> or when some tasks are taking too much time.		Panic Blood Moons occur when the game is running out of memory<ref>Debug play reports refer to the event as a "BloodyMoon ForMemory" at 0x71007A95B4 (Switch 1.5.0)</ref> or when some tasks are taking too much time. Unlike regular blood moons, panic moons trigger a full system reset and take longer to execute.

	Contrary to a widespread theory, they are not used as a generic error handler or a fallback for "unhandled events". Panic blood moons can only occur in specific cases.		Contrary to a widespread theory, they are not used as a generic error handler or a fallback for "unhandled events". Panic blood moons can only occur in specific cases.

Leoetlino: clarify the fact that regular blood moons only exist for gameplay reasons

2022-05-25T21:04:09Z

clarify the fact that regular blood moons only exist for gameplay reasons

← Older revision		Revision as of 21:04, 25 May 2022
Line 1:		Line 1:
	The '''Blood Moon''' is a game mechanic that ensures the world stays populated with enemies and weapons. Every time a blood moon occurs, enemies that have been defeated and overworld weapons that have been picked up by the player respawn.		The '''Blood Moon''' is a game mechanic that ensures the world stays populated with enemies and weapons. Every time a blood moon occurs, enemies that have been defeated and overworld weapons that have been picked up by the player respawn.

	~~Blood~~ moons are also used to reset internal state when some subsystems are running out of memory or become unresponsive. Such blood moons do not follow ~~the~~ regular schedule and are commonly referred to as "panic blood moons".		''Regular'' or ''scheduled blood moons'' (those that occur at midnight) only exist for gameplay reasons: contrary to popular belief, they do ''not'' act as a garbage collection or error repair mechanism.

			In some rare circumstances, blood moons are also used to reset internal state when some subsystems are running out of memory or become unresponsive. Such blood moons do not follow any regular schedule and are commonly referred to as ''panic blood moons''.

	A common misconception is that blood moons help replenish system memory by resetting enemy kill flags. This is however total nonsense, because enemy kill flags are just GameData flags, and all GameData flags are loaded at bootup and stay in memory forever<ref>Even without any code reverse engineering, anyone who has an idea of what they are talking about knows that the game never loads [[Bootup.pack]] (which holds the GameData configuration) again after init so it cannot possibly be unloading flags. Not to mention that it'd be ridiculously inefficient to unload and reload flags all the time.</ref>.		A common misconception is that blood moons help replenish system memory by resetting enemy kill flags. This is however total nonsense, because enemy kill flags are just GameData flags, and all GameData flags are loaded at bootup and stay in memory forever<ref>Even without any code reverse engineering, anyone who has an idea of what they are talking about knows that the game never loads [[Bootup.pack]] (which holds the GameData configuration) again after init so it cannot possibly be unloading flags. Not to mention that it'd be ridiculously inefficient to unload and reload flags all the time.</ref>.

Leoetlino: /* Scheduled Blood Moons */

2020-06-05T15:57:56Z

Scheduled Blood Moons

← Older revision		Revision as of 15:57, 5 June 2020
Line 8:		Line 8:
	{{link to article\|link=Time}}		{{link to article\|link=Time}}

	Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[Time]] or [[WorldMgr]] (for even more technical details).		Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" cutscene (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[Time]] or [[WorldMgr]] (for even more technical details).

	== Panic Blood Moons ==		== Panic Blood Moons ==

Leoetlino: /* Panic blood moon inhibitors */

2020-05-22T15:32:34Z

Panic blood moon inhibitors

← Older revision		Revision as of 15:32, 22 May 2020
Line 49:		Line 49:
	* there is an active event		* there is an active event
	* the player actor does not exist		* the player actor does not exist
	* the player is more than 0.~~25 distance units~~ away from his save position (game data flag: PlayerSavePos)		* the player is more than 0.5m away from his save position (game data flag: PlayerSavePos)

	== Notes ==		== Notes ==

Leoetlino: /* Scheduled Blood Moons */ link to Time

2020-05-10T21:56:59Z

Scheduled Blood Moons: link to Time

← Older revision		Revision as of 21:56, 10 May 2020
Line 6:		Line 6:

	== Scheduled Blood Moons ==		== Scheduled Blood Moons ==
	{{link to article\|link=~~WorldMgr#Midnight checks~~}}		{{link to article\|link=Time}}

	Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[WorldMgr]].		Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[Time]] or [[WorldMgr]] (for even more technical details).

	== Panic Blood Moons ==		== Panic Blood Moons ==

imported>Leoetlino: /* Panic Blood Moons */

2018-11-25T11:41:58Z

Panic Blood Moons

← Older revision		Revision as of 11:41, 25 November 2018
Line 15:		Line 15:
	Contrary to a widespread theory, they are not used as a generic error handler or a fallback for "unhandled events". Panic blood moons can only occur in specific cases.		Contrary to a widespread theory, they are not used as a generic error handler or a fallback for "unhandled events". Panic blood moons can only occur in specific cases.

	Panic conditions are checked every frame by [[GameScene]], which also keeps track of the panic reason in an unsigned 32-bit integer so that memory issues can be reported to Nintendo via the [[telemetry]] system.		Panic conditions are checked every frame by [[GameScene#precalc]], which also keeps track of the panic reason in an unsigned 32-bit integer so that memory issues can be reported to Nintendo via the [[telemetry]] system.

	{\|class="wikitable"		{\|class="wikitable"

imported>Leoetlino: /* Panic blood moon inhibitors */

2018-11-25T11:41:26Z

Panic blood moon inhibitors

← Older revision		Revision as of 11:41, 25 November 2018
Line 43:		Line 43:

	=== Panic blood moon inhibitors ===		=== Panic blood moon inhibitors ===
	Panic blood Moons can only occur if '''all''' of the following conditions are '''false''':		Panic blood Moons can only occur if '''all''' of the following conditions are '''false'''<ref>Switch 1.5.0 0x71007ADFB0</ref>:
	* the player is in a dungeon, AocField, GameTestField, GameTestField2, or any debug or dev map		* the player is in a dungeon, AocField, GameTestField, GameTestField2, or any debug or dev map
	* the Fade screen (loading screen) is opened		* the Fade screen (loading screen) is opened

imported>Leoetlino: /* Panic blood moon inhibitors */

2018-11-25T11:41:06Z

Panic blood moon inhibitors

← Older revision		Revision as of 11:41, 25 November 2018
Line 45:		Line 45:
	Panic blood Moons can only occur if '''all''' of the following conditions are '''false''':		Panic blood Moons can only occur if '''all''' of the following conditions are '''false''':
	* the player is in a dungeon, AocField, GameTestField, GameTestField2, or any debug or dev map		* the player is in a dungeon, AocField, GameTestField, GameTestField2, or any debug or dev map
	* the Fade screen is opened		* the Fade screen (loading screen) is opened
	* some EventMgr check returns false{{check}}		* some [[EventMgr]] check returns false{{check}}
	* there is an active event		* there is an active event
	* the player actor does not exist		* the player actor does not exist

imported>Leoetlino: /* Inhibitors */

2018-11-25T11:40:17Z

Inhibitors

← Older revision		Revision as of 11:40, 25 November 2018
Line 42:		Line 42:
	A panic moon causes enemies and other respawnable objects to respawn since it calls [https://eventviewer.zeldamods.org/viewer.html?data=/d/Demo011_0.json&params=1&entry=Demo011_0&node=Event3 Demo011_0] just like the regular blood moon code. The demo contains a call to [[AIDef:Action/EventOffWaitRevivalAction]] (OffWaitRevival), which appears to be what actually resets the revival flags.		A panic moon causes enemies and other respawnable objects to respawn since it calls [https://eventviewer.zeldamods.org/viewer.html?data=/d/Demo011_0.json&params=1&entry=Demo011_0&node=Event3 Demo011_0] just like the regular blood moon code. The demo contains a call to [[AIDef:Action/EventOffWaitRevivalAction]] (OffWaitRevival), which appears to be what actually resets the revival flags.

	=== ~~Inhibitors~~ ===		=== Panic blood moon inhibitors ===
	{{~~empty section~~}}		Panic blood Moons can only occur if '''all''' of the following conditions are '''false''':
			* the player is in a dungeon, AocField, GameTestField, GameTestField2, or any debug or dev map
			* the Fade screen is opened
			* some EventMgr check returns false{{check}}
			* there is an active event
			* the player actor does not exist
			* the player is more than 0.25 distance units away from his save position (game data flag: PlayerSavePos)

	== Notes ==		== Notes ==

imported>Leoetlino: /* Scheduled Blood Moons */

2018-10-30T20:02:37Z

Scheduled Blood Moons

← Older revision		Revision as of 20:02, 30 October 2018
Line 7:		Line 7:
	== Scheduled Blood Moons ==		== Scheduled Blood Moons ==
	{{link to article\|link=WorldMgr#Midnight checks}}		{{link to article\|link=WorldMgr#Midnight checks}}

	Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[WorldMgr]].		Scheduled Blood Moons are based on a timer that starts running as soon as the "step out of Shrine of Resurrection" (Demo103_0) has finished. When the timer reaches 7 in-game days, the WM_BloodyDay flag is set. The next time it is midnight, assuming blood moons are not inhibited, the Blood Moon cutscene will trigger. For more details, read [[WorldMgr]].