Action
Learning paths through this topic
Mark several players for a boss attack without marking two who stand together
A boss attack that marks a few players works as a puzzle only if the marked players can spread out and the rest can stay clear. A random pick often puts two marks side by side. This entry shows a pick that avoids it and what to do when the group is too tight.
Combine several cooldown speed-ups without making spells endless loops
A ring, a talent and a potion each shorten spell waiting times, and adding them up lets a clever player cast nonstop. A second trap waits when the bonus changes while a spell is still recharging. Here is a rule that stays fair in both cases.
Let magic shields absorb damage in the right order before health
A hero can wear a blessing, a spell barrier and a potion shield at once, and each one runs out on its own clock. Hits must eat them in a sensible order, spill into health only when they are empty, and some damage should ignore them entirely.
Let a boss call helpers, but never more than a fixed number at once
A necromancer who summons skeletons should keep the room busy, not bury the hero in thirty of them. The catch is that helpers take a moment to appear, and counting only the visible ones lets the cap be broken. This entry shows what to count and when to spend the wait.
Let the hero survive one deadly blow, once, then pay for it
A second-chance charm sounds simple, but three arrows in the same moment can still kill the hero it just saved, and a charm that rearms too easily means nobody ever dies. This entry shows the small state that makes it feel dramatic and fair.
Stop fast bullets from flying through thin enemies between two server updates
When the server updates only a few times per second, a fast bullet can be in front of an enemy in one update and behind it in the next, and never touch it. This entry shows how to test the whole path the bullet took, and which hit counts when it crosses several.
Fill a shared super move together without one player doing all the filling
A team charge bar that fills from everybody's fighting is a nice shared goal, until one player on a farmable spot fills it alone. This entry shows a limit on one player's share, why that limit must not apply to a solo player, and what happens to the overflow.
Decide when the whole team has lost, without ending the round too early
Ending the round the instant the last standing player falls cuts off a revive that was about to finish, and counting only dead players never ends a round where everyone is down. This entry shows the rule that avoids both, and how to treat players who left.
Show a hit at once on your own screen, then take it back if the server says no
Waiting for the server before showing a hit makes shooting feel dead, but showing it at once and being wrong feels like a lie. This entry shows a middle way that feels immediate, what to display for which moment, and what to do with answers that never come.
Reward two players who attack one enemy in turns, without a solo player earning it
A bonus for teamwork should come from really taking turns on an enemy. A simple counter of hits within a short time is earned by one fast player alone. This entry shows what counts as a link between two players, when the chain breaks and how high the bonus may climb.
Decide who gets a pickup when two players grab it at the same moment
Two players run to a health pack and both press at once. Whoever's message reaches the server first wins, which means the one with the better connection always wins. This entry shows a fairer ruling and a trick it must be safe against.
Let an arrow to the head hurt more and a broken leg slow the monster
Hit zones make fights about aim, but the usual version has two bugs: a head that stays a weak point after it is destroyed, and part damage that is mixed up with the creature's health. This entry shows both numbers kept apart and what a broken part does.