Elden Ring Gameplay Speedrun Co Op

Getting Two Players Through Elden Ring in Under 45 Minutes

Co-op speedrunning Elden Ring is mostly about communication, frame-perfect summoning, and accepting that your run will fall apart the moment one person touches a wall they weren't supposed to. I've run the Any% co-op category enough times now that the routes are memorized, but that doesn't make things easier when you're actually in the match. The basic concept is straightforward: two players split responsibilities, one distracts bosses while the other positions for optimal damage windows, and both of you use only glitchless movement and attack methods. That sounds simple until you realize the game's latency can shift your hitboxes by three frames in either direction. The category runs across any platform, though PC-to-PC pairings tend to be more consistent because of lower input lag. Both players need to be on the same save-file version — this means the same game patch and the same region code. A Japan-hosted lobby and a US client can sometimes connect, but the boss health pools and frame data don't always line up cleanly, and I've watched runs get invalidated over exactly that issue at major tournaments. Player roles are informal but usually settle into one of two patterns. The "puller" draws enemy aggression using ranged spells, bows, or just running in circles near the boss. The "dps window player" stays on the periphery and commits only when the puller has secured aggro. This works because most Elden Ring bosses have a fixed detection radius and a delay of roughly half a second before they reset targeting. You can exploit that delay by pulling, stepping back three meters, and having your partner attack immediately.

Neither player should use multiplayer items outside the designated ones. The standard build uses the Gold-Picked Furled Finger for co-op invitation only. Using item-based buffs like Food or consumable status effects is allowed, but weapon enhancements from spirits or talismans that grant unique co-op bonuses are generally excluded from any serious run. Check the specific ruleset you're submitting under, because different communities enforce this differently. The route itself cuts through the starting area, then hops directly to Liurnia, and from there it threads through a specific sequence of dungeons that skips roughly sixty percent of the overworld. Stormveil Castle, Raya Lucaria Academy, and Caelid's Mohgwyn Palace are the usual anchors. The exact order depends on which glitches you're using — or rather, which ones you aren't — since "glitchless" is defined differently by whoever you're talking to. Common accepted movement techniques include wall-clipping through certain doorframes at Liurnia and exploiting collision faults at Mohgwyn to skip the entire underground access path. Those skips save about seven minutes total and are considered legal by most leaderboard committees. I ran into a specific problem during a practice session last year where my partner and I kept dying at the Radahn festival because his controller input was registering one frame later than mine. The festival requires two players to hit the trigger in near-perfect sync, or the enemy wave spawns a half-second early and the timing chain breaks entirely. I spent three hours experimenting with input lag compensation before finding the actual fix, which turned out to be having both of us disable V-Sync and lock the frame cap to sixty on both machines simultaneously. Without that, one player's input was queuing in a different render cycle and the boss fight physics were desyncing. It sounds minor. It cost us about forty minutes of real time and two failed PR attempts.

Setting Up for a Clean Run

Start by ensuring both clients are on the same network topology. Ideally both are wired. If one player is on WiFi, run a separate traceroute during practice and log the average ping. Anything above thirty milliseconds between the two hosts tends to cause noticeable input desync in boss encounters. I once paired with someone on a 45ms connection and the Malenia fight became unplayable because her waterfowl dance animations were desynced between our clients. Each of us saw a different phase of the move coming. Download links for the game itself are standard — Steam, PlayStation Store, Xbox Store. There's no special tool you need to install. Speedrun timers are usually handled externally. Most co-op runners use LongCat or a custom Split-Timer spreadsheet. Both are fine. What matters more is that the recording software captures both players' perspectives if you're doing a verified submission. Some organizers accept a single screen capture, but dual-feed recordings reduce disputes about whether a skip was actually executed or just looked like one. Communication during the run should be minimal and pre-planned. Shouting random advice in voice chat wastes time. Before the run, agree on a set of callouts: "ready," "pulling," "engage," "skip confirmed." Nothing else. I've seen runs where too much talking caused both players to hesitate at a critical moment, and the hesitation resulted in a missed window that took another two minutes to reset.

When it comes to boss strategies, the counter-intuitive part most beginners miss is that the highest-damage player should often take the pull role, not the dps role. It sounds backwards, but having the stronger damage dealer draw aggro forces the boss to stay committed longer, which opens bigger windows for the second player. A weak character pulling gets killed quickly, resetting the encounter and burning valuable seconds. Use your strongest build to tank initial pulls and your secondary build to output damage during the boss's recovery animation. The DPS numbers on paper look worse, but the actual time-per-boss is significantly better. Another thing people overlook is item usage timing. Consuming a buff potion two seconds too early means the buff expires before the next boss. Consuming it one second too late means you enter the fight without it. Both scenarios happen constantly in co-op runs because you're coordinating consumption with your partner's positioning. The workaround is to pre-plan buff usage around the known distance between each major node on the route. Most routes have roughly equivalent spacing between major dungeon transitions, so a single buff can be timed to cover three or four boss encounters if used at the right moment. Figure out that moment through practice, not theory.

Common Failures and Why They Happen

The single most common reason co-op speedruns fail is collision or pathing disagreements between the two players. One player decides to skip a section the other hasn't reached yet. They arrive at the boss room at different times. The game state desyncs. The boss spawns with different HP or in a different phase than expected. These desyncs are nearly impossible to recover from and usually require a soft reset of the entire segment, which costs anywhere from ninety seconds to four minutes depending on the location. Boss-specific pitfalls are another frequent issue. Some bosses have enrage conditions that trigger if a player dies above a certain threshold. Others change behavior based on how many players are present versus how many have died. The Rennala fight in particular is sensitive to whether both players are in the arena simultaneously at the start of phase two. If one player is still traveling from the previous room, the boss can reset and force a full re-engagement. Both players need to be in the room and ready before the transition happens. Practice this transition separately until it takes less than five seconds. Inventory management between runs is also more important than most people think. If you enter a boss fight and both players accidentally equip the same talisman or weapon buff that creates a stacking conflict, the game can sometimes apply the buff twice to one character and not the other. This creates uneven damage output and can stall the run for several minutes while you figure out what went wrong. Check each other's loadouts before every major boss. It takes twelve seconds and prevents twenty minutes of confusion.

What This Category Doesn't Do Well

Co-op speedrunning in Elden Ring has hard limits. The category cannot go faster than the slowest network connection between the two players. It cannot bypass boss AI decision trees, which are fairly rigid and don't respond to coordination the way real-time strategy games do. It cannot recover from certain desyncs without reloading from a save, and some saves are located far from the point of failure, meaning a single mistake can cost you fifteen to twenty minutes of progress. These are not edge cases. They happen regularly, even among experienced runners. If your goal is simply a fast clear time, solo speedrunning the same route will typically be three to five minutes faster and involves far fewer failure points. Co-op is worth the extra complexity only if you're racing against another co-op team or if the collaborative aspect is the actual goal. For leaderboard purposes, the community currently records the fastest verified co-op times in the low-forty-minute range for Any% glitchless, though those times assume near-perfect execution and sub-ten-millisecond network latency between partners. Most practice runs land somewhere between fifty-five and seventy minutes until the route is locked in. The route data and split times are available through the usual speedrun community archives. Search for co-op splits on the main Elden Ring speedrunning forums and Discord. The community is active and generally responsive to questions about ruleset interpretation, which matters because the rules have changed slightly across the major platforms over the past year. What was legal on Korean Boss Rush last season isn't necessarily legal this season.