Scheduled system upgrade on Sunday 21 April 2024 15:00-16:00 UTC - On that day, the wiki and other services might go down for 5-15 minutes.

Blood moon: Difference between revisions

From ZeldaMods (Breath of the Wild)
Jump to navigation Jump to search
VisualWikitext
imported>Leoetlino
imported>Leoetlino
(10 intermediate revisions by the same user not shown)
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 are commonly referred to as "panic" or "emergency blood moons".
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".


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 reverse engineering the code, everyone 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>.


== Scheduled Blood Moons ==
== Scheduled Blood Moons ==
{{empty section}}
{{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]].


== Panic Blood Moons ==
== Panic Blood Moons ==
Panic Blood Moons occur when the game is running out of memory<ref>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.
 
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]], 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.
Line 19: Line 23:
| 0 || '''[[Resource system]]'''<ref>0x7101213144</ref>: at least one of the following is true:
| 0 || '''[[Resource system]]'''<ref>0x7101213144</ref>: at least one of the following is true:
* Bit 12 is set in the ResourceMgrTask's flags (indicating a problem with a resource load{{check}})<ref>0x710120C5E4</ref>
* Bit 12 is set in the ResourceMgrTask's flags (indicating a problem with a resource load{{check}})<ref>0x710120C5E4</ref>
* ''An'' overlay arena's heap free size percentage is ''less than or equal to'' its configured minimum percentage.<ref>0x71011FCDE4</ref>
* ''An'' overlay arena's heap free size percentage is ''less than'' its configured minimum percentage.<ref>0x71011FCDE4</ref>
**The limit is 0% for the OverlayArena system itself, "Tera SZS work" (Tera decompressing buffer), Audio and [[StarterPackMgr]]. The default is 0% too.
**The limit is 0% for the OverlayArena system itself, "Tera SZS work" (Tera decompressing buffer), Audio and [[StarterPackMgr]]. The default is 0% too.
**The limit is 5% for the "ForResourceS" (small) and "ForResourceL" (large) heaps, which is where most resources are allocated from.
**The limit is 5% for the "ForResourceS" (small) and "ForResourceL" (large) heaps, which is where most resources are allocated from.
Line 38: 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 ==
<references/>


[[Category:Game mechanics]]
[[Category:Game mechanics]]
[[Category:Internals]]
[[Category:Internals]]

Revision as of 11:40, 25 November 2018

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".

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[1].

Scheduled Blood Moons

Full article: 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.

Panic Blood Moons

Panic Blood Moons occur when the game is running out of memory[2] or when some tasks are taking too much time.

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 Blood Moon reasons
Bit Description
0 Resource system[3]: at least one of the following is true:
  • Bit 12 is set in the ResourceMgrTask's flags (indicating a problem with a resource load[check])[4]
  • An overlay arena's heap free size percentage is less than its configured minimum percentage.[5]
    • The limit is 0% for the OverlayArena system itself, "Tera SZS work" (Tera decompressing buffer), Audio and StarterPackMgr. The default is 0% too.
    • The limit is 5% for the "ForResourceS" (small) and "ForResourceL" (large) heaps, which is where most resources are allocated from.
1 PhysicsMemSys: Havok main heap is running out of memory (less than 5% free)[6]
2 PlacementMgr: Actor spawning heap is running out of memory (less than 5% free)[7]
3 ResourceSystem/OverlayArena: ForResourceS heap is running out of memory[8]
4 ResourceSystem/OverlayArena: ForResourceL heap is running out of memory[9]
5 ResourceSystem/OverlayArena: Audio heap is running out of memory[10]
6 ResourceSystem/TextureHandleMgr: Last TextureHandleMgr::calc execution took more than 60 seconds[check][11]

A panic moon causes enemies and other respawnable objects to respawn since it calls 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.

Panic blood moon inhibitors

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

  1. ↑ 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.
  2. ↑ Debug play reports refer to the event as a "BloodyMoon ForMemory" at 0x71007A95B4 (Switch 1.5.0)
  3. ↑ 0x7101213144
  4. ↑ 0x710120C5E4
  5. ↑ 0x71011FCDE4
  6. ↑ 0x7101216C08
  7. ↑ 0x7100D5DC40
  8. ↑ 0x71011FCFF8
  9. ↑ 0x71011FD000
  10. ↑ 0x71011FD008
  11. ↑ 0x710120C670
Retrieved from "https://zeldamods.org/w_botw/index.php?title=Blood_moon&oldid=7133"