Scapewatch Atlas

Combat and raids

Raid wave respawn

The delay before the next dungeon wave appears. The party's Alms respawn perks add up against one shared timer.

See it on the systems map

Rules and numbers

  1. confirmed The base is 10 s minus the sum of every party member's respawn reduction, with a 3 s floor.waveRespawn = max(3, 10 - sum(memberReductions)) (RAID_WAVE_RESPAWN_BASE, RAID_WAVE_RESPAWN_MIN)
    Source: Constants.js:4315-4324
  2. confirmed A clone contributes its host's reduction minus 1 s, so a host with no perks gives each clone +1 s.cloneReduction = hostReduction - 1 (RAID_CLONE_RESPAWN_PENALTY)
    Source: Constants.js:4325-4330
  3. dev note Solo combat uses its own timer: 8 s on task (16 s off), -1 s per Alms Mob Respawn tier (Alms 30/60/90/120) and -1 s per slate, with a 2 s minimum.soloRespawn = max(2, 8*(onTask?1:2) - almsTiers - slates)
    Source: Constants.js:2686-2695, 4898-4899, 2202
  4. dev note The 3 s raid floor exists so killing shots and the death animation can finish before the next wave lands.
    Source: Constants.js:4318-4322

Connected systems

Arrows show who acts on whom: → this system acts on the other, ← the other acts on this one, ↔ both do.

More in Combat and raids

Ancient and Chaos shards and slates · Chaos Dungeon · Combat · Combat styles and Life/Spirit · Corruption · Death · Delve (combat raid skill and tree) · Dungeons (tiered raids) · Fortify talent tree · Fortress (skilling raid) · Fortress Ledgers and Banners · Fortress rares · Slay masters · Slay tasks

Statuses: confirmed is a value or rule in the game files; observed is measured from recorded play; dev note comes from a developer comment, tooltip or patch note; inferred is worked out from the files with the assumption stated; unknown is decided on the server. Game data read 2026-10-03.