Saturation Diving Expired Codes Archive
Every dead code, the reward it granted, and when it expired — so you know what to ignore.
This page is the archive of expired Saturation Diving codes. Saturation Diving is in beta and the developer has not yet shipped a public code wave, so this archive is empty for now. Once the first wave drops and ages out, every dead code will land here with the reward it granted and the date it expired, so you know which strings to ignore and which ones the wiki flagged prematurely.
Why Track Expired Codes
Three reasons we keep this page even when empty. First, players regularly search for old codes they remember from a creator video — those searches land here instead of dead-ending on the active codes page, which keeps the live page clean. Second, when codes return for a milestone event (Halloween, anniversary wave, beta reset) the historical record lets us quickly verify that the same reward string is shipping, not a new one. Third, the timestamp column gives the wiki a single source of truth for “we marked this dead on day X” — useful when a player asks why a code was removed.
What Goes Here
Each row in the archive will record four fields: the code string (exact case, including hyphens), the reward granted at redemption, the date the wiki marked it expired, and a short reason for expiry (event over, beta wipe, region-locked, replaced by a better code). Once a row ships it stays on this page forever so the audit trail is preserved. If the developer re-uses a string later, we add a new row with the same code and a fresh timestamp instead of editing history.
How to Spot an Expired Code
In-game, expired codes trigger the “This code has expired” toast with a sad submarine icon. Some codes that the developer removed from rotation still print “Code not found” instead of the expired toast — the wiki lists both responses in the expiry reason column so you can pattern-match. If you copy a code from a creator video and the wiki says it is expired but you get a “not found” toast, that usually means the developer pulled it faster than the wiki could update; file a report via the footer so we can flag the discrepancy.
Reporting a Dead Code
If you try a code the wiki lists as active and it returns expired, open the contact channel in the footer with the exact code, the toast text, and the time you tried. We verify against the developer’s Discord pins before moving the code to this archive page, so the active list stays trustworthy. Reporting takes about 30 seconds and saves every other diver from wasting a redemption attempt.
Re-Released Codes
Developers sometimes re-issue a code string after a major patch, especially after beta wipes when they want returning players to feel welcome. The wiki treats a re-release as a brand new code: it returns to the active codes page, the old entry stays on this archive page with a note that the string re-surfaced, and a fresh expiry timestamp is recorded the next time it ages out. This pattern means the archive can hold multiple rows for the same string over the lifetime of the game.
Beta Wipes and Code Carryover
Beta wipes typically invalidate reward items but not the redemption ledger, which is why we keep this archive independent of the in-game inventory. After the next beta wipe, come back to this page to see which rewards you can re-claim by re-redeeming an active code. The wiki tries to mirror the wipe schedule on the updates tracker within an hour, so check both pages together when a wipe is announced.
Why Beta Games Delay Codes
Developers usually wait until the save system, anti-cheat, and reward inventory are stable before exposing code redemption. Beta builds can lose progress during wipe events, and shipping a code that grants a non-recoverable item would create support headaches. Our updates tracker logs every wipe so you know when it is safe to invest in upgrades versus when to bank rewards for the next season. Until the first wave lands, this archive exists in skeleton form — every row from now on will be filled with a real string, real reward, and real timestamp.
What To Do With Old Codes
If you find an old code from a screenshot or a creator video, do not waste a redemption slot on it. Cross-check this archive first, then check the active codes page, then ask in the developer’s Discord. If all three say the code is dead, treat it as dead and report it to the wiki so we can update the archive. The wiki prefers to be conservative — we move codes to expired when we have two independent signals (Discord pin plus an in-game toast screenshot), never on a single rumor.
Frequently Asked Questions
Quick answers to the most common questions.
Is there any way to use an expired code?
No. Expired codes are removed from the developer's redemption server. If a string re-surfaces for a milestone event, the wiki treats it as a brand new code and adds it back to the active page.
Why does this page exist if there are no expired codes yet?
Because the moment the first wave ships, every dead code needs a permanent home. Keeping the archive ready now means we can move codes within minutes of expiry instead of scrambling to design the page after the fact.
Who decides when a code is moved here?
The wiki maintainers, after verifying the code against the developer's Discord pins and (when possible) an in-game toast screenshot. A single rumor is never enough — we wait for two independent signals.
Does the archive reset after a beta wipe?
No. The archive is independent of the in-game inventory, so the audit trail survives every wipe. Re-issuable codes get a new row instead of editing history.