How to Design Enemy Attack Telegraphs

Telegraphs—the cues that signal an enemy's incoming attack—are essential to fair, skillful combat, because they give the player the information and time to react. Designing clear, readable telegraphs with appropriate timing is what makes combat feel fair, turning getting hit into a readable mistake the player can learn from rather than an unfair surprise.

Telegraphs make combat fair and readable

The function of a telegraph is to signal an incoming attack before it lands, giving the player the chance to react—to dodge, block, or counter. This is what makes combat fair: when attacks are telegraphed, the player can read them and respond, so getting hit is the result of failing to react to a readable cue, which feels fair and is a mistake the player can learn to avoid. Without telegraphs, attacks come without warning, and getting hit feels arbitrary and unfair, because the player had no way to react. Telegraphs transform combat from a guessing game into a readable exchange where the player perceives the cues and responds skillfully, which is the foundation of satisfying action combat. Each enemy attack should have a clear telegraph—a wind-up animation, a visual cue, an audio signal—that signals the attack is coming, so the player can read and react to it. Designing telegraphs for enemy attacks, so that attacks are signaled and readable, is what makes combat fair and skillful rather than an unfair guessing game.

Clarity and timing are what make telegraphs effective. A telegraph only works if it's clear and gives appropriate warning. Clarity means the telegraph is readable—a distinct, perceptible cue that the player can recognize as signaling a specific attack, so they know what's coming and how to respond. A telegraph that's too subtle, ambiguous, or hard to perceive fails to inform the player, leaving them unable to react despite the attack being 'telegraphed.' Clear, distinct, recognizable telegraphs—that the player can perceive and identify—are what make telegraphs actually inform. Timing means the telegraph gives enough warning to react: the time between the telegraph and the attack landing has to be enough for the player to perceive the cue and respond, but not so long that combat feels sluggish. Tuning this timing—enough warning to react skillfully, calibrated to the pace of combat—is what makes telegraphs fair, since a telegraph that gives no time to react is useless, while one with appropriate warning enables the skillful reaction that makes combat satisfying. Combining clarity (readable, recognizable telegraphs) with appropriate timing (enough warning to react) is what makes telegraphs effective—giving the player the clear, timely information to read and respond to attacks, which makes combat fair and skillful. When attacks are clearly telegraphed with enough warning to react, getting hit feels like the player's readable mistake, which is fair and teaches them to do better, rather than an arbitrary unfair surprise. Designing clear, well-timed telegraphs for enemy attacks is what makes action combat the fair, skillful, readable exchange it should be, where the player's success and failure come from reading and reacting to the cues, which is exactly what telegraphs provide.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

Telegraphs signal incoming attacks, giving players time to react—essential for fair, skillful combat. Make them clear and readable with enough warning, so getting hit feels like the player's mistake, not an unfair surprise.