Skip to content

Releases

v0.5.5-alpha — fixes 'connected, but nothing updates live'

Choose a tag to compare

@BayneBuild BayneBuild released this 01 Aug 23:16

If live sync isn't working for you but reloading the vehicle shows your partner's changes, this is the fix. Update both machines.

What was wrong

When a block arrives from your partner, the mod sometimes can't place it immediately — it needs a template of the part and a body to attach it to, and on a fresh workbench neither may exist yet. So it holds the block instead of dropping it, which is right.

What was wrong is when it tried again: only when you placed a block yourself. So a partner's blocks could sit in the queue indefinitely, and the only way to release them was to place something of your own — which nobody would ever guess.

The result looks exactly like sync being broken: nothing appears live, no error, but the craft is correct after you reload the vehicle (because re-entering the bench pulls the whole craft, and that path always worked).

Held blocks now retry every second. The conditions that cause a hold resolve on their own, so retrying is all that was needed.

Reported by a user who described it precisely enough to identify — "I got it to connect with another client, but nothing is updating live. To see changes, I have to reload the vehicle" — where the reload detail is what separated a live-path bug from a network one. Thank you.

If you're still stuck after updating

Press F8 in game for the log. On the machine that's placing, look for <detect> add. On the machine that should be receiving, look for <<< APPLIED. Which of those appears tells you where it stops:

  • no <detect> — your edits aren't being seen at all
  • <detect> but no <<< APPLIED on the other side — it's the network
  • both present but nothing on screen — it's the visual rebuild

Also worth checking: if you're both in the same Stormworks multiplayer session, the game itself replicates that vehicle and the host is the authority, which can fight the mod. It's designed for two people in separate worlds, connected over Steam.

Everything else is unchanged from v0.5.4-alpha.

v0.5.4-alpha — first real two-machine session, and it worked

Choose a tag to compare

@BayneBuild BayneBuild released this 01 Aug 05:17

Everything added since v0.2.2-alpha had only ever been tested solo. This is the first two-machine session on that work — the project has had plenty of them, but not on any of this. It held up: live sync on a 471-component / 42 KB craft, four whole-craft pulls served cleanly, automatic pairing, the partner camera marker, and presence tracking across bench entry and exit. There is footage on the README now.

Two fixes from that session

Both were the same mistake — the mod knew exactly what was happening and told the wrong audience.

F7 is one press again. The confirmation prompt was being drawn through the error path, so "are you sure?" rendered as a red SYNC FAILED banner. The tester reported F7 as erroring while it was in fact working perfectly. The confirm is gone entirely: F7 is the thing you reach for when sync looks wrong, so putting a hesitation in front of the recovery action was backwards.

"Your partner built while you were away — press F7 to catch up" now appears on screen. Edits are not sent at all while you are outside the workbench, so on re-entry there is nothing queued to replay and F7 genuinely is the only way to catch up. The mod detected this precisely and wrote it to the log file, which nobody reads mid-session.

The sync banner now carries three meanings instead of two: red failed, amber a question or a heads-up, blue in progress. Previously anything that was not blue was red.

Also

  • Quitting with Alt+F4 races Steam's own shutdown and faults inside steamclient64.dll before the mod is even active. Harmless, but it was raising PREVIOUS SESSION CRASHED on the next launch — noise that trains people to ignore the one warning that matters. It is now recognised and marked benign.
  • The uninstaller clears coop-peer.txt and the other config files. A leftover one is not a saved preference, it is a trap: it pins your partner and switches auto-discovery off, so a reinstall silently pairs you with someone who may have stopped playing.

