The jump starts before anyone leaves the ledge. One player spots the moving platform. The other is already pressing forward. “Wait. Now. Go.” Three scraps of speech, each tied to a different moment, can keep a co-op attempt readable. In Split Fiction, where Zoe and Mio bring different abilities to stages built around changing mechanics, the callout is part of the timing.
Call the next action, not the whole scene
Split Fiction is made for two players. Its two protagonists have different abilities, and progress depends on using them together. The game moves among platforming, puzzles, stealth, and combat, with stages introducing their own mechanics. That variety gives partners a reason to communicate, but it can also make running commentary hard to follow.
Keep the callout attached to one decision. “Platform moving left” reports what you see. “Jump after it turns” gives the other player a usable cue. “Jump, then hold” adds a second instruction that may compete with the first. If the action needs two steps, break them apart: “Jump.” Then, once the first player is airborne, “Hold.”
The official descriptions stress coordinated actions and timing, but do not prescribe callout language or identify specific jump sequences. Treat the phrases here as a practical routine, not a description of a particular level. The aim is to give a partner enough information to act without making them process a running commentary during the jump.
Put the words on the jump’s three beats
A useful rhythm has three beats: cue, departure, landing. The cue names the thing both players can watch. “Wait for the platform.” The departure call says when to commit. “Now, jump.” The landing call confirms what happened or gives the next instruction. “Safe. Keep moving.” These short calls leave less room for two people to shout different plans at once.
Timing matters because a direction can arrive too late to use. “Jump now” is helpful before the input. If it arrives while the player is already in the air, it may be better to say “left” or “hold” only if that information can still change the move. Otherwise, save the note for the landing. A calm “short, try again” beats a stack of corrections while someone is still steering.
Use the smallest visible reference both people can identify. That might be a ledge, a moving surface, an opening, or the partner’s position. Avoid vague calls such as “there” when each player is looking at a different part of the screen. In split-screen, the two views can make “your left” and “my left” disagree. Name the target instead: “toward the ledge,” not “go left.”
Give each player a clear job
Before a tricky sequence, decide who is watching the timing and who is executing the jump. The player with the clearest view of a cue can call it. The player taking the action can answer with a quick “ready” or “got it.” Then both know whose voice to follow. This is especially useful when a stage asks the characters to use different abilities, since each player may be tracking a separate part of the solution.
“Watch the turn.”
“Ready.”
“Now.”
“Landed.”
That exchange is deliberately plain. It avoids explaining the entire plan at the moment of execution. If one ability has to set up the other, name the order before moving: “You trigger it. I cross after.” Keep the live call focused on the cue. If the first attempt fails, pause and change one thing at a time. Was the call early, was the target unclear, or did the plan need another step?
The two characters’ abilities and the mechanics of a stage can vary, so a routine that works once may not fit the next section. Recheck who is doing what when the game introduces a new task. Don’t assume the partner knows which character action you mean from “use yours.” Say the character or ability in your own words, then let the other player confirm the plan.
Make the reset part of the session
A missed jump is a useful test of the communication, not a reason to talk faster. On the retry, change the callout to something more specific. If “go” came too early, replace it with a landmark: “when the platform reaches the near side.” If both players moved at once, assign one person to wait. If the landing was unclear, agree on what counts as safe before trying again.
Keep the review short. One sentence is often enough: “I thought you meant the first opening.” Then settle on a shared name for it and restart. A long postmortem can make a small mistake feel bigger than it was. The useful detail is the one that changes the next attempt.
This approach also leaves room for the game’s surprises. Split Fiction combines science fiction and fantasy stories and shifts among different kinds of play. Partners do not need to predict every mechanic in advance. They need a way to stop, identify the next cue, and agree on who acts first.
Set up the call before the first jump
Agree on a few basics before starting: which player calls timing, what you will call the main landmarks, and whether you are playing locally or online. The game supports local and online co-op, and the publisher lists a Friend’s Pass for inviting a friend to play free. Check the current platform details together before arranging a session. The official game page lists the Friend’s Pass and crossplay information, while Hazelight’s page lists the supported platforms.
Then keep a small session log in your head: cue missed, call late, or target unclear. Pick one adjustment and take the next run. “Wait for the turn” is more useful than “be faster.” “Say the ledge” is more useful than repeating “over there.” What single word or timing change would make your next jump easier to read?
He is a house writer for GamesUnlimited. He covers co-op campaigns, controller design, and player rituals through reports from launch nights and living rooms.
