Ask Angry: The Telegraphing “Hack”

November 18, 2026

I promised last time that I’d be answering another question from the Ask Angry mailbag today. Today’s answer kind of follows from the last, but it also doesn’t, but don’t worry about it. It’ll all make sense eventually or it won’t. Especially because I’m not even starting with the question.

Before I get rolling, though, let me remind you that you can submit questions for my not-nearly-regular-enough Ask Angry column by emailing ask.angry@angry.games. Remember to keep it brief, cut to the chase, and tell me what to call you.

The Art of the Telegraph

The question I’m eventually gonna answer concerns telegraphing. I’ve yammered several times about telegraphing in the past, but it’s always been a side thing in another article, and it’s never been rigorous. Actually, I might once have been kinda rigorous about it, but that was about five years ago, so I’m due to yammer again. As a side thing. Non-rigorously.

There’s a reason, just not one I can really explain. Don’t worry about it.

Telegraphing is, without hyperbole, the most important hack to add to any action roleplaying game if you think the combat’s shallow, bland, or boring. If you use phrases like damage race or rocket-launcher tag to describe your combat, telegraphing is the fix.

Not that it matters how you describe your combats. What matters is how players describe your combats. Game Masters always overanalyze combat math until they convince themselves it sucks. Game Masters are idiots.

Anyway…

Telegraphing is the art of telling your players what they need to know to make good tactical choices in combat without actually telling them what they need to know.

The classic example of telegraphing is, of course, the massive blue dragon opening its gaping maw and drawing in a vortex of air while electricity crackles and sparks between its teeth. Everyone knows that dragon is about to expel a lightning bolt. Even people that don’t know blue dragons spit lightning can guess a thunderstorm is coming out of its gullet when it goes from suck to blow.

The reason that’s the classic example is that it tells you everything you need to know about telegraphing. You, the descriptive Game Master, have warned the players that the dragon is about to unleash its most powerful ability without actually just saying it outright. The players have to connect the final dot. It’s an easy dot to connect, sure, but that doesn’t matter. What matters is that the players’ brains have to do something called synthesis. After that, assuming you provided the description in advance of the actual action, some of those player brains can choose a response to the incoming lightning storm.

Of course, that might depend on the initiative order, but that just makes initiative matter, doesn’t it?

Think about it: if you do the telegraphing thing and some characters have fast-initiative scores to react while others don’t, initiative matters, doesn’t it? It’s changing the game. You’re all always pissing and moaning about how initiative doesn’t matter except but for the first combat round, and it doesn’t even matter then, right? Well, with telegraphing, it does.

That’s just the first example of how telegraphing can help make mechanics matter. There are others. In the latest edition of one of the world’s roleplaying games, and in many other editions, and in many other similarly tactically-actiony roleplaying games, telegraphing also makes defensive options matter. Which is important because modern Dungeons & Dragons actually has really good monster design for the kind of defensive options it does offer.

Seriously.

You just have to know what you’re looking at.

The Depth of Damage Output: Beware of Math Ahead

I’ve said before that modern Dungeons & Dragons has the best monster design of pretty much any game ever, and I stand by that. The actual monsters in the book vary from holy awesomesauce, Batman to crappity crap, but the underlying framework is solid gold. Of course, it was a lot golder in 2014 when the designers actually told you how to use it, but all the machinery remains in the 2024 revision.

Maybe, in the very near future, a sexy gaming genius will revisit the whole making custom D&D monsters thing and give you pretty tools and tables so you can say, “Screw CR!”

If you know what I mean.

Anyway…

The key here is something I call damage cycles. Specifically, it’s that D&D’s math is actually built around a three-round damage cycle. With that, if you know what you’re doing and can fling around terms like regular damage and spike damage, you can get a lot of depth out of something as simple as damage codes.

Let’s say I’m building a monster, and it needs to do an average of 10 damage points a round, right? The easiest move is just to give it a sword attack that does 10 damage points. That works, right, but it’s dull.

