Opens settings
Q key listed officially.
Database
Core systems that deserve dedicated tracking as sources improve.
A good wiki database is useful only when each entry explains what the item or system does, where it comes from, and why players care. These are the first tables this site should keep expanding as more verified data appears.
Officially listed in the description.
Need route landmarks and media proof.
Search evidence references 17 secrets; exact list needs verification.
Official description says more is coming; avoid premature claims.
Structured Wiki Data
Each row shows what is currently known, how strong the evidence is, and what still needs testing. This keeps the wiki useful without inventing game data.
Opens settings
Q key listed officially.
Movement/navigation
C key listed officially.
Movement speed
Left Shift listed officially.
Inspection and orientation
V key listed officially.
Long-tail exploration target
Route details should be validated against the current beta build.
Tracked as a core controls topic for this wiki. Details stay source-checked before they become ranked advice.
Tracked as a core areas topic for this wiki. Details stay source-checked before they become ranked advice.
Tracked as a core settings topic for this wiki. Details stay source-checked before they become ranked advice.
Tracked as a core work-in-progress notes topic for this wiki. Details stay source-checked before they become ranked advice.
Video Guide
Embedded for players who want to compare the written guide with live gameplay. Use the wiki text as the verified checklist and the video as practical context.
Open on YouTubePractical Playbook
Use the database page as the map of what deserves future detail. Every entry should eventually answer source, purpose, progression value, and the mistake players make with it.
Open the official Roblox page first and check whether the title banner or update date changed. If it did, treat old codes, rankings, and route claims as suspect until they are tested again. For Unseen Liminality, pay special attention to Exploration-first design because it anchors the rest of the wiki.
Keep one goal for the session: unlock a route, test a build, verify a code, find a secret, or compare a strategy video. Do not change three variables at once. If Controls affects the result, write that down before judging the method.
Record what actually changed: reward gained, zone reached, boss defeated, secret found, code accepted, or mechanic disproved. A useful wiki grows from repeatable notes, not vibes. Anything that cannot be repeated should stay in the research backlog.
The next best additions are exact names, unlock sources, reward amounts, and dated screenshots or videos. For now, this page publishes practical guidance and marks uncertain systems clearly so players are not sent chasing fake details.
Research Base
This wiki favors verified mechanics over filler. If a fighter, unit, weapon, pet, secret, entity, faction, skill, or code cannot be tied to an official page, in-game confirmation, or exact-match guide evidence, it is treated as unverified.