MULTIVOID

It's a listen server. Every client connects to the host, and the host has the final say over the world, the save, NPCs and events. Players send their own movement and voice; everything else goes through the host, and clients never talk to each other directly. The master server lists lobbies and introduces peers to a host when they join — it has no say in the game itself, and once you are connected it is out of the loop.

Mostly no. Only the host schedules events, but an event isn't one message: the creatures, weather and alarms it involves are each synced on their own, so what a client sees is the event, not a re-enactment of it. Joining mid-event works too — a joiner gets the host's save and a snapshot of whatever is going on right now.

No, and that's on purpose. All gameplay still runs in the game's own code, which the mod calls into. Multivoid only decides who controls what and what goes over the network. It also means a game update doesn't force a gameplay rewrite, because there is nothing to rewrite.

One person, working extensively with AI coding tools. The direction, the architecture, the testing and the releases are mine; a lot of the code is written with Claude, which is in the credits below with its commit count next to mine.

I didn't invent the multiplayer architecture — I went and learned it. The core decisions are adapted from MTA:SA, which has been solving this for a single-player game for twenty years: 153 files in our source name the precedent they follow, and in 16 of them the source says why we deliberately did it differently. Knowing which parts of twenty years of prior art apply to this game, and which don't, is the work. The repository and its full commit history are public, along with 135 design documents and a categorised record of everything this project got wrong on the way. Judge the result rather than the method — all of it is there to check.

Prior art this owes thanks to: MTA:SA for the multiplayer architecture it follows, RE-UE4SS for the UE4 modding substrate its reflection algorithms were ported from (also the loader the mod runs under — the mod itself imports nothing from it), MinHook for hooking, and VoidTogether, the first multiplayer attempt for this game, which was useful to study while designing this one. Full credits are in the README.

Never. It doesn't edit the .exe, repack the .pak or touch any asset. The mod is a standard UE4SS mod folder: remove it, or uninstall in your mod manager, and the game boots completely stock. Its settings and logs live in a couple of folders next to the game — delete those too if you want a clean sweep.

Expected, unfortunately. The mod is a DLL that loads into the game process (through UE4SS, the game's standard modding loader), and to a scanner that looks exactly like DLL injection — this is why so many game mods get flagged. You don't have to take our word for it, though. The source is public, so you can read it or build it yourself. Releases are built by GitHub Actions straight from that source, with the workflow's hash pinned into a release fingerprint that ties the binary to its commit. And every file's SHA-256 is printed in the release notes, so you can compare before running.

Network-wise, the full list: our own master.multivoid.dev — to list your lobby, fetch the lobby list, check for a newer version, and to introduce you to the host when you join; and a public STUN server (Google's, by default — changeable in the config) which tells your game what its own address looks like from outside. STUN sees an IP and nothing else. After that it's a direct connection to the people you play with, unless your networks refuse to meet, in which case the traffic is relayed — still encrypted end to end. No analytics, no tracking, no account.

Traffic between peers is encrypted, so nobody reads your voice or chat off the wire. Peers now prove who they are before they get a seat — each side holds a signing key, and a joiner that can't answer the challenge doesn't get in — and you can put a password on your lobby. What is not finished is what happens after that: the host still takes some things a client says on trust, and closing that off action by action is the current work. Hosting for friends is fine; hosting for strangers is still a door you're leaving open.

We'd rather tell you where it actually stands than put a padlock icon on the page. How to report something you find is in SECURITY.md.