Still known-broken

  • A partner's microcontroller arrives carrying yours (#11) — press F7 after either of you places one.
  • An F7 pull can land the craft offset (#12) — root cause found, fix in, not yet confirmed.

Component-settings sync ran live throughout the session from the sending side; whether it landed has not been confirmed from the receiving machine's logs yet, so it stays marked as unproven.

v0.5.1-alpha — auto-connect no longer disables itself

Choose a tag to compare

@BayneBuild BayneBuild released this 01 Aug 03:50

Point release on top of v0.5.0-alpha — read those notes too, they cover component-settings sync and the two severe known bugs.

Auto-connect disabled itself after its first success

When automatic discovery found a partner, it wrote their SteamID into coop-peer.txt. Any ID in that file switches discovery off — so one successful auto-connect became a permanent pin to that person, and the mod never looked for anyone again, even after they stopped playing.

Compounding it, "connected" came from Steam's accept call returning true. That registers your own willingness and succeeds with nobody on the other end. So a stale pin reported a live partner indefinitely while every message queued into the void.

Found because the overlay claimed a partner when nobody else was running the mod at all. The log showed hundreds of sends "succeeding" and not one inbound message.

  • An adopted partner is now session-only. coop-peer.txt goes back to meaning only "I chose this person", never "the mod chose for me, permanently".
  • "Connected" now requires a message to have actually arrived.

If you were on v0.5.0 or earlier and it ever paired automatically, delete coop-peer.txt from your plugins folder — an old pin will otherwise keep overriding discovery.

Also

  • The uninstaller no longer deletes dinput8.dll. The installer deliberately keeps a pre-existing one, since another mod may own that loader — so uninstalling could silently break someone else's mod. It also no longer deletes your config, so a reinstall keeps your pairing.
  • Corrects two overstatements in the README: bench-mismatch refusal has never actually run between two machines, and automatic pairing had less real testing than the logs suggested — the stickiness above meant later launches were reading a file rather than discovering.

v0.5.0-alpha — component settings sync, and two root causes

Choose a tag to compare

@BayneBuild BayneBuild released this 31 Jul 05:15

Everything new in this release is solo-tested only. It has not yet been run between two machines. That's the honest headline — the rest of this is what changed and what's still broken.

Component settings now sync live

Sliders, names, logic constants and microcontroller internals stream between players. This was the biggest limitation the README has admitted since the first release.

If a setting doesn't appear on your partner's screen, press F7 — the whole-craft pull remains the cure for any desync. To turn it off, create coop-noprops.txt next to the mod.

Two known bugs, both severe

A microcontroller placed by your partner arrives wrong. Not merely empty — it arrives carrying whatever microcontroller you currently have selected, at that one's size. Press F7 after either of you places one, and don't build against an MC's faces until you have.

An F7 pull can land the craft offset. Root cause is now understood and the fix is in, but it hasn't been confirmed with a real partner.

Two root causes found

Craft position is three fields, not one. poff (carried by the save), a float64 master in the editor, and the rendered anchor. The game never loads the anchor — it reconstructs it, in a block appearing verbatim at four call sites. We ran none of it, so a pulled craft was displaced by exactly the difference between the two players' offsets — and identically zero on one machine, which is why it never reproduced in solo testing.

The wrong body. Every block belongs to a body; a hinge or pivot makes a new one. When forging a partner's block we read a field believed to be "the hovered body". It's the local player's cursor cell — nothing to do with where your partner placed anything. A wrong body writes both the parent pointer and the body id, so the craft renders correctly and is structurally wrong. Partners now send the body id and the receiver resolves it through the game's own lookup.

Install

Run install.bat — it finds your Stormworks folder, shows exactly the two files it will copy, and asks first.

Or do it by hand, which some people reasonably prefer: drag dinput8.dll next to stormworks64.exe, make a plugins folder, drag coopworkbench.asi into it. That's exactly, and only, what the installer does. Delete those two files to uninstall, either way.

No injector, nothing to run each session, and no Windows Defender prompt.

Also new

  • In-game log viewer on F8 — scroll, jump, filter. Reading a log no longer means leaving the game.
  • Crash reporter — writes the faulting address, what the mod was doing, and the tail of the log to one file with no SteamIDs in it. Please attach it to bug reports.
  • Stuck warning markers fixed — they were the game's own UI widgets being duplicated on every craft load.
  • A memory leak fixed in the whole-craft pull; it had been leaking the previous craft every sync.
  • Startup display, a readable font, and calibration keys that no longer fire during normal play — F7 was also teleporting the overlay lattice on every press.

Reporting

coopworkbench-log.txt from both machines, plus coopworkbench-CRASH.txt if there is one. Strip the 17-digit SteamIDs first. Say what each of you saw separately — "it didn't sync" is usually two different stories on the two screens, and the difference is the clue.

Bundles Ultimate-ASI-Loader (MIT, unmodified); licence included.

v0.2.2-alpha - whole-craft sync, co-op/solo entry, partner cursor

Choose a tag to compare

@BayneBuild BayneBuild released this 31 Jul 05:37

Whole-craft sync (F7) - pull your partner's entire build in one shot: blocks, colours, wires, microcontrollers and settings. Also the universal cure for any desync, and the mechanism behind joining mid-build.

Co-op vs solo entry - the workbench prompt becomes START CO-OP / JOIN PARTNER, and Q opens the bench solo, syncing nothing. First player in is the source of truth.

Partner cursor - the exact cell your partner is hovering, alongside their camera marker.

Bench matching - build volumes are compared, so two players at different-sized benches are caught rather than half-syncing.

Wire disconnect sync, and logic connections confirmed working (#7).

Confirmed across multiple bench types and inside a shared multiplayer session.


The download has been removed from this release. It used the injector-based install, which is retired and no longer works; the zip also contained a developer-only script and a stray config file that should not have shipped. Get the latest release instead.

The tag is intact, so the source at this point is still browsable and checkout-able.

These notes were reconstructed from the commit history; the originals were lost when the release was deleted.

v0.1.0-alpha - first public release

Pre-release

Choose a tag to compare

@BayneBuild BayneBuild released this 31 Jul 05:37

First public release of Coop Workbench.

Real-time collaborative building in the Stormworks vehicle workbench over Steam peer-to-peer: place, delete, paint, rotate and wire together, with your partner's camera drawn in the bench. Shipped as a single DLL with the world-space overlay merged in, loaded by a per-session injector.


The download has been removed from this release. It used the injector-based install, which is retired and no longer works. Get the latest release instead - it copies two files and loads with the game, with no Defender prompt.

The tag is intact, so the source at this point is still browsable and checkout-able.

These notes were reconstructed from the commit history; the originals were lost when the release was deleted.