SubCargo Alpha Overview

SubCargo [ALPHA] on Roblox is DeltaCore Studio’s cooperative submarine delivery game in active development. The official description—visible on the Roblox game page—states plainly that the experience is in alpha and game-breaking bugs are to be expected. It recommends 2+ players, credits thumbnail artists, notes Barotrauma inspiration, and directs bug reports to in-game tools or the community server reachable through Roblox social links. This overview translates that warning into practical expectations so your crew enjoys playtesting instead of rage-quitting when ballast ignores pumps.

Alpha is a contract: you get early access to ocean-vein deliveries and Larry fights; developers get feedback on systems that are not finished.

What “alpha” means for SubCargo

In game development, alpha sits before beta polish—core loops exist, but stability and balance fluctuate. SubCargo already implements deliveries, dock shops (Underforge, ReCore, Krakken’s), crew roles, welding, fuel rods, and the Blood Worm nicknamed Larry. Missing polish shows up as UI confusion, inconsistent physics, and patch-day regressions.

You should expect:

• Features to change or disappear between builds.
• Stats documented on wikis—Larry HP, weapon damage, shop prices—to drift until balance locks.
• Sessions to end abruptly from bugs, not skill gaps.

You should not expect:

• MMO-level persistence guarantees for credits or unlocks.
• Final performance on low-end devices.
• Complete tutorialization of Barotrauma-grade systems.

Treat every run as data collection with friends, not a ranked ladder.

Video guide

Known pain points (community-tracked)

No public Trello is linked from this wiki, so pain points compile from official warnings plus community reproduction guides. Categories below mix confirmed alpha issues with setup checks—always try fixes before filing duplicate reports.

Ballast and flooding weirdness

Ballast troubles are the loudest alpha topic. Submarines may sink at neutral throttle, ignore pumps, or flood rooms despite welders online. Community troubleshooting suggests:

• Mark hull sections as ballast correctly, not generic rooms.
• Set neutral ballast near 0.5 where manual systems expose the value.
• Label pumps as ballast in wiring UI—mislabels break automation.
• Rebuild hull segments when logic refuses to update after edits.

If all checks pass and behavior persists across reboots, you likely hit a genuine alpha bug—report with reproduction steps on the community server or in-game tools.

Submarine systems and networking

Roblox server latency affects timing-sensitive tasks: welding during flooding, Larry hit registration, diver re-entry at depth. Crews on high ping should shorten callouts and avoid simultaneous exterior work during combat.

Systems interactions—fires, breaches, fuel timers—can cascade faster than alpha UI warns. Use the crew checklist to reduce cognitive load.

Economy and shop drift

Documented prices—$230 welder, $320 fuel rods, $750 PPS pistol—reflect community wiki snapshots at alpha 0.2.x. Silent hotfixes can change them. Re-read dock shops after patches before planning delivery routes.

Combat balance volatility

Larry’s ~300 HP and weapon TTK benchmarks come from developer comments and player testing. When APS joined in alpha 0.2.0 at $2120, economy shifted overnight. Re-test tier list assumptions frequently.

Patch mindset: how to survive alpha development

Before playing after an update:

1. Scan this hub and the community wiki for notes.
2. Dry-run ballast on an empty dock.
3. Confirm role spawn loadouts—engineer welder spawns matter for first purchases.

During sessions:

• Call bugs calmly; note map seed and player count.
• Save clips when floods or Larry behave impossibly.
• Prefer restarting broken subs over hour-long debugging in pub lobbies.

After sessions:

• File concise reports with version strings.
• Update personal crew strats when weapons or tools change.

Speedrunning blame on teammates before checking patch notes wastes alpha time.

How to give useful feedback to DeltaCore

Developers fix bugs faster with reproducible tickets. Include:

• Platform (PC, mobile) and input device
• Party size and assigned crew roles
• Exact sequence: “Undocked with two rods, Larry surfaced at minute six, hull damage continued after kill”
• Whether issue repeated on second attempt

Avoid all-caps “unplayable” without steps—alpha teams triage structured reports first.

Join the community server through official Roblox links; this wiki intentionally does not invent Discord invites because URLs rotate and unofficial links risk phishing.

What alpha players contribute

You are playtesters for:

• Co-op pacing — Is 2-player viable versus 4-player?
• Economy floors — Can crews afford minimum Larry kits after fuel?
• Tutorial gaps — Where does getting started fail new Barotrauma fans?
• Accessibility — UI readability, color contrast, control bindings on mobile.

Feedback shapes beta boundaries. Playing silently helps only your crew; reporting helps everyone.

Video context

The embedded video above shows typical alpha session flow—dock shopping, submarine handling, and the kind of emergent chaos alpha invites. Watch once with your crew, then discuss role assignments using linked wiki pages rather than treating YouTube as the only manual.

Enjoying the game despite bugs

SubCargo’s hook—delivering cargo through hostile ocean veins with friends—already works well enough to spike concurrent players during alpha peaks. Wipes from ballast glitches sting, but coordinated beat Larry moments create stories finished games chase.

Set session goals appropriate to alpha: “test new APS,” “learn ReCore fuel math,” “no rage quits,” not “100% completion.”

Related pages

• Updates Hub — reporting workflow and hub navigation
• Official Links — Roblox and Miraheze wiki URLs
• Crew Checklist — reduce chaos between bugs
• Dock Shops — economy reference post-patch
• Larry stats — combat numbers that change with balance