Players

Saturation Diving Community Hub

Discord, creators, events, and how to get involved — the social side of the wiki.

Last updated:

Saturation Diving Community — Discord Servers, Creators, and Events

This page is the community hub for Saturation Diving. Beyond the in-game squad coordination, the wiki tracks the Discord servers, content creators, wiki contributor channels, and seasonal events that keep the player base connected. Pair this with the official links page for the developer’s own channels and the updates tracker for the events calendar.

Discord Servers

Three Discord servers are worth joining as a new diver:

  • Official developer Discord — pinned channels for patch notes, bug reports, and role-specific chats. The invite link rotates with each major update; check the official Roblox game description for the current code. The wiki mirrors every announcement within minutes.
  • Community-run wiki Discord — the channel where wiki contributors coordinate content updates. If you spot a typo or want to suggest a new page, this is the place. Open to all divers, not just contributors.
  • Tier-council Discord — the volunteer-run channel where the tier list votes are tallied before each patch. Strictly for players who want to influence the meta. Membership requires a portfolio of 20+ public runs.

Content Creators

Three creator channels are worth subscribing to:

  • TheKacperosEN — long-form Saturation Diving walkthroughs, typically 30-60 minutes per video. The most thorough creator coverage of new zones and patches. Videos are uploaded within 24 hours of every patch.
  • BucketheadDev — the developer’s own channel, used for trailer drops and patch recap videos. Usually 5-10 minutes per video. The first place new mechanics are shown before they land on the wiki.
  • CyberHaptic Plays — first-look horror gameplay, focuses on the entity encounters and the scariness of the deeper zones. 15-25 minutes per video. Useful for spotting entity patterns before you push hadal zones.

Wiki Contributor Channels

The wiki is community-maintained. Three contributor channels are open:

  • #content — propose new pages, edit existing pages, request translations. Most wiki edits flow through this channel.
  • #translations — translate wiki pages into fr / de / es / id / vi / pt. The wiki tries to keep translations within 7 days of the EN update.
  • #tooling — request new wiki tools, file bugs against existing tools, propose widget improvements. The Dive Depth Calculator and Breathe Timer were both community-proposed in this channel.

Events Calendar

The wiki tracks an events calendar on the updates tracker page. Recurring events include:

  • Beta waves — every 6-8 weeks the developer opens a new public beta wave with a credit wipe. The wiki flags every wave 48 hours in advance and posts a credit-spending checklist.
  • Halloween event — late October, themed zones with limited cosmetic rewards. The wiki tracks the reward pool and the unlock conditions.
  • Anniversary wave — late August, celebrates the developer’s first launch date with double credit weekends and a free Cryo Helix Tank code.
  • Speedrun tournaments — community-run tournaments with credit prizes. The wiki posts signup links on the updates tracker.

How To Join The Wiki Contributor Pool

The wiki is open-source and accepts pull requests from any diver. The fastest path to becoming a contributor:

  1. Read the official links page to find the wiki Discord.
  2. Join the #content channel and introduce yourself with your main role and your strongest zone.
  3. Submit a small fix (typo, broken link, missing alt text) as a pull request. The wiki team reviews within 48 hours.
  4. After three accepted PRs, you get contributor role in the Discord and edit access to the wiki.

Most wiki contributors are divers who started by fixing a typo and stayed because they wanted better documentation for their main role. The wiki team is friendly to first-time contributors and walks you through the PR workflow the first time.

How To Suggest A New Page

Open a thread in the wiki Discord #content channel with the page name, the audience (new divers, mid-game, endgame), and a rough outline. The wiki team reviews suggestions weekly and prioritizes pages that complement existing hubs. Saturated topics (deep dives on a single mechanic) are usually accepted; broad overviews (general Saturation Diving tips) are usually redirected to existing pages.

How To File A Bug Report

Two channels for bugs:

  • In-game bugs — file on the developer’s Discord via #bug-reports. The developer reads every report and tags common bugs on Trello.
  • Wiki bugs — file on the wiki Discord #content channel. The wiki team fixes wiki bugs within 24 hours of the report.

The wiki tracks known in-game bugs on the updates tracker so divers can plan around them. If you find a wiki bug, file on the wiki Discord — the wiki team is separate from the developer and cannot fix in-game bugs.

Community Code Of Conduct

The wiki follows a simple code of conduct: respect all roles, no pay-to-win accusations without evidence, no tier-list brigading, no doxxing or harassment. Violations are flagged in the Discord and result in a temporary ban for first offenses. The wiki team maintains a public incident log on Trello for transparency.

How The Wiki Decides Meta Calls

The wiki tracks every meta call as a Trello card with public comments. When a patch drops, the tier-council Discord opens a vote on each gear slot; majority wins, minority opinions are recorded on the card. The wiki updates the tier list within 24 hours based on the vote. Divers who want to challenge a meta call should bring run data (ore-per-second under pressure, credit efficiency, role synergy) — votes without data are usually rejected.

Localized Community Channels

Each of the seven supported wiki locales has a community-run sub-Discord or Telegram channel:

  • fr — wiki-fr channel on the wiki Discord.
  • de — wiki-de channel on the wiki Discord.
  • es — wiki-es channel on the wiki Discord.
  • id — wiki-id channel on the wiki Discord, plus a Telegram mirror for Indonesian players.
  • vi — wiki-vi channel on the wiki Discord.
  • pt — wiki-pt channel on the wiki Discord, plus a Telegram mirror for Brazilian players.

The localized channels translate patch notes within 24 hours of every EN update and host regional speedrun tournaments. New divers in any locale should join their local channel first.

How To Stay Updated

Three ways to stay updated without checking the wiki daily:

  • Discord ping role — react to the wiki Discord #updates channel to get pinged on every patch. Most active option.
  • Email digest — the wiki publishes a weekly digest of patch notes and tier-list shifts. Subscribe via the footer contact form.
  • RSS feed — the wiki exposes an RSS feed at /feed.xml that mirrors every update. Add it to your RSS reader for a passive update.

The wiki tries to make every update reachable through at least one of these three channels. If you prefer a different update channel, file a suggestion in the wiki Discord and the team will consider it for the next wiki iteration.

FAQ

Frequently Asked Questions

Quick answers to the most common questions.

How do I join the wiki contributor pool?

Read the official links page to find the wiki Discord, join the #content channel, and submit a small fix as a pull request. After three accepted PRs you get edit access.

Where do I report an in-game bug?

File on the developer's Discord via #bug-reports. The developer reads every report and tags common bugs on Trello. Wiki bugs should be filed separately on the wiki Discord.

Are there localized community channels?

Yes — fr / de / es / id / vi / pt all have community-run sub-channels. Indonesian and Brazilian players also have Telegram mirrors of the wiki Discord channel.

How does the wiki decide tier list calls?

Trello cards with public comments. After every patch, the tier-council Discord votes on each gear slot; majority wins, minority opinions are recorded on the card. Votes without run data are usually rejected.

Can I host a community event through the wiki?

Yes. Open a thread in #content with the event name, date, and prize pool. The wiki team reviews events weekly and posts qualifying events on the updates tracker.