Guides

Meltdowns in Tuantu's Lobotomization Branches

Choose which Qliphoth counter resets under time pressure — coordination wins facility days.

Last updated:

Meltdown Guide — Tuantu's Lobotomization Branches

What meltdowns are

Meltdowns are timed facility events in Tuantu’s Lobotomization Branches that force you to select which Abnormality has its Qliphoth counter reset. Pick correctly and the entity stabilizes; pick poorly or fail the timer and the Abnormality breaches — becoming a mobile threat until suppressed with E.G.O weapons. Meltdowns appear throughout normal days, during Ordeals, and inside Core Suppression gauntlets.

Meltdowns are the highest-leverage decision in the daily loop. One panic click on a WAW cell during a HE breach cascade ends more runs than Ordeal add waves.

Qliphoth counter reset mechanics

Each enabled Abnormality maintains a Qliphoth counter — successful works usually stabilize or reduce pressure; failures and passive abilities chip counters toward zero. Meltdowns interrupt normal work by demanding an immediate reset choice.

When meltdown UI appears:

  1. Scan listed cells and current counter values.
  2. Identify which Abnormality is mid-work or closest to breach.
  3. Avoid resetting high-risk boxes with active agents inside unless no alternative exists.
  4. Confirm choice with team via middle-click ping before clicking.

Encyclopedia (J) shows counter depths per entity — memorize your enabled roster.

Meltdown pick priority framework

Use this priority ladder — adjust for live breach status:

Tier 1 — Active breach or suppression objective. Any breaching ALEPH, WAW, or Core Suppression target beats optional PE farms.

Tier 2 — Corridor hubs. Cells whose breaches block elevator or stair routes between departments — especially near HE wings with v0.9 elevator cooldown — see HE Guide.

Tier 3 — Mid-work high risk. Agents currently inside HE or WAW boxes when counter hits one.

Tier 4 — Stable low risk. ZAYIN or safe TETH cells with agents evacuated and counters above two.

Document which tier your team dies to — gear gaps versus discipline gaps require different fixes from Extract E.G.O or How to Play.

Meltdown overload in v0.9.1

Version 0.9.1 introduced meltdown overload — approximately +2% HE spawn weight during meltdown events. Overload means meltdown windows more frequently pressure HE-tier cells even when your enable plan targeted TETH stability.

Overload implications:

  • Pre-position suppressors near HE doors before meltdown timers appear.
  • Avoid enabling new HE boxes on days with heavy Ordeal overlap — Ordeals Guide.
  • Budget extra time for meltdown picks — HE breaches take longer to suppress than TETH.

Read full balance context in Patch v0.9.1.

Team coordination protocols

Multiplayer meltdowns fail from double-clicks and silent picks. Standardize callouts:

  • “Meltdown north HE” — proposed pick with location.
  • “Wait — agent inside” — veto until evacuation.
  • “Confirm click” — caller only clicks after second ping ack.

Owners may /ann meltdown caller role at day start — Owner Commands.

Solo private servers: verbalize picks anyway — builds habit for public lobbies.

Meltdowns during Ordeals

Ordeals do not pause meltdowns. During simultaneous events:

  • Assign separate players for Ordeal suppression and meltdown calling.
  • Clear Ordeal adds blocking the path to meltdown target cell if necessary.
  • Prefer meltdown picks that do not spawn breaches into active Ordeal lanes.

Dusk Ordeals plus meltdown overload is the most common v0.9 wipe combo — slow PE pacing when counters are unstable.

Meltdowns during Core Suppression

Core Suppression uses stricter meltdown priority than normal days — see Core Suppression and Binah Core Suppression. During suppressions:

  1. Suppression objective cell beats PE farm.
  2. Elevator hub connectivity beats wing rooms.
  3. Ping before click — double picks lose more time than controlled ZAYIN breach.

Practice meltdown discipline on HE days before attempting Sephirah suppressions.

Work Helper integration

The wiki Work Helper tool tracks mood outcomes and suggested next work types per Abnormality. Use Work Helper between meltdowns to:

  • Plan counter-stabilizing works before next meltdown window.
  • Avoid chaining risky Insight jobs on agents with low Prudence.
  • Cross-reference TETH Guide and HE Guide entity notes.

Work Helper does not replace ping coordination — it informs picks, not team communication.

Fear and Sanity during meltdowns

Fear spikes when agents witness meltdown breach telegraphs or high-tier mood screens. Sanity drops during Insight-heavy cells selected for reset. Mitigate with:

  • V carry clerks away from meltdown halls — Keybinds.
  • G stims on tanks holding breach doors.
  • Rotating Insight agents after meltdown-stabilizing works.

High Fear reduces work success on the next meltdown cycle — break the loop with department regeneration tiles.

Risk tier meltdown differences

TierMeltdown riskTypical pick strategy
ZAYINLowSafe default when team agrees
TETHMediumAvoid mid-Attachment chains
HEHighEvacuate agents before reset
WAWSevereSuppression team on standby
ALEPHCriticalOften pick only with full team focus

Graduate through Risk Levels before enabling upper-tier boxes.

Practice routines

Improve meltdown discipline without griefing public lobbies:

  • Owner /resetday cycles focusing only on meltdown windows.
  • Enable one new box per wing with ping rules.
  • Log picks that caused breaches in Discord notes for team review.
  • Run LOB Planner so stat gaps do not masquerade as pick errors.
FAQ

Frequently Asked Questions

Quick answers to the most common questions.

What happens if I fail a meltdown timer?

Failing the meltdown timer or picking a dangerous cell causes the selected Abnormality to breach. Breaches require E.G.O suppression and raise Fear across nearby employees.

What is meltdown overload in v0.9.1?

Meltdown overload adds roughly +2% HE spawn weight during meltdown events. Expect more HE-tier pressure during meltdown windows — pre-position suppressors near HE doors.

How should teams coordinate meltdown picks?

Assign one meltdown caller, propose picks via ping, and confirm before clicking. Double-clicks waste more time than controlled lower-tier breaches.

Does the Work Helper tool replace team callouts?

No. Work Helper suggests work types and mood planning between meltdowns. Team ping coordination remains mandatory for pick confirmation in multiplayer.

Which Abnormality tier is safest for meltdown picks?

ZAYIN and stable TETH cells with evacuated agents and counters above two are safest defaults. Avoid resetting active HE, WAW, or ALEPH boxes unless no alternative exists.