So, maybe I get more creative. Maybe I give it a 5-damage sword attack and the Multiattack feature so it can swing twice a round. That’s a pretty common thing in D&D, and it actually makes the monster a little more interesting. Why? Because it can decide, every round, whether to concentrate that damage on one target or spread it between two. That might not seem like a big deal, but that’s because it isn’t. It’s actually a thousand different possible small deals. When a creature can attack twice, choosing to put two targets in its reach has consequences. When a creature spreads its damage, healing that damage gets harder because multitarget heals are rarer. When a creature can spread its damage, it’s harder to control it through tanking.

All those little things that change the calculus are what we in the biz call gameplay depth. Or sometimes, we just call it depth. It’s the number of different ways the same situation might play out depending on individual choices and changing situations. Depth is what you want. It’s the opposite of repetitive. It’s the opposite of damage race. Sure, there’s still a damage race, but it’s not a straight run. Now it’s a race through a maze.

That said, the difference between one 10-damage attack every round and two 5-damage attacks every round isn’t huge. Can we do better? Of course we can. Otherwise, I wouldn’t ask the question.

Because of the length of its combat and how the probability math works, Dungeons & Dragons uses three-round averages to figure damage. Creatures don’t have to do 10 damage; they have to do an average of 10 damage per round over three rounds. So my monster doesn’t need to do 10 damage every round; it needs to do 30 damage every three rounds. So, maybe it has a normal strike it can do every round for 6 damage and then a super-ultra-mambo-tango-foxtrot swing for 18 damage once every few rounds.

That’s what we, in the biz, call spike damage, and it’s actually great for games that have defensive options with a high perceived cost.

Let’s say, for example, that your game has a defensive action called Dodge that no one ever uses because, even though it does grant a very hefty defensive bonus, it eats up an entire action. Seriously, Dodge in D&D is consequential. When you Dodge, you’re 35% less likely to get hit if you do the math right and don’t confuse odds for percentage points like everyone always does.

Now, if you, yourself, as a player, can deal 10 damage points to a monster with 50 hit points, giving up a round to Dodge means skipping a chance to do damage, which means the monster gets another round to hit you. If it also deals 10 damage points every round, Dodging an attack at the price of not attacking changes nothing, all else being equal. Yes, for simplicity, I’m ignoring the odds of attacks actually hitting.

If you don’t Dodge, you kill the monster in five rounds and take 50 damage yourself. If you Dodge one attack, you kill the monster in six rounds and still take 50 damage. As tactical actions go, that’s pretty crap.

But now look at Spike the Spike-Damage Sword Guy. If he does 6 damage a round, but he also gets one attack in the combat that does 18 damage, he deals 42 damage during his five-round life. But if you know when his 18-point spike is coming and Dodge it successfully, he lives for an extra round, sure, but he only does 6 damage in that extra round. Over his now six-round life, without its spike landing, he only does 30 damage.

You see what I mean? Suddenly Dodge isn’t a crap option. Because, really, it isn’t always about how long the fight lasts, but about how much damage you take before it’s done. It’s still a damage race, but the enemy gets a sprint move, and you can try to counter its sprint. If you see it coming and decide it’s worth the risk that you won’t counter it.

This ain’t just about the Dodge action either. That’s just one example. If your hit points are low enough that you can absorb two more regular hits but a spike hit will kill you, you’re gonna have to do something different for a round, even if it’s just screaming for a medic. Assuming the medic is ahead of Spike the Sword Spiker in the initiative rotation. Or maybe that’s the round you spend your Expertise Die on saving your own ass. Whatever.

The point, again, is we have a depth situation. It’s not just the raw math of the Dodge action; it’s that there are lots of situations and lots of options whose value changes when spike damage is coming. In fact, there are whole strategies that change value when you can see a spike is coming. When you’re fighting a red dragon, you don’t have to spread out for the entire combat; you just need to know which round to scatter. That’s useful because several character types and options benefit from keeping allies snuggly close.

