Creepy Jar shipped StarRupture Hotfix 0.2.4 on May 6, 2026 — a small but pointed patch targeting the two crashes most reported through the in-game Crash Reporter since Hotfix 0.2.3 went live two days earlier. It is the fourth hotfix in less than four weeks, all chasing the long tail of issues kicked up by Update 1, the early-access overhaul that landed on April 9. If you run a dedicated StarRupture server, the recent hotfix run is the part of the story worth paying attention to.
Release Date
Hotfix 0.2.4 went live on Steam on May 6, 2026 for both clients and dedicated server builds. No restart of your save is required. If you host a server, pull the latest server build via SteamCMD before your players log back in — co-op clients on an out-of-date host will crash on the same paths this patch closes.
What Hotfix 0.2.4 Actually Fixes
The notes are short on purpose. Creepy Jar called this one a "smaller hotfix" addressing the two most common crashes reported during the days following Update 1's progression rework. Both are co-op crashes — fitting for a patch that comes only 48 hours after Hotfix 0.2.3 spent most of its energy on multiplayer stability:
- Save-load crash after a lost Base Attack in co-op. If your colony was overrun while playing with friends, loading the resulting save could hard-crash the game. That path is closed.
- Progression rollback crash. A potential crash tied to
UCrProgressionRollbackEvent::Execute— the same rollback system that converts pre-Update 1 progress into Data Points — has been patched.
If you played the first week of Update 1 and saw "this crashes every time I reload" reports in your friend group's chat, this is the hotfix you were waiting for.
The Bigger Story: Hotfix 0.2.3 Did the Heavy Lifting
Hotfix 0.2.4 is a follow-up to Hotfix 0.2.3 from May 4, which is the patch that genuinely moved the needle for co-op and dedicated-server play. The full 0.2.3 list is dense, but the multiplayer-impacting items are the ones worth flagging if you run a server:
- Vulpir eggs now spawn correctly for clients in co-op sessions. Pre-patch, only the host saw eggs from Update 1's new wildlife — clients were quietly missing content.
- Large Personal Storage unlock requirements now count for clients, not just the host. Same pattern: progression silently broken on the non-host side.
- Foundation Platforms spawn correctly under buildings on placement, and platforms no longer deconstruct adjacent structures or float mid-air after a primary support is removed.
- Fire Wave aftermath is fixed. Infection no longer persists on save reload after the last cyst dies, gatherables like Ignitium spawn around you again post-wave, and the interaction prompts on those gatherables work.
- Pathfinding fix for enemies that lost track of players, plus a Vulpir VFX fix when shooting them mid-roll.
- Turret unlock logic now correctly delivers the Standard Ammo recipe alongside the Turret recipe in the Corporate Terminal — a small one but a real progression cliff before the patch.
Together, Hotfix 0.2.3 and 0.2.4 are the strongest signal yet that Creepy Jar is treating dedicated-server play as a first-class supported mode, not an afterthought.
What This Means for Your Server
If you run a StarRupture dedicated server, here's the practical checklist for the week:
- Update the server build before next session. Run
steamcmd +force_install_dir <path> +login anonymous +app_update 3809400 validate +quit. Both crashes patched in 0.2.4 affect co-op, and an outdated server will keep producing them. - Take a save backup before logging back in. Hotfix 0.2.4's progression-rollback fix is for a crash, not a data-loss bug, but the rollback system has been the source of multiple post-Update 1 issues — defensive backups cost nothing.
- Audit player progression on returning saves. Hotfix 0.2.2 retroactively unlocks pre-Update 1 buildings in the Development Station on save load; if you migrated a save from before April 9, confirm with your players that nothing they had built is locked behind a research wall they no longer have time for.
- Expect more hotfixes. The 0.2.x cadence — 0.2.1 (April 16), 0.2.2 (April 22), 0.2.3 (May 4), 0.2.4 (May 6) — is fast and explicitly crash-report-driven. Don't lock your group out of patches by pinning a server version.
- Dedicated server tooling is still rough around the edges. The community consensus is that StarRupture's bundled server tools work but require more babying than a polished release. A managed host removes the SteamCMD dance, the firewall-and-port-forward grind, and the "did the host or the client crash" diagnostic problem.
Recap: What Update 1 Actually Added
If you missed the April 9 drop and you're only now thinking about jumping back into Arcadia-7, here's the short version of what's in the build the hotfixes are stabilizing:
- New wildlife — Vulpir, Corallion, Skylisk — alongside the existing creatures. Vulpir is the one most often broken in co-op; the recent hotfixes specifically target its egg spawning and combat VFX.
- 40+ new items and recipes feeding new production pipelines and Corporation orders.
- Ziplines — placeable Zipline Poles let you build a personal travel network across your base and out into the new zones.
- Development Station — upgrades existing buildings to higher tiers (Large Habitat, Ore Excavator v.2, Orbital Cargo Launcher v.2).
- Expanded map with new playable zones and points of interest.
- Corporation Levels rolled back to 1. All previous progress was converted into Data Points that you redistribute through the Corporate Terminal — the system the May 6 hotfix patches a crash inside.
- Pistol moved off the Corporation reward track — it's now crafted at the Equipment Upgrade Station, and it drops on death along with everything else you're carrying.
That last point matters more than it looks: dying naked in StarRupture is now a real possibility, which means private co-op servers with friends are a much friendlier place to learn the post-Update 1 loop than public lobbies.
Worth Coming Back For?
If you bounced off StarRupture in the first week of Update 1 because of co-op desync or save crashes, this is the moment to come back. Two hotfixes in 48 hours plus three more in the prior two weeks is not the cadence of a studio sitting on its hands. The early-access roadmap is still front-loaded with stabilization, but the new content from Update 1 — the wildlife, the ziplines, the Development Station's tier-2 buildings — is real and increasingly bug-free.
Host Your StarRupture Server with DoomHosting
If you'd rather skip the SteamCMD grind, the firewall fights, and the daily hotfix-tracking, DoomHosting's StarRupture servers handle build updates, port forwarding, automatic backups, and DDoS protection so your group can just play. Instant setup, full FTP access, low-latency global locations, and 24/7 support — exactly the stack you want when the patch cadence is this fast.
Update 1 is finally settling. With Hotfix 0.2.4 closing the last of the loud co-op crashes, Arcadia-7 is the most stable it has been in a month. Get your group back online before the next wave hits.
