Mycopunk Threat Levels Explained: What Each of the Seven Tiers Actually Changes

Mycopunk has seven threat levels and one of them is a lie. "Safe" is a tutorial setting; the other six are a real ladder, and the jump from Treacherous to Deadly is where most builds break.

Since 2.0.2 removed the enemy intensity buttons — they had stopped working after the Freeze & Fester update — threat level is the only difficulty lever players control. That makes understanding the ladder more important than it was at launch.

The ladder

Regulated Rampage pays less at every tier — 65 / 82 / 98 / 114 / 130 / 140 — because it is a pure clear-the-hostiles mission with no objective work. Do not use it to level; use it to test a build.

What actually scales

The ladder is not a flat multiplier. Different things change at different tiers:

1. Enemy health scales steadily across all six.
2. Group size jumps at Perilous and again at Onslaught.
3. Elites start appearing at Treacherous.
4. Modifier severity increases — the same Horde modifier at Onslaught is a different modifier than at Perilous.
5. Respawn pressure at Onslaught and Predicament means a wipe costs the room, not the fight.

That ordering matters for build planning: health scaling rewards damage, but group size and respawn pressure reward area coverage and survivability. A build that only solves damage stalls at Deadly.

The Deadly wall

Threat 5 is where most players stop progressing, and the reason is almost always the same: they built a damage board with no movement or defensive layer. At Deadly the enemy count is high enough that you cannot kill your way out of a flank, so you need either:

• a movement option (Wrangler's three escapes, Bruiser's cubes, Scrapper's flight), or
• a defensive layer (Bruiser's shields, a healing primary on the team).

If you are stuck at Deadly, spend your next three upgrades on the second category. The meta builds page lists which loadouts pass that check.

Onslaught and Predicament

These two are different games.

Onslaught (6) is a density problem. Waves arrive continuously and the objective still has to be completed. Area damage wins — Gunship Cannon, Street Sweeper in a corridor, infection spreading through a group. Single-target builds underperform because the boss is not the threat; the crowd is.

Predicament (7) is a survival problem. Everything is on the table and mistakes are fatal. In practice this tier is where:

• Bruiser's Modular Construction build is the default,
• a second player is strongly recommended,
• support weapons (DMLR, Carver) stop being luxuries.

Solo Predicament is possible with a finished Bruiser board and a lot of patience. It is not a reasonable target for a new player at any level.

Which threat should you play?

The farming recommendation is deliberate: Treacherous gives 175 XP with manageable risk, and the farming guide explains why the XP-per-minute maths beats running Deadly and dying.

Modifiers and threat interact

Threat sets the baseline; the weekly modifiers decide the shape. Some combinations are effectively a threat level higher than they read:

• Bullet Hell + Horde at Onslaught is a wall for any build without shields.
• Sharpshooter + Fog punishes slow weapons and long sightlines simultaneously.
• Explodungus + Mitosis turns kills into traps, which is brutal for close-range shotgun builds.

Check modifiers before you pick a loadout, not after. The mission types page has the current modifier list and which archetypes each one punishes.

FAQ

What is the max threat level in Mycopunk? Seven: Safe, Risky, Perilous, Treacherous, Deadly, Onslaught, Predicament.

Does higher threat give better loot? It gives more XP and better drop rates, but the biggest jump is at Deadly, not Predicament. Farming Predicament for loot is inefficient unless you are clearing it comfortably.

Why did the difficulty buttons disappear? 2.0.2 removed the enemy intensity buttons because they had stopped working after Freeze & Fester. Swarm intensity is now dynamic and threat level is the only manual lever.

Can you change threat mid-run? No. Threat is set at deployment, which is why the modifier check has to happen before you commit a loadout.