Now, some have argued that telegraphing and all the juicy depth it creates just make already easy fights easier, but those people are missing the point. Easiness of fights isn’t the issue. Hell, the thing they’re calling easiness isn’t even easiness. It’s just “how many resources the fight costs, and there’s nary a thing you can do about it.” That ain’t challenge, really.

Telegraphing actually does make fights easier, but it does so by empowering players to make the right calls. Isn’t that how it should be? If the players are attentive, make smart plays, and choose the right gambles when they matter, shouldn’t they win more fights better?

Meanwhile, once the players have more power to make smart plays and choose different gambles, you can risk throwing more complex fights at them. Not harder. Not deadlier. Not more damagier. Just more complex. Which leads to depth.

Telegraphing isn’t Signposting: A Quick Detour

Just a personal pet peeve here: people use the words telegraphing and signposting interchangeably. Please don’t. Telegraphing is about signaling an immediate action to change a player’s tactical response. Dragons warming up their breath, ogres winding up their swing, spellcasters gathering magical energy, elemental crystals swelling up because they’re about to explode: those are all telegraphing. “Something is about to happen,” says telegraphing, “so react accordingly.”

Signposting is more about long-term or strategic information. When the players find a bloodless corpse with puncture wounds, that’s signposting a vampire. When the vampire locks eyes with the fighter and begins waggling her eyebrows because she’s about to dominate person him, that’s telegraphing.

Telegraphing is technically a kind of signposting, but it’s a specific-enough skill that it needs to be talked about separately. So it needs a separate word.

My Telegraphing “Hack”

No matter the game or the system, I telegraph the motherloving crap out of my game. It’s the most important thing I do in combat. I never don’t telegraph anymore. I never won’t again. If a game makes it impossible to telegraph, I probably won’t run it. Buh-bye PBtA with your golden opportunity/Game Mastering move horseshit. I’ll still use you for convention one-shots, but you’re out of my campaign systems rotation.

I always want my players to have at least a general idea about what their foes are going to do next, and I especially want them to know whenever something impactfully big is coming. I also want them to know the health status of their foes and when a creature’s threat changes.

Now, I call this a hack because it really, truly is. It’s game mechanical. It has impact. It requires me to change how I’m running things and obey some rules. The reason why I’ve never rigorously tried to explain those rules and constraints, though, is because I only really know them intuitively and because that’s not the right way to do a telegraphing hack. But it really is a hack. I am changing the rules of the combat game.

Let me take this one step at a time, though.

Top-of-the-Round Telegraphing

At the top of every combat round, I tell the players what their characters can perceive of their enemy’s intentions. That’s assuming that my chosen engine’s initiative system isn’t doing something absolutely bonkers. If it is, I have to figure out a different way to telegraph because telegraphing has to happen.

Note, by the way, that I said perceive. I interpret that very broadly. A monster’s actions must be readable. If they are not, I make them so. I find a way. But note that I have left room for things like misdirection and feinting, and isn’t that interesting? That would be extremely rare, but a master swordsman that is hard to read would make for a really cool, unique challenge.

Anyway…

At the top of the round, I tell the players what their characters can see of their enemy’s intentions. If an enemy is just continuing to fight normally, I’ll skip saying that or say it very briefly. “The goblins fighting Ardrick are still going…” or whatever. If an enemy’s about to change tactics, targets, or doing something big, though, I call that out. “Having dropped Cabe, the ogre looks around for a new target and spots Beryllia off on her own. He grins and prepares to charge. Meanwhile, the shaman, realizing his allies are losing, reaches into his pockets and pulls out some disgustingly organic reagents. He spreads his arm wide and begins calling out the goblin spirits.”

Does that mean I have to pick my monsters’ actions at the top of the round? Yes. Yes, it does.

Does that mean I’m committed to those actions if they can’t happen or if the party thwarts them by the time the monster’s actual turn comes around? Actually, yes, kind of, but also not necessarily.

