Running Baldur's Gate 3 in Co-Op Without Going Completely Insane
Multiplayer speedrunning Baldur's Gate 3 is a weird corner of the community. Most people run solo because it's faster. When you add a second player who doesn't know what they're doing, you're looking at maybe double the time on any given segment. That said, it's possible to run competitively through co-op if everyone commits to the run and actually rehearses their inputs. It's exactly what it sounds like — two or more players attempting to finish Baldur's Gate 3 as fast as possible, typically with strict of who controls which characters. The most common format is four players controlling Astarion, Shadowheart, Lae'zel, and Gale simultaneously, with one person acting as a "handler" or observer calling out skips and timing windows. There's no official speedrun category for this. Most co-op runs are submitted as "fun runs" rather than timer-verified attempts, which means you're running without any formal recognition from the speedrun community databases. That doesn't mean the runs aren't serious. They just operate outside the usual structure. The main technical challenge is input synchronization. Every action in BG3 takes a few frames to register. In solo runs, you can queue abilities with practiced precision. In co-op, you're relying on voice comms or external tools like Discord timestamps to coordinate who acts when. A typical battle sequence that takes three seconds solo becomes eight to ten seconds with four players rotating through actions. The combat pace fundamentally changes. You lose the tight rotation system that solo runners use to maximize damage per round.
I've done maybe twenty or so co-op speedrun attempts across different groups. One thing I learned the hard way — don't try to run with someone who hasn't actually played the game before. Even experienced players need at least a full playthrough of the Act 1 sequences to understand the pacing. We once spent forty-five minutes in the Goblin Camp because our third player didn't know how to skip the initial dialog with Minthara. That single mistake cost us roughly ten percent of our total run time. We re-ran the same segment twice that day just to compensate.
Setup and Technical Requirements
For any co-op speedrun attempt, you need the standard BG3 multiplayer enabled. Larian's native co-op supports up to four players either locally or online. The local co-op option is generally preferred for speedrun purposes because there's no network latency between players. You're all sharing one keyboard or a combination of controllers on the same machine. The input registration is cleaner. Online play introduces a variable I'd rather not deal with — even a 50ms delay between players adds up across hundreds of interactions in a run. You also need a recording setup. If you're submitting to a leaderboard or tracking your times, OBS or similar screen capture software is necessary. BG3 itself doesn't have a built-in speedrun timer. You'll want an external timer application like LiveSplit running alongside the game. Some groups use custom Lua scripts or modify the game's debug tools to get more precise frame-by-frame tracking, but that's more work than most people want to invest. The save system in BG3 complicates speedrunning significantly. The game autosaves constantly — after every major story decision, after every combat encounter, and sometimes during trivial moments. For a proper speedrun, you're relying on manual saves and the ability to reload quickly. In co-op, this becomes a coordination problem. If Player 2 messes up a dialogue check and triggers an unwanted fight, the whole group has to reload. There's no single-player privilege to instantly revert your own mistake.
Get the Full Details
I ran into a specific issue during an Act 3 attempt where one of our players accidentally initiated a conversation with the Duke that triggered a cutscene we had been skipping. The entire group had to reload from about twenty minutes earlier. We lost roughly an hour of work. The workaround was establishing a strict protocol: no player initiates any interaction without calling it out first. You say "I'm clicking this" before you click it. It feels slow at first. After a few runs, it becomes automatic and actually speeds things up because you avoid those catastrophic mistakes.
Route Optimization in Co-Op
The speedrun route for Baldur's Gate 3 is well-documented by solo runners. You can find current WR splits on sites like speedrun.com. The general approach involves skipping as much dialogue as possible, using action economy efficiently in combat, and taking specific skill checks that unlock shortcuts. For co-op, the route needs modification because four players can't access the same dialogue options simultaneously. One critical adjustment: character assignment matters enormously. In most co-op setups, the fastest arrangement gives one player Astarion for his stealth and skill-based skips, another player Lae'zel for direct combat efficiency, a third handling Shadowheart for her divine magic and healing, and the fourth controlling Gale for utility spells. This distribution covers the most important skip opportunities. Any other arrangement tends to create bottlenecks where a required skill check has no qualified player available. The Underdark sequence is where co-op runs typically lose the most time. Solo runners use specific positioning and ability combinations to bypass the entire area. In co-op, coordinating four characters through the Underdark's environmental puzzles takes significantly longer. The most effective approach is having one player drive the puzzle solution while the others provide covering fire and ready to act on command. You communicate the puzzle answer before anyone touches anything. Everyone knows their role for that segment.
Combat pacing is the other major factor. Solo speedrunners use a technique called "action denial" — they end encounters before the enemy can take most of their turns. This requires very specific build choices and gear optimization. Co-op runs generally can't replicate this level of control because four players need time to coordinate their rotations. A more realistic co-op approach is "target elimination" — focusing all damage on one enemy at a time until the threat is reduced to something manageable. It's slower but more reliable with multiple operators.
Common Pitfalls and Reality Check
Multiplayer speedrunning BG3 has serious limitations that make it impractical for competitive purposes. The primary issue is coordination overhead. Every decision requires communication. Every action requires confirmation. In solo runs, these steps happen internally in milliseconds. In co-op, they take seconds to minutes depending on group familiarity. Another problem is the save structure. BG3's frequent autosaves are both a blessing and a curse for speedrunning. They allow quick recovery from mistakes but also create confusion about which save state is current. Four players each controlling different characters means each person might be operating from a slightly different understanding of the run state. We've had situations where one player thought we had already completed a segment and was preparing for the next, while another player hadn't actually progressed there yet. These desyncs are incredibly frustrating and relatively common. There's also the matter of skill-based skips. Many of the fastest routes rely on high Athletics, Acrobatics, or Persuasion checks. In co-op, only the player controlling the character with that skill can attempt the skip. If your Astarion player has a bad roll on a critical check, the entire group is stuck waiting for the next attempt or forced to take the long route. There's no way to redistribute that skill check to another player. You're locked into whoever is controlling that specific character.
I should mention that co-op speedrunning is ultimately a social activity more than a competitive one. The times you'll achieve will be slower than solo runs, often significantly so. A solo WR attempt might complete the game in under two hours with optimal execution. A four-player co-op run of comparable quality will likely take three to five hours depending on group skill and communication efficiency. If your goal is pure speed, solo is the answer. If your goal is completing the game faster while hanging out with friends, co-op works fine. Just don't expect world record competition. The community around co-op runs exists primarily for entertainment rather than records. There are a handful of Discord servers and YouTube channels documenting co-op speedrun attempts. The content is more about the chaos of four people trying to execute a optimized route than about the actual times achieved. Watching experienced groups handle complex segments with clean coordination can be genuinely impressive. The runs themselves are less about breaking records and more about demonstrating that the route is achievable under cooperative constraints.
