A spoiler-aware field guide to the dream threats that interrupt exploration, puzzles, and journal runs across both chapters.
A Broken Dream uses chapter-specific threats as pressure during exploration rather than as a collectible combat roster. There is no honest S-to-D monster ranking: the useful question is where a threat appears, what objective you are protecting, and whether the current room gives you space to retreat.
Threats in A Broken Dream are tied to scenes and story spaces. A video that demonstrates one chase does not prove that the same timing, path, or behavior applies everywhere. Use the chapter walkthrough as the route map, then treat the room’s lighting, sound cue, doors, and objective text as the final instruction.
The safest preparation is route knowledge. In Cloud Theater, Dream Elementary, Grassy Beach, The Twist, Homescape, The Past Future, Surreal Woodlands, and The In-Between, leaving an objective half-finished can force an unnecessary return through danger. Journal and memory hunters should check the collectible route before triggering a transition.
The game does not publish a bestiary with health, damage, speed, spawn rate, or difficulty numbers. This guide therefore does not assign fake stats. Practical survival comes from recognizing the active objective, keeping an escape route visible, and repeating a failed section with the same group size when possible.
Snoogle's public “Modeling a Monster for Chapter 3” development stream confirms that a Chapter 3 monster is in development. Its title does not establish a finished name, behavior, area, stats, or playable status, so this hub links to the Chapter 3 source-watch instead of inventing a new bestiary entry.
If a named entity or behavior is missing here, that is deliberate. The creator-associated community wiki and recent walkthrough videos are useful discovery sources, but names and lore can change or reflect fan terminology. The page will expand when a threat can be matched to a stable scene and current-build evidence.
No useful combat tier list is supported. Threats are story hazards, not units that players collect, equip, or rank.
The current evidence supports exploration, puzzle, and chase behavior rather than a published combat-stat system. Follow the room objective instead of relying on invented damage advice.
Only some names may appear in creator-associated or community references. This site does not promote a fan label to official status without stronger evidence.
Start with the Chapter 1 or Chapter 2 walkthrough, identify the exact area, and use the room-specific stuck notes.
Choose the chapter and area where the threat appeared.
Separate confirmed development work from unnamed or unreleased monster claims.
See the honest alternatives to made-up monster rankings.
Read a spoiler-aware entity summary with clear lore limits.
First-party development signal; the public title confirms modeling work but no name, mechanics, or release date.
Used for scene discovery and repeated player language, not universal stats.
Creator-associated community reference; pages remain community editable.
First-party identity, chapter, platform, and game-description reference.