Unless the monster has successfully deceived the party in some kind of mechanical way or the party has information that would let smart players see through the ruse, I either have to follow through on the monster’s declared intention to the best of its ability or abort to a crappier action.

If Ardrick moves to stand between Beryllia and the ogre, for example, the ogre can charge Ardrick. It can also use the Dash action to move around Ardrick to engage Beryllia without attacking. It can even charge past Ardrick, eating an opportunity attack to get to Beryllia. It can’t, however, decide to target a different squishy target instead, nor can it stay still and coupe deville the downed Cabe.

If I wanted to leave it the option to choose which squishy to attack on its turn, I could. I just have to say, “With Cabe downed, the ogre looks between Danae and Beryllia, both in the open, as it weighs which to charge.” That’s a fair telegraph. I said, “You’ve got two exposed pieces on the board, and you either need to protect both or shield one knowing the ogre will probably attack the other.”

The shaman can choose not to cast the spell if someone throws antimagic down his throat; he doesn’t have to lose the slot. If the players wanted to cost him a slot, they could have chosen a Ready action or something, or just waited to do dispel magic as a reaction or whatever options they have. The shaman can’t, however, then use its big spike-type action instead. It has to do something smaller. Maybe it runs up to Danae and bonks her with its weak-ass bonky stick. Maybe it runs away.

That’s what makes being rigorous so hard. My Telepgraphing Hack isn’t really a systematic approach, but more just a list of things I’m not allowed to do without a top-of-the-round warning. I can’t do spike damage, high-level spells, big area attacks, switch to squishy targets with high threat monsters, or try to kill any downed character ever.

This is where a real, actual hack would work better. Imagine, for example, a special top-of-the-round phase in combat where monsters must flag their targets and in which they must use a special charge up action to be allowed to use a high-impact or limited power on their actual turn. That would force Game Masters to telegraph without having to understand what telegraphing even is or why it’s good.

It would also be a great place to build feinting and deception mechanics and the ways to see through them, no?

If I were writing a roleplaying game engine…

Health Status and Threat Telegraphing

Apart from action telegraphing, I also telegraph my creatures’ health and threat status. Or, rather, I tell the players when they change.

And I tell them about those changes the moment they happen.

First, health…

All creatures in every system I run ever basically have three levels of health: okay, staggered, and critical. Creatures with most of their hit points are okay. They’re fine. They’re getting cut, bruised, and battered, but not enough to really affect them.

Once creatures lose a bunch of hit points — I use half in D&D and most other systems — they’re staggered. Somehow, in some way, the creature’s injuries are affecting it. It’s not enough to cause a penalty, of course, unless the system already has a penalty built in, but the effect is pronounced enough that anyone looking at the creature can tell it’s having a rough time.

Once a creature has lost almost all of its hit points, it’s critical. In D&D, I set the threshold either at 10% health or at the very scientific, I’m pretty sure one more normal hit will finish it threshold. Look, I usually eyeball this shit; sue me.

Being critical doesn’t have any mechanical impact either. It’s just me saying, “One more hit will probably finish this thing unless you roll really crappy damage like you always do.”

That’s health status, but I also telegraph threat status. What’s that? It’s whether the creature looks like it’s no longer a threat. Basically, I use it for things like morale breaks and foes dropping. I’m just saying, “The creature may not be dead, but you can focus on something else; this one’s done.”

Now, this, too, is based on character perception. There is room for bluffing with a fake surrender, and that room is filled with dice rolls and intuition mechanics, and it’s also a room I rarely go in, because if I overuse it, the whole point of telegraphing gets ruined. However, certain classes of creatures also fake being a non-threat as part of their nature, which the players very quickly learn. I’m speaking, of course, of undead that drop as if no longer animate and then get up again a round or two later like someone yelling, “… and another thing,” two hours after a fight’s ended. That sort of trait being unique to a certain class of creature and basically always being present doesn’t ruin telegraphing because it’s something the players learn and react to.

