What Happens Between Your Actions in Turnless RPG Combat?
You swing your sword.
The enemy catches the blow on its shield. Your blade slides away, and the two of you separate just enough to look for another opening.
Your attack is over. Now what?
In a traditional turn-based combat system, the answer is usually pretty clear. Your turn ends. Someone else takes theirs. Eventually the order works its way around the table and comes back to you.
Until then, you wait. But what happens when there isn't a line of combatants taking turns?
That's one of the first questions that comes up when we talk about turnless combat in Mayhem, and it's a good one. If your character has finished an action, something has to determine when they can do something else. Otherwise “turnless” could easily become “whoever talks fastest gets to act most often.”
That isn't what we're looking for.
The answer begins with something that's easy to forget when we're sitting around a gaming table.
Your character didn't stop. The Sword Is Still in Your Hand
Go back to that first attack. You swung your sword and the enemy blocked it.
From the player's perspective, there's a natural tendency to think of the action as finished. The dice were rolled. We know the result. Move on to somebody else.
But imagine the fight.
Your sword didn't teleport back to its starting position. You didn't freeze in place. Your opponent didn't turn transparent while something happened on the other side of the battlefield.
You're still standing in front of someone who would very much like to hurt you.
You're recovering from the swing. You're watching their weapon. You're shifting your footing. Perhaps you're advancing. Perhaps you're backing away. Maybe you're trying to get your shield between the two of you before they answer your attack.
At the same time, everything around you is still happening. The wizard behind you is casting.
Someone is running across the room.
An arrow just went past.
One of your companions shouted something that sounded important.
And that enemy you just attacked?
They're doing something too. The space between one attack and the next isn't empty. It's the fight.
The Part We Usually Skip
Turn-based combat has trained many of us to think of combat as a series of completed actions.
I attack. You attack.
The goblin attacks.
The wizard casts.
Then we start over.
It's an excellent way to organize what would otherwise be a messy collection of events. The problem is that the organization can make the spaces between those events almost invisible.
Those spaces are where an enormous amount of real action would actually be happening.
A fighter doesn't spend an entire battle attacking. Much of the fight is spent watching, moving, defending, recovering, threatening, looking for openings, and trying not to give the opponent one.
An archer doesn't simply alternate between “shooting” and “doing nothing.” They're finding another arrow, watching the battlefield, choosing a target, trying to keep a clear line of sight, and deciding whether the person who just charged toward them has suddenly become a much bigger problem.
A spellcaster may already be working on something that hasn't happened yet.
Combat is full of actions in progress.
Once we started looking at a fight that way, the question changed from “Whose turn is next?” to something much more useful:
What is everyone doing right now?
You're Not Waiting. You're Doing.
Imagine a fighter and rogue working against the same opponent.
The fighter attacks first and forces the enemy to react. While that's happening, the rogue is moving around the fight.
The rogue hasn't necessarily made an attack yet. That doesn't mean the rogue is waiting.
Movement is what the rogue is doing.
Perhaps the fighter sees the rogue moving and realizes what they're attempting. Instead of making another immediate attack, the fighter keeps pressure on the enemy, making it harder for them to turn and deal with the rogue.
Now the rogue reaches a better position.
The next attack isn't an isolated event. It grew out of what both characters were already doing.
That's one of the things we like about looking at combat this way. The moments between attacks become opportunities rather than dead space.
Maybe you're advancing.
Maybe you're defending.
Maybe you're controlling an enemy's attention.
Maybe you're trying to reach someone.
Maybe you're preparing something.
Maybe you're simply watching for the right moment.
The character is still participating even when the player isn't currently rolling dice.
But You Still Can't Do Everything at Once
Of course, there's an obvious danger here.
If there's no traditional turn saying, “That's all you can do for now,” why can't a player just keep announcing actions?
“I attack him. Now I move over there. I attack again. I draw my dagger. I attack with that too. Then I—”
This is where turnless combat still needs structure.
Mayhem doesn't remove time from combat. In fact, time becomes extremely important.
Actions require effort and take time. Moving across the battlefield takes time. Fighting takes effort. Defending yourself takes effort. Doing something complicated may require more of both.
So finishing one action doesn't magically reset your character.
What you just did matters to what you can do next.
This gives combat boundaries without requiring every participant to stand in the same line.
Instead of asking whether your turn is over, we're interested in what you've been doing and how much you've been doing.
The battle keeps moving while that happens.
Actions Don't Have to Happen All at Once
There's another reason this becomes possible: an action doesn't have to be treated as one indivisible event.
Think about drawing a sword, moving toward an opponent, striking, and then moving into a defensive position. We can describe all of that as one plan, but it isn't really one thing happening at one instant. It's a series of smaller things connected together.
Mayhem calls those pieces Links. Links can be connected into Chains, allowing a character to build a sequence of actions that flows naturally from one thing into the next.
That becomes especially useful when several people are acting at once.
While the fighter is moving through one Link in a Chain, the rogue may be moving through another. An enemy may be preparing an attack while the wizard is already working through the actions needed for a spell. Their actions don't have to wait politely for one another to finish before something else can begin.
Segments give those overlapping actions a common sense of time.
That means we don't have to pretend that four complete actions somehow happen at precisely the same instant. We can look at the smaller pieces that make up those actions and see where they overlap, where they finish, and—most importantly—where they affect one another.
The fighter may begin moving before the archer fires, but the arrow will reach its target before the fighter reaches theirs. The rogue may begin circling an enemy while that enemy is occupied with someone else. A spell may already be underway when something happens that causes the caster to reconsider it.
That's much closer to how we imagine a fight.
And Chains add another interesting possibility. What you're doing now can help determine what you can do next. A successful Link can flow into another Link, creating a sequence instead of a collection of unrelated actions.
The battle doesn't become simultaneous because everyone does everything at once.
It becomes simultaneous because everyone's actions can be in progress at the same time.
Six Seconds Are Still Six Seconds
There's another distinction worth making here because the word turnless can be misleading.
Mayhem's combat is turnless in the sense that characters don't take traditional combat turns.
That doesn't mean Mayhem throws away turns as a measurement of time.
Time still matters outside combat, and it continues to matter while combat is happening. Mayhem tracks short periods through Moments and Rounds, while turns remain useful for just for who is acting right now. Spells have durations. Effects have durations. Things begin, continue, and eventually end.
If a magical effect lasts for a certain amount of time, getting into a fight doesn't stop its clock.
The world doesn't stop keeping time just because swords came out.
That's important because otherwise removing combat turns could create another problem: suddenly everything outside the immediate attack becomes vague.
We don't want that either. The goal isn't to eliminate the clock. It's to stop making everyone use that clock one at a time.
Meanwhile, the Fire Is Still Burning
Imagine the wizard has created a magical effect that will last for a limited duration.
A traditional combat system might express that duration in turns or rounds, and players become accustomed to checking it at convenient points in the initiative order.
Without conventional combat turns, we need to think about the effect a little differently.
It began at a particular time. Now time is passing.
While the fighter attacks, time passes.
While the rogue moves, time passes.
While an enemy retreats, time passes.
The effect doesn't care whose action we're currently resolving.
It's still there. And eventually it won't be.
The same idea applies to more than magic. A door is closing. A bridge is collapsing. Reinforcements are approaching. Someone is bleeding. A torch is burning. A creature is trying to escape.
Those things don't patiently wait for their place in the initiative order.
They're part of the situation.
That can make time more interesting rather than less important.
Plans Can Change Before You Finish Them
There's another consequence of treating combat as ongoing instead of dividing it into isolated turns. Sometimes what you intended to do stops making sense.
The wizard begins preparing an attack against the ogre. Before it's completed, the fighter drives the ogre backward. Now the rogue moves into the area the wizard intended to target.
That's a problem.
The wizard can ignore what's happening and continue with the original plan.
Or change it.
That ability to watch the battlefield develop becomes important because players aren't simply waiting for their next opportunity to select an action. They may already be doing something when circumstances change.
This is where combat starts becoming a conversation between actions.
You do something. The enemy responds. That creates an opportunity for someone else.
Their action changes what another player was planning.
Something goes wrong. Everyone adjusts. The battle develops rather than simply progressing through a list.
What If Your Target Isn't There Anymore?
One question came up that gets right to the heart of how Chains work: What happens if you're in the middle of a Chain against a goblin and you kill the goblin before the Chain is finished?
The simple answer is: the goblin is dead, not your Chain.
Chains in Mayhem aren't scripts that have to be planned from beginning to end and then followed no matter what happens. They're meant to be flexible because the battle is changing while you're fighting it. Unless a Link specifically requires another Link to immediately follow it, you can change course as the situation changes.
Suppose you're firing arrows at a goblin. You planned to keep shooting, but your first arrow kills it. You don't have to waste the rest of the Chain firing arrows into a corpse. If another foe is visible, you might add an Aim Link, choose the new target, and continue your Chain against it. If there isn't another foe beyond the dead goblin, you may need to move first, find another target, and then continue from there.
The same idea applies in close combat. If your sword drops one goblin sooner than expected, you might move toward another opponent, defend against a new threat, change position, or continue into another appropriate Link. What happens next depends on what is happening on the battlefield right now, not what you thought would be happening when the Chain began.
There is one important exception. Some Links require a particular Link to immediately follow them. When that happens, you have committed yourself to that combination. You can't insert something else between those Links simply because the situation changed. Otherwise, a Chain remains flexible.
That's one of the reasons Chains fit turnless combat so well. You're not announcing an entire sequence and then watching helplessly as the battle makes your plan obsolete. You're building the Chain as the fight develops, responding to enemies, openings, movement, and unexpected results.
A Chain isn't a script. It's what you're doing next.
The target may be gone. The fight isn't.
Sometimes the Smartest Action Is Not Attacking
This also gives us room for something that combat systems sometimes struggle to make interesting. Not attacking.
If your opportunities are measured primarily by turns, there's enormous pressure to make each turn count. When your turn finally arrives, doing anything that doesn't immediately produce a result can feel like you've wasted it.
“I waited twelve minutes for my turn and I'm going to... watch the doorway?”
That can feel terrible.
But if combat is ongoing, watching the doorway can be exactly what your character is doing while other events unfold.
Holding an enemy's attention matters.
Protecting someone matters.
Moving into position matters.
Waiting for an enemy to make a mistake matters.
Preparing to respond to something matters.
Not every useful contribution needs to end with damage.
That's especially important in tactical combat because tactics aren't merely about how effectively you attack.
They're about creating the circumstances in which the right attack becomes possible.
What Are You Doing Right Now?
That question may be the simplest way to understand what happens between actions in turnless combat.
Your attack ended. Fine. What are you doing now?
Are you recovering? Advancing? Defending? Watching the enemy? Moving somewhere? Helping someone? Preparing another action? Trying to stop something that's already happening?
And while you're doing that, what is everyone else doing?
The answers don't need to be complicated. They simply need to keep the characters inside the battle.
Because that's ultimately what we're trying to accomplish with turnless combat in Mayhem. We're not trying to make everyone act constantly. We're not trying to see who can announce actions the fastest. And we're certainly not pretending time no longer matters.
We're trying to get away from the strange idea that when your action ends, your character's involvement in the fight ends with it.
You swung the sword.
The enemy blocked it.
Your attack is over.
But the enemy is still standing in front of you. The rogue is still moving behind them. The wizard is still casting. Somewhere nearby, somebody just screamed.
And now your opponent raises their weapon. You're not waiting for your next turn.
You're already there.
Next from the Engine Room
If everyone is acting during the same stretch of time, does that mean everything happens simultaneously?
Not quite.
An arrow will reach its target while someone else is still moving. A sword can strike before a spell is completed. One action can interrupt, change, or even make another action unnecessary.
So how do you make a battle feel simultaneous without trying to resolve everything at exactly the same instant?
That's where things get interesting.