Stop using ai (or atleast not so much)

[thegmodfrog]

Using ai for 40% or more of the code is setting yourself up for failure, right now, the mod is buggy, it doesnt sync well, when i slip/my friend slips it crashes, make your own code so its not buggy, i have hope in this mod, but knowing that a large part of it is generated, sucks.

[pelmentor]

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. AI tools are a large part of why the project got this far this quickly.

[ComputerFritz]

As much as I'm sure this is the case, AI still leaves a bad taste in people's mouths regarding quality and performance. Plus, from my own play through of the game with 3 other friends it was nearly unplayable. I didn't think to grab logs due to just putting the mod down thanks to my bad experience, but will post them to the discord next time.

De-sync is really bad: Inventory duplication from the host as well as inventory deletion for clients, proximity chat being heard globally for some players while others are completely muted without any real cause, players becoming invisible but still able to interact with objects and entities (I have a clip of that one, kinda funny actually lol)
Maybe the mod wasn't designed with 4 people in mind but if so, a warning on the mod page would be better than nothing.

While its true that AI got the mod working very quickly, and the bare-bones version of the mod is actually awesome (using HL2 models for multiplayer characters is kinda funny). I would much rather it have more time in the oven WITHOUT AI even if it takes months between each update.

Not only would you gain more support from the fans of this game, but you could also have more people offer assistance or ability to QA each update to find bugs faster. Many people don't even want to try this mod due to Claude having over 1k more commits than the lead developer, "Vibe Coded" is the first thing people think of when they see this mod unfortunately.
(Almost ~1100 lines of code were posted EXCLUSIVELY by Claude between the 14th of June and 26th of July, according to https://github.com/VOTV-MP/Multivoid/graphs/contributors?from=5%2F16%2F2026&to=9%2F26%2F2026 )

A final note, the dismissive tone towards criticisms of AI wont do much to help gain public favor. Even if the project eventually shifts into a primarily human-coded mod. Many fans of VotV do very much want to have a multiplayer mod, but just saying "AI did it fast, so we can just deal with the bugs!" is flawed in many aspects. Instead, try taking the criticism as feedback and trying to find a middle ground at least.

[pelmentor]

@ComputerFritz smh, same useless "reeee ai bad reee" type of comment not far from the OP, alright I'll answer it. But first - the bug list.

Your session was almost certainly on b150: b208 came out few hours before your comment, 2,522 commits later. What you describe matches bugs other players had already reported, and here is where they stand:

• Inventory copied from the host, items vanishing for clients. A joiner's world comes from the host's save, and the mod put the joiner's own items where the game never reads them. So every joiner kept a copy of the host's inventory, item IDs included, and dropping one copy could delete both. Fixed in b208.
• Invisible players who can still interact. With three or more players, the host relays everyone's movement. A player who restarted their game and rejoined numbered their packets from zero again, and the other clients threw them away as older than what they had. That player stayed frozen or invisible for some people while the host saw them fine. Fixed in b208.
• Voice heard everywhere by some, not at all by others. Voice plays from the other player's body, so a frozen body puts it in the wrong place: that's the bug above. One case is still open: when your game has no body for someone at all, their voice plays at full volume everywhere.
• The slip "crash" from the first post. A slip could set off the game's own death sequence, which threw the player to the main menu and could end the session. b208 stops that.

If any of this still happens on b208, it's a new bug and I want the log.

@thegmodfrog your oven report (#28) is fixed in b208 too, thanks for filing it. The title alone was enough to find it.

The mod is built for four. Its page already says it's an alpha and that everyone playing it is a tester, and the invisible-player bug above, which needs three or more players, is fixed in b208.

On AI: the contributor graph is accurate, and there is nothing to uncover. Claude is on 3,675 of 3,738 commits because every commit made with it says so, as author or co-author. Until August 22 the tool committed under its own name, which is why the stretch you looked at shows almost nothing under mine. That's a label, not a split of the work: Claude and I are a day-to-day engineering pair. The direction, the architecture and the releases are mine, and I test the builds hands-on in the game myself. On top of that, a change isn't done until it passes the automated checks and runs on a two-player test rig with both logs read. Anyone who judges the mod by the graph alone is free to skip it. I won't hide the AI to win them over; hiding it would be the dishonest option.

"Without AI, even if it takes months" isn't a middle ground. It's the same bugs for longer: every fix above landed in the four weeks since b150.

Criticism that points at something I can change gets acted on, and the record is public. Two outside reviews of how the mod is built changed its whole foundation in b143, and both reviewers are credited by name: https://github.com/VOTV-MP/Multivoid/blob/main/docs/credits.md#review. When one of them later said the repo was half prose and hard for a human to read, the numbers agreed, and I spent a week cutting it down.

So no, I don't think it's dismissive: no criticism is being dismissed here. The parts of your comment with something in them, the bugs and the four-player point, are answered above. What's left is "AI bad", and that names no bug, no decision and no line of code. Taking that seriously, or calling it criticism, would be unfair to the people who send real reports. I'm not dismissing your session; I'm dismissing the idea that AI caused it.

Send the clip and your logs on Discord: https://discord.gg/bA6tGBvGMN. Reports, logs and code are welcome from anyone, and reporters are credited in the mod's main menu. That's what fixes bugs, whoever types the code.