None of this requires a lot of explanation. It’s easy to grasp. So, let me move on to Banjo’s question. Because this is actually an Ask Angry, remember?

Banjo asks…

I’ve been applying your advice on telegraphing, and your two-headed, two-tailed snake thing, or whatever it was called. However, once bosses have multiple turns per round, telegraphing starts to feel weird [For example] when a dragon charges its laser beam breath for the next round, but it can still swipe away with its claws in the meantime. This tends to confuse players.

I’ll bet that confused players. That’s a very confusing thing to do.

First, though, you’re just talking about boss fights, which is a super deep cut. I did those years ago. They were a way to build awesome, multiphase boss monsters like you see in video games and to fix some problems with the D&D action economy. That whole two-headed, two-tailed, bifurcated snake thing was me explaining why my math worked.

For those of you late to the party, by the way, there are two things you need to know to make sense of Banjo’s question. First, there was a time when I suggested telegraphing a monster’s plan to use a spike attack next round at the end of its current turn. Second, multiphase boss monsters aren’t limited to one turn per round. They get several spread through the initiative order. The precise number changes. Some monsters slow down as you beat them down and lose actions as they fight. Others get enraged as you piss them off and gain actions as they fight.

Banjo is getting a weird interaction because the monster is signaling the use of a spike attack on a middle turn of its round for use next round, but still gets another turn or two before the spike action actually goes off.

And this, kids, is why we don’t mix drugs. All that stuff I said about combining hacks? This is what happens. You get these weird-ass interactions when two hacks are touching the same subsystem. My old way of telegraphing, which I have abandoned in favor of top-of-the-round telegraphing as described above, and my multiphase boss monsters both grind themselves against the turn order in different ways, which means they’re grinding on each other.

And because neither was designed to exist alongside the other, they’re grinding on each other without consent.

If you ever wonder why I explain everything I do down to component atoms, this is part of the reason. Of course, I want to show you how to think about game design so you can make your own hacks, but I also want you to know why my hack is doing what it does, so if you have to make a judgment call to fix a bad interaction, you’ve got my voice in your head helping you.

Above, for example, I pointed out that the big deal with telegraphing was that it let players know when a spike was coming. Remember? “If you know when Spiky Sword-Spiker is going to spike for 18, you know when to Dodge action.” So, if a creature gets multiple turns and some of them come between the telegraph and the spike, the players don’t know anymore when the spike is actually coming. You’re telling them, “Here it comes… eventually… anytime now… not yet… could happen anytime really…”

That’s why they’re confused.

The obvious fix is just to say that the telegraph turn must always come right before the spike turn. Or to say the telegraph turn must always be the last turn in a round and the spike turn must always be the first turn. You need to guarantee that nothing ever comes between the telegraph and the spike.

But that might not be enough. Why?

Well, the other thing I said above was that enough players need enough of a chance to do something about the telegraphed spike for it to make a difference. If a monster gets two or three turns every round, there might never be enough time between telegraph and spike to give the right players a chance to respond.

Of course, my top-of-the-round telegraphing carries the same risk. It leaves the question in the fickle fingers of the initiative system to decide how many characters get a chance to do something about this telegraph in this combat. On average, that isn’t usually a huge problem, but once in a while, the party’s slow off the mark and the fight gets harder because of it.

That said, because I stick to the system’s damage recommendations anyway, a fight in which the party can’t benefit from telegraphing due to crappy initiative is just a normal fight. It’s no more dangerous than anything the unmodified system says to throw at my hapless victims.

And because I also designed my multiphase boss fights to the system’s core math adjusted to balance out the extra actions and phases, that should be true in a boss fight. If the monster’s actions line up so the right player doesn’t get to act between telegraph and spike, it won’t demolish the party more than any normal fight would.

Which also shows you why I work so hard to stay as close as possible to the system’s actual rules in everything I do. I work hard to make sure that if my hack breaks, it doesn’t break your game with it. None of my hacks do any more damage to your game than has already been done by whatever mad Cthulhu monster is currently controlling the diseased brains of the designers at Wizards of the Coast.

