Updates

SubCargo Updates & Patch Notes

Alpha expectations, bug reporting, and where to track DeltaCore changes.

Last updated:

SubCargo Alpha Updates Hub

SubCargo from DeltaCore Studio is playable on Roblox in alpha—explicitly labeled SubCargo [ALPHA] on the official game page. That status is not marketing fluff; the description warns that game-breaking bugs are expected and asks players to report issues in-game or through the community server accessible from Roblox. This Updates hub collects patch mindset guidance, reporting workflows, and child pages like alpha overview so you know what early-access means before blaming your crew for ballast weirdness.

Fan wikis track community knowledge; DeltaCore ships the builds. Use both sources together after every patch Tuesday vibe.

What early-access alpha means here

Alpha is a development phase where mechanics, prices, and stability change frequently. SubCargo draws inspiration from Barotrauma—complex submarine systems compress into Roblox sessions—so bugs hit movement, welding, combat, and economy at once. You are playtesting live systems, not reviewing a finished co-op sim.

Expect:

  • Balance swings — weapon DPS, Larry health, shop prices adjusted without warning.
  • System glitches — ballast pumps, wiring labels, and hull flooding behaving inconsistently.
  • Progress resets — alpha saves or credits may not persist across major builds.
  • Content gaps — missing tutorials, placeholder UI, or undocumented features.

Do not expect launch-day polish. Do expect developers listening through official channels referenced on the Roblox page.

How to report bugs effectively

The official description lists two paths:

  1. In-game reporting tools when available in the alpha build you play.
  2. Community server linked from Roblox—join through the game’s social entry points rather than random invites; this wiki does not publish unofficial Discord URLs.

Strong reports include:

  • Build version (e.g., alpha 0.2.x if shown)
  • Player count and roles assigned
  • Steps to reproduce — “Larry surfaced during diver exit at X map”
  • Expected versus actual behavior
  • Clips or screenshots when possible

Vague “ballast broken” posts slow fixes. Mention whether pumps were labeled ballast, neutral values near 0.5, and if rebuilding hull sections helped—community guides document those checks because alpha issues mix user setup errors with real glitches.

Known issue categories (community-tracked)

Until patch notes publish formal lists, treat these as recurring alpha pain points mentioned across player guides:

Ballast and flooding. Submarines sink, bob, or ignore pumps despite seemingly correct setup. Workarounds include verifying ballast tank labels, neutral ballast values, and rebuilding affected hull sections when logic refuses to respond.

Combat desync. Larry damage or weapon hits may feel inconsistent under latency—Roblox servers vary.

Economy discrepancies. Shop prices and stock counts documented on wiki pages can drift after silent hotfixes.

Co-op coordination edge cases. Friendly fire, diver recall timing, and corpse aggro on Larry create wipes that feel like bugs but sometimes are intended alpha brutality.

Detailed context lives in alpha overview with video reference for first-time alpha players.

Patch mindset for crews

When a new build drops:

  1. Read overview notes here and on the community wiki.
  2. Re-test ballast on a quiet dock before ranked deliveries with friends.
  3. Re-verify dock shop prices before budgeting routes.
  4. Update personal crew checklists if role spawns change.
  5. Retry Larry TTK with your usual guns—balance passes happen.

Speedrun blaming your engineer before checking patch notes is an alpha tradition—avoid it.

Relationship to promo codes and content updates

When DeltaCore publishes Roblox promo codes, list them on the codes hub with expiry notes. Content updates—new weapons like the APS added in alpha 0.2.0—belong in patch summaries linked from this hub. Separate balance tweaks from content drops when writing notes so returning crews know whether to rerun tutorials.

Wiki maintenance policy

This fan wiki updates English JSON sources after verified community or official info changes. We run npm run verify before builds to catch broken links and SEO issues. If you see outdated stats post-patch, cross-check the community Miraheze wiki and submit corrections through our site channels if available.

We are not the official DeltaCore site—always trust in-game patch text first.

Start with Alpha Overview for a plain-language explanation of alpha expectations, ballast bug context, and how to enjoy SubCargo without treating every wipe as skill issue.

Then open Patch Notes 0.2 for community-tracked 0.2.0–0.2.2 content: APS pricing, Data Chips, weapon snapshots, and a post-build re-test checklist for fuel, ballast, and crane behavior.

FAQ

Frequently Asked Questions

Quick answers for SubCargo crews in Roblox alpha.

Is SubCargo fully released?

No. The Roblox page labels the experience as alpha and warns that game-breaking bugs are expected during early access development.

Where should I report bugs?

Use in-game reporting when available, or join the community server through official Roblox social links—avoid unofficial invite URLs.

Why does ballast break so often?

Alpha submarines combine complex physics with rapid development. Some issues are setup-related; others are genuine bugs—see alpha overview for checks before reporting.

How quickly does this wiki update after patches?

After verified notes appear from official or community sources. Always confirm in-game values immediately after a major build.

Will progress from alpha carry to future versions?

Not guaranteed. Treat alpha progress as testing data; DeltaCore may reset economies or stats between major milestones.