Prepare for disruption, not a memorized script. Enter a boss with a reliable damage plan, a way to recover or reduce pressure, and enough draw quality to function when the ideal sequence fails. Current public sources do not establish a fixed boss order or universal turn-by-turn solution.
Audit the deck before committing.
Can the deck close a long fight, or does it only clear ordinary encounters? Identify the repeatable damage or scaling line.
Know how the run survives a poor draw, sustained damage, or the loss of a key card. Food and healing must arrive when needed.
Ask what happens under discard, curses, status pressure, or a broken combo chain. A plan with no fallback is a gamble.
Then check deck size and stranded support cards. A card that only works beside one missing partner lowers the odds of drawing the sequence that actually keeps you alive.
What the current sources actually confirm.
Official launch material confirms two playable pathways with distinct cards, enemies, rewards, quests, and synergies. The Mysterious Facility is one of those routes and is associated with the Janitor, Gunk, Machines, and Data.
Official material does not publish a complete boss list, fixed route order, encounter-generation rule, or final-boss action script. Early Access content can also change after the public build checked here.
Two current runs reach very different endings.
| Run | Observed outcome | What it can teach |
|---|---|---|
| Zueljin Plays, Sep 10 | The Janitor/Facility run prepares for a boss around 01:10:48 and later ends under final-boss discard pressure around 02:25:53. | A functioning resource engine still needs a recovery plan when draw order or hand access is disrupted. |
| Dabble, Sep 12 | The creator's title describes an infinite deck followed by a one-shot final boss. | Loops and burst finishes are a current player goal, but the title does not prove repeatability or identify all required pieces. |
The videos may show different routes or bosses. They are useful as outcome cases, not evidence that one boss always discards cards or that every loop defeats every final encounter.
Watch the embedded Facility case Watch the embedded infinite-deck case
Build records are a research index, not a route guide.
An unofficial extraction for build 25221077 lists 46 encounter records. Some entries contain Boss labels or names such as Megashroom, Cubey, Mecha Shroom, and Gunk Worm. The same list mixes generic numbers, P02-prefixed records, and short placeholder descriptions.
Those records help identify what to verify in footage or the current game. They do not prove the name shown to players, the pathway, the encounter order, the normal availability pool, or a guaranteed action sequence. This page therefore does not convert the extraction into a full boss roster.
Read the fight one cycle at a time.
- Read visible intent and status text. Base the next play on what the current UI shows, not a remembered Demo pattern.
- Protect the engine's bridge. If one resource or card connects setup to payoff, avoid spending it without a replacement.
- Budget for interruption. Keep enough useful draws or recovery to survive a discard, curse, status, or missed combo.
- Track what changed. Re-check enemy states after a trigger, phase, summon, or reaction rather than assuming the previous action repeats.
- Choose the safe finish. A shorter line with verified damage may be stronger than extending an unproven loop.
These are decision prompts, not claims about hidden boss AI. Exact counters belong on individual boss pages only after the current encounter is verified.
What remains unverified.
- The complete current boss roster and the display name of each encounter.
- Boss order, map randomness, phases, reinforcements, and fixed action rotations.
- Whether the two referenced videos face the same final boss.
- Which of the 46 extracted encounter records occur in normal play.
- Whether any Demo-era counter or value still applies to build 25221077.
Sources and version notes.
Official: September 10 Early Access announcement, Team Lazerbeam's systems video, and the Steam store.
Build metadata: SteamDB public branch, showing build 25221077 when checked September 13, 2026.
Unofficial encounter index: NiaMeowDB encounters, used to identify verification targets rather than publish a complete current roster.
Player cases: Zueljin Plays and Dabble videos published in the current Early Access window. Neither is developer documentation or first-hand testing by this site.