Message 1/2
Dear Barotrauma Developers (FakeFish & Undertow Games)!
I’m a passionate fan of your game, which has become a true masterpiece of cooperative horror and underwater survival sim beneath Europa’s ice. Since the full release in 2023, I’ve spent hundreds of hours in Barotrauma: from solo campaigns commanding a full crew of bots, to multiplayer sessions with friends on modded servers. Your game isn’t just a project—it’s a living ocean of chaos, where every leak, every husk attack, or traitor betrayal creates unforgettable moments. You’ve created something unique, with deep lore, crafting mechanics, and AI that makes bots feel like real “hands” for the player.
But here’s the painful issue that keeps thousands of players (including me) up at night: why can’t bots be used in multiplayer the same way as in single-player? In solo, I can switch between bots (switch control), directly manage them, customize talents, gear, and force them to craft masterwork fuel or repair the reactor mid-attack. It makes the game dynamic, strategic, and accessible for solo players—I can play anytime, without friends, and feel like the captain of a fully crewed submarine.
In multiplayer? Bots are half-dead weight: they obey orders (sometimes), but you can’t switch to them without cheats (F3 + “control” or “setclientcharacter,” which disables achievements), can’t conveniently manage talents (only via Tab-click, without full control), and can’t tweak inventory or force crafting with talent bonuses (+1 quality for players). With 2–3 friends on a large sub (like the Berilia), we can’t cover all roles: the mechanic can’t weld fast enough, the medic can’t heal, and bots just get stuck on ladders or forget to charge batteries in the turret. The result? Frustration, failed missions, and a retreat back to solo.
(Continued in the next message)
#Bring Full Single-Player Bot Control to Multiplayer–Unlock Hybrid Co-op for Everyone
azure talon
Message 2/2
This isn’t just my whim—it’s a massive community request! Steam Discussions, Reddit (r/Barotrauma), and GitHub are full of threads: “Ability to use Bots in multiplayer similar to single player” (2024), “Why you cannot switch with bots in MP?”, “Multiplayer Bot Manage Talents and Manual Control.” Mods like “Multiplayer Crew Manager” or Lua scripts are buggy workarounds that require sync for all players and break the vanilla experience. Players with small groups (2–4 friends) are forced to play tiny subs or suffer because they can’t leverage bot talents for crafting (recipes unlock for all, but bonuses? No).
Why is this necessary?
Accessibility: Not everyone has 16 friends online 24/7. With bots like in solo, MP becomes hybrid—perfect for 2–3 players + AI.
Role balance: Bots with talents become useful (crafting, repairs), not “husk food.” In campaigns—permanent death/hiring, just like solo.
Reduced cheating: You already have “setclientcharacter”—make it a vanilla feature with a host toggle (karma-based, for friends/admins only).
Online growth: More players = more servers, streamers, content. Barotrauma holds 3–4k concurrent—this is your chance to grow!
Implementation suggestions (simple & elegant):
Server toggle: “Allow bot switching” (host/group only, with karma limits).
Bot UI: Click bot in crew list → “Take control” / “Manage talents/loadout” (like solo).
Auto-return: After switching back, bot reverts to AI.
Free update with Home & Harbor: Perfectly fits bases and the new faction—bots become part of “outpost ownership.”
Developers, you’re legends who’ve kept the game alive for years (Summer/Autumn Updates, 2026 DLC). But this feature is the key to true hybrid multiplayer, like RimWorld with co-op. I’m calling out on Discord—hear the voice of the ocean’s players! Let’s make Barotrauma even greater, where bots aren’t a problem, but allies in the abyss.
With respect and huskies in my heart,
BlackBeirin
fresh cradle
I support this 100%, this is what stops me from playing solo, and what ultimately stops me and my friend from finishing campaigns
sweet oracle
Ong ts peak
copper idol
@azure talon just keep it short and sweat also take it to the Github next time
open valley
As long as its a server setting I am also fine with this