Action
Learning paths through this topic
Decide when a fight is over so healing starts and old poison does not restart it
Health should regrow when the fight is over, but what is over? A timer after the last hit sounds right, until a poison tick from a minute ago puts the hero back in combat forever. This entry separates real hostile actions from leftovers and shows the exact moments.
Let a well-timed block count for players on slow connections, within limits
A block that needs perfect timing is hard enough on a good connection, and nearly impossible when the player sees every attack late and the answer reaches the server later still. This entry shows how to give the delay back to the player without making blocking free.
Reward a well-timed block without letting players just mash the button
A perfect block that is open every time you press feels great until players discover that pressing block ten times a second beats every boss. This entry shows how to give the reward only to a deliberate press while an ordinary block still works.
Slow time after a perfectly timed dodge, and keep the timer honest
A last-moment dodge that slows the world is a great reward, until the effect lasts three times too long, or can be triggered again and again. The trouble is which clock the effect runs on. This entry shows how to count, how to judge perfect, and how to space the reward.
Let poison or frost build up on a target until it tips, then get harder to repeat
Instead of a dice roll for each poisoned dart, many games fill a hidden bar that triggers the effect at the top. Players like the feeling of progress, but the bar must drain, must not trigger again at once, and should get stiffer for the next time. Here are the rules and numbers.
Let several players poison one enemy with a stack limit and a clear killer
When three players apply damage over time to the same enemy, the stack grows without limit and nobody knows who gets the kill when the poison does the last bit. This entry shows a limit per player and a rule for the killer that always gives the same answer.
Poison and burning that deal whole points and handle being reapplied
Ten damage spread over three seconds does not divide evenly, and a second poison dart raises two awkward questions: does it restart, add up, or get ignored? This entry shows how to lose no damage and avoid weak effects overwriting strong ones.
Make healing potions weaker when drunk one after another
If every potion heals the same, a stack of them makes any boss fight a matter of inventory, and the player never has to dodge. A drop in power for quick repeats keeps potions useful but not endless. This entry shows how to count recent potions and when the effect recovers.
Start a bullet where it would be by now when the fire message arrives late
On a slow connection the shot leaves the gun on the shooter's screen, but the server starts it a moment later, so it trails behind and misses things it should hit. This entry shows how to catch the bullet up, how far to allow it, and what to do about walls it skipped.
Build a rage meter that fills in a fight, waits to be used and then drains
A special-power meter sounds like a number that goes up. In play it needs rules: slower gains near the top, a full bar that does not leak away before you press the button, and a power mode that cannot refill itself. This entry shows the three states and the clock behind them.
Reflect part of a blow back at the attacker without a never-ending ping-pong
A thorn armor that hurts the attacker is simple, until two fighters with thorn armor meet and the damage bounces between them until someone drops dead from one hit. And reflecting a blow that was never dealt gives free damage. This entry shows the stop rule and the right base.
Fix the player's position after the server disagrees, without a visible jump back
The server says the player was somewhere else, and a naive fix puts them back in the past, undoing every step and dash they made since. This entry shows how to accept the server's word and still keep what the player just did.