Saturation Diving Autofarm Scripts

This page is the autofarm and companion scripts guide for Saturation Diving. The game is in beta and the developer does not officially endorse third-party tools, but a community of companion scripts has emerged that automate the boring parts of credit farming without touching game state. The wiki tracks the most-used scripts here and flags any that risk account action.

How Companion Scripts Work

Companion scripts in Saturation Diving run in a side window and read the public in-game HUD (oxygen, sonar ping, entity proximity) to give you faster reaction times. They do not inject packets, modify game state, or automate character movement — the latter would be a Roblox ToS violation and the developer has banned accounts for it. The legitimate scripts fall into three buckets: HUD overlays, keyless macros, and route planners.

• HUD overlays — read your oxygen meter and pop a desktop notification when you cross 30%. The wiki’s Breathe Timer is a reference implementation that runs in the browser without any external tool.
• Keyless macros — bind a single key to a sequence (Q to drop ore at the cargo bay, R to call the submarine back). These are not automation — they are keybinding shortcuts.
• Route planners — calculate the optimal pipe-mining order for a given zone. The wiki’s Dive Depth Calculator is a manual implementation; third-party planners automate the same math.

Roblox: Saturation Diving — first video walkthrough

Autofarm Routes

Three autofarm routes are widely used:

• Twilight Reef circuit — solo Captain runs the surface pipe cluster in a fixed loop, banking every 9 minutes. Average credit yield: 1,200 credits per loop with the Salvaged Glowstick + Reefwalker IV starter set.
• Mid Ridge two-cluster — Captain + Engineer pair runs the upper cluster, surfaces, then runs the lower cluster, surfaces. Average credit yield: 3,800 credits per cycle with mid-tier gear.
• Black Mound salvage — full four-role squad runs a single Black Mound loot run. Average credit yield: 8,500 credits per run with the Triton Mark VII + Salvage Multiplier build.

The wiki tracks the average yield per route per patch on the updates tracker. Routes get nerfed or buffed by zone rebalances, so check the tracker before committing to a route.

Credit Farming Builds

Three credit farming builds are most efficient per squad size:

• Solo Captain, Twilight Reef — Captain + Reefwalker IV + Salvaged Glowstick + Standard Tank. Use the wiki’s Breathe Timer to manage oxygen. Expected credits: 1,200 per loop.
• Duo, Mid Ridge — Captain + Engineer with Cryo Helix Tank + Hydraulic Core-Bit. Use the wiki’s Dive Depth Calculator to plan depth. Expected credits: 3,800 per cycle.
• Full squad, Black Mound — full four-role meta with Triton Mark VII + Salvage Multiplier. Expected credits: 8,500 per run.

All three builds assume the player is perk-optimized for their role. Sub-optimal perks drop credit yield by 15-30%.

Keyless Macros

Three keyless macros are commonly used:

• Q + R combo — bind Q to “drop ore” and R to “call submarine”. Saves 2-3 seconds per surface cycle.
• Hold-to-mine — bind left-click hold to a single key (F). Saves finger fatigue on long Black Mound runs.
• Sonar ping cycle — bind a single key to cycle between Mk I, Mk II, Mk III sonar modes. Saves time during zone transitions.

The wiki does not endorse any specific macro tool because the developer has not blessed any. Most divers use the Roblox Studio macro tool or a third-party AutoHotkey script. Neither modifies game state, so neither is a ToS violation.

Safety Checklist

Before installing any companion script:

1. Verify the source — only use scripts from public repositories with active maintainers. Avoid closed-source scripts from Discord DMs.
2. Check the permissions — the script should not ask for Roblox account credentials or admin privileges on your machine.
3. Run in a sandboxed VM if possible — even trusted scripts can have bugs. A VM keeps your main machine clean.
4. Watch for false positives — Roblox’s anti-cheat is aggressive and can flag legitimate companion scripts. If your account gets a strike, file an appeal on the developer’s Discord.

The wiki tracks banned-script reports on the updates tracker so divers can avoid scripts that have triggered anti-cheat flags.

Tools The Wiki Provides

Two built-in browser tools cover the most common use cases for companion scripts:

• Dive Depth Calculator — replaces most third-party route planners. Runs entirely in the browser, no install.
• Breathe Timer — replaces most third-party HUD overlays. Runs entirely in the browser, no install.

If you find yourself reaching for a third-party tool that does what one of these already does, the wiki-built tool is the safer choice — same functionality, no risk of an anti-cheat flag.

Anti-Cheat Notes

Roblox’s anti-cheat (Byfron + Hyperion) is aggressive. Three patterns trigger false positives:

• Packet-level automation — any tool that sends inputs faster than humanly possible.
• Memory reading — any tool that reads the game’s memory to gain an advantage (entity HP, ore positions, etc.).
• Process injection — any tool that injects DLLs into the Roblox client process.

All three patterns are Roblox ToS violations and can result in a permanent ban. The wiki flags them clearly. Companion scripts that avoid all three patterns (HUD overlays, keyless macros, route planners) are not flagged because they do not modify game state.

Where To Find Scripts

The wiki does not host scripts directly. Three public repositories host the most-used companion scripts:

• GitHub topic “saturation-diving” — open-source companion scripts with permissive licenses. The wiki recommends this as the safest source.
• Roblox script community forums — community-rated scripts with public comments. Quality varies; check the rating before installing.
• Developer Discord #scripts channel — pinned scripts from the developer-approved community. Highest trust but smallest catalog.

Avoid closed-source scripts from random Discord DMs, YouTube descriptions, or TikTok comments. The wiki has flagged every such script that triggered anti-cheat bans on the updates tracker.

Beta Wipes And Script Compatibility

Every beta wipe can break companion scripts because the game client changes. The wiki tracks script compatibility on the updates tracker within 24 hours of every wipe. If your script breaks after a wipe, check the script’s GitHub issues first; most maintained scripts get patches within 48 hours of a wipe. Closed-source scripts often take weeks to recover — this is the main reason the wiki recommends open-source only.

How To Report A Broken Script

If a script breaks after a patch, file a bug report on the script’s GitHub issues (or Discord, if no GitHub). Include the patch version, the script version, the broken feature, and a screenshot if possible. The wiki maintains a public compatibility matrix on Trello that scripts maintainers consult before pushing patches; reporting in public speeds the fix.