MULTIVOID

No. 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 it in your mod manager, and the game starts completely stock. The mod does write its own settings, logs and player data, next to the game and in your user folder; delete those too for a clean uninstall.

That's expected. The mod is a DLL that loads into the game process through UE4SS, the standard modding loader, and to a scanner that looks exactly like DLL injection, which is why so many game mods get flagged. You don't have to take my word for it: the source is public, so you can read it or build it yourself. Releases are built by GitHub Actions from that source, and each release's notes name the commit it was built from and print every file's SHA-256, so you can compare before running.

Multivoid's own server, master.multivoid.dev. It lists your lobby, serves the lobby list and the thanks list, checks for a newer version and introduces you to the host when you join. The same machine runs the STUN service that tells your game what its address looks like from outside, and the relay used when two players can't connect directly; relayed traffic stays encrypted end to end. Otherwise your game connects straight to the host. A connection you set up by hand in the settings file uses Google's public STUN server by default.

There are no analytics or tracking, and no account is needed. The servers keep ordinary connection logs.

Traffic between players is encrypted (AES-256-GCM), so someone listening on the network can't read your session, and traffic with the master server runs over TLS. Players 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. You can also put a password on your lobby.

What isn't there yet: there is no defence against an attacker sitting in the middle of the connection, since the connection-setup step isn't encrypted, and the host still takes some things a client says on trust. Closing those off is planned. For now, host only for people you know. To report a security problem, see SECURITY.md.

It's a listen server. Every client connects to the host and clients never talk to each other directly: the host runs the save, the NPCs and the events, and relays everything else, including each player's movement and voice. The master server lists lobbies and introduces players to a host when they join; it has no say in the game.

Only the host schedules events. An event isn't sent as one message: the creatures, weather and alarms it involves are each synced on their own, so clients see the host's event itself as it plays out. Joining mid-event works too: a joiner gets the host's save and a snapshot of whatever is happening at that moment.

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

The core design is adapted from MTA:SA, which has been adding multiplayer to a single-player game for twenty years. 125 files in the source name the precedent they follow, and where the design deliberately differs, the source says why. The work is in knowing which parts of that prior art apply to this game. The repository, its commit history, 31 public documents and the rules every change has to pass are all public.

No. Vibe-slop, or AI-slop, means accepting whatever a model writes without checking it, and that isn't how this is built. Every code change has to follow the project's written rules, pass its automated checks and run on a two-player test rig before it counts as done; the netcode question below has the details. The full history is public: over 3,200 commits since May 2026.

No. Multivoid started in May 2026 and adds multiplayer to a game that has been in development for five years and was never designed for it. Early builds of a project like that have bugs whoever writes the code. Bugs go away when they are found and fixed at the root cause, and that is what the process is built around.

If you hit a crash or a desync, please report it on Discord with your logs; several of the fixes credited below started that way. AI tools are a large part of why the project got this far this quickly.

Only with guardrails, and the project has them. Boris Cherny, who created Claude Code, said it on X: “Production code written by Claude should have a higher bar than if it was written by a human.” This project holds that bar in four ways:

• The rules are written down in CONTRIBUTING.md, for people and AI alike, and a script checks every rule a script can check.
• 12 automated checks run on every push to the main branch and every pull request. Two of them guard the network code directly: every reliable message type must reach a receiver on the other side or document why it doesn't, and every place that writes a player slot must declare whether the seat changed hands.
• A change isn't finished when it compiles. It runs with a host and a client on the test rig, and both logs are read. One race has a dedicated test so far: two players taking the same item at the same moment.
• Finished work gets audited. One audit of every hook the mod installs, prompted by another modder's note, found six defects nobody had reported, including one that let a client delete props the host still held. All six are fixed in the source and ship in the next release; the write-up is in the credits.