The Hollow maze changes across the event, so the most useful route is a method you can repeat: anchor yourself to the entrance, search in short loops, record clue and puzzle locations relative to landmarks, and protect the return path before taking a risk. Roblox officially confirms a new maze, clues, and a different monster each day, but not a complete public floor map.
Before entering
Check which floor or night the hub currently offers. Do not assume a screenshot labeled “Day 2” matches your server. Note the displayed floor, time, party size, and any objective text. If a prior floor remains selectable, decide whether you are completing an old reward or exploring the current event state.
Adjust brightness, camera sensitivity, volume, and performance settings. Connected horror content may use loud sounds or flashing effects. Stable movement and readable turns are more important than maximum graphics during route discovery.
Choose roles if you are in a group. One player can track the last safe landmark, another can inspect branches, and another can watch for the current threat. Everyone should know the return point before splitting.
Build a route from landmarks
At the entrance or elevator, pick a landmark that remains distinctive from both directions: a large prop, unusual wall color, staircase, sign, or room shape. Move to the next junction and give it a simple name. Record turns as relationships—“left from projector room, down one level”—rather than a long string of left and right commands.
Search one branch until it closes, produces a clue, or becomes unsafe. Then return to the named junction before opening another branch. This loop method costs a little distance but prevents the entire map from becoming one untraceable chain.
Use vertical information. A puzzle object above or below the entry level can look close on screen while requiring a different staircase. When a route crosses itself, note elevation as well as direction.
Handle clues and puzzle pieces
When you find a clue, relic, switch, lever, or puzzle piece, first identify whether it is collected automatically, held by one player, or changes a shared state. Watch for a visible counter or sound, but do not assume a sound alone means progress saved.
Call out the item and location before moving. If it must be carried back, protect a return path instead of continuing deeper. If it opens another route, check the nearest previously locked object before searching the whole maze again.
Community walkthroughs report floor-specific puzzle devices, but those details can change and may apply only to one day. Use them as a lead, then verify the visible symbols and interaction in your current server. Never present an unsupported clue count or lever order as universal.
Survive an unknown monster
The nine crossover identities are official, but their exact Hollow behavior needs current observation. A mechanic from DOORS, Dandy’s World, Piggy, or another source experience may be changed for this event.
On the first encounter, prioritize these questions:
- What visible or audible event begins the danger?
- Does the threat follow line of sight, sound, proximity, or a scripted route?
- Which spaces actually break pursuit in this server?
- Can players revive or regroup, and where do they return?
- Does a failed run preserve clues, a relic, or floor progress?
Change one variable per attempt. If hiding failed, try earlier separation or a different route rather than inventing a counter from one result. Share only behavior you can reproduce.
Solo and squad routes
Solo players should shorten each search loop and turn back earlier. Keep an escape direction visible when interacting with a puzzle. Do not commit to a long animation while the current threat is unaccounted for.
Squads can cover more branches but easily lose shared context. Use one leader for route names and one regroup rule: after a clue, danger cue, or missing teammate, return to the last named junction. Avoid everyone carrying separate incomplete directions.
If the event teleports or separates players, agree on a fallback landmark. The entrance, elevator, or first unmistakable room is better than “where we were before.”
Recover after a failed run
Before immediately restarting, check the objective counter, badge state, floor selector, and inventory. Record what persisted. Roblox has not published a universal rule for whether death resets clues or daily progress, so your current visible state is the deciding evidence.
If progress vanished, repeat the shortest verified branch first. If progress remained, return to the nearest unresolved object. If the server state looks inconsistent, rejoin once after capturing the current screen; repeated rejoins can erase useful evidence without fixing a service delay.
For a badge that exists on your account but does not register in the hub, stop rerunning the maze and use Badge Not Registering.
Route notes that remain useful
Use a compact entry for each attempt:
This note is useful even after a layout update because it states exactly which server state produced the result.
What is still unverified
Exact floor maps, clue counts and spawn points, puzzle orders, death persistence, monster detection rules, and the daily unlock minute still require current in-game confirmation. The Monster Schedule distinguishes confirmed identities from a reported rotation, while Updates records first-party changes.