The Angry GM: Staring directly into the game design abyss so you don’t have to.

Anyway…

I think, Banjo, if you just stop letting anything come between the telegraph and the spike, you’ll be fine. After all, boss monsters don’t get three turns every round; they either speed up or slow down over the six-round fight. So if you just stick to an always spike the next turn after the telegraph rule, it’ll just be the equivalent of the telegraph window getting bigger if the monster slows down or smaller if the monster speeds up. That actually seems kind of cool. At the very least, it should be a good enough answer to get you by for a while.

Hopefully long enough for some sexy gaming genius to finish building one unified system that’s designed to do all these amazing things at the same time.


[jetpack_subscription_form]

7 thoughts on “Ask Angry: The Telegraphing “Hack””

  1. I’m in the middle of a monster building blitz for my next campaign right now, so this gives me a lot to chew on. Thank you!

  2. If you are using a system with cyclic initiative, do you modify when you telegraph so as to not leave someone always behind and unable to react, or is that just the price of rolling lower than team monster on initiative?

  3. “If your hit points are low enough that you can absorb two more regular hits but a spike hit will kill you…”

    How do players figure this out during a 3-5 round combat with a high degree of variance on rolled attack damage? Is it worth using average damage instead of rolled damage to make it a bit more obvious what damage different attacks actually do? Or is a 18 damage spike hit (~5d6+2) just sufficiently outside the plain 6 (~1d6+2) average damage hit that it’s super obvious (3x seemed pretty freaking obvious when I figured out the rough dice for a super-melee attack).

    • You’ll probably describe the big attacks differently, so they’ll already know to expect *more* damage. If you roll damage openly they can do the math themselves, if not I guess you could start announcing what dice you’re rolling?

      • Well sure, but if the monster rolls damage poorly on its super attack and well on its baseline attack the difference between the two may not be noticable to a degree that tells the players anything.

        Golem’s point above was enough to give me flashbacks of my old GM rolling for damage and the mental feeling of “oh shit that’s a lot of dice.” That tends to stick around, even if players luck out and take minimal damage. I might even sulkily pout about getting nothing higher than a 2 on 5d6. I get it; there’s more to the gamefeel in the moment than just 7-12 vs. 8 damage on the extreme edges.

        • There are a lot of different factors here, but I think a lot of them come down to the fact that the way you run a game transcends any single instance of a ruling you make. Angry’s talked about this before with things like how undead function or whether you can cast firebolt underwater or things like that. (A good example would be how whether you make players track and consume ammunition or rations will change how they treat ammunition and rations.)

          So for example, even if that one monster rolls shit damage on its damage spike in that one combat, it’s a pattern of description that your players can learn to expect and pick up on, which leads to “Oh, yeah, the GM did make it obvious that the ogre was winding up to wallop me, and I didn’t respect that the way I should have, and now I’m rolling death saves,” which is a different feeling from “What? It used its big attack? That’s so unfair!”

          Similarly, if the players know that a spike attack is coming and they get hit by it and the dice roll small, it’s a great feeling of good luck or escaping by the skin of their teeth. Just like as a player rolling a 2 on a d12 for damage feels like the worst thing in the world, having a monster wind up and then whiff its attack feels amazing.

          All of this is tangential to your actual question, which was, “How do the players know they’re about to be dropped by a spike attack?” and the answer, I think, is ultimately that they just learn to intuit it. Once again, lots of different combats over lots of different sessions, not a single combat in isolation. If I have 48 HP and I’m down to 12, I know that that thrall wielding a longsword in one hand almost certainly isn’t gonna drop me, but the vampire charging up a spell behind the thrall really might. It doesn’t matter whether the vampire’s doing 5d6 damage or 3d8 damage or what have you, I can still intuit, “I think I’m okay against the normal guy, and I think I’m in trouble against the big spike,” even without the numerical details.

          At least, that’s my take on it.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.