G. asks:

A villain in my campaign has run away to fight again another day. The players want to pursue them, but the villain is in hiding. How many clues should I prep for a revelation that I don’t want the PCs to access?

One thing to consider is what you mean by “access.” There are lots of non-actionable revelations you can have about, say, the Lost City of Arthak-Val without ever learning where it is or how to find it; i.e., without being able to access the Lost City. The same can be true about your villain’s hiding spot.

But if by “access” you mean “learn the revelation,” then the answer to how many clues you should prep is zero. The Three Clue Rule isn’t about how many clues the players need to draw a conclusion; it’s about having redundancy for missed or misunderstood clues. A single clue can (and usually should) be enough for the players to figure something out.

Of course, that seems to be the case here: You have a revelation that the players want (“the bad guy has gone to location X”) that you don’t want to give them.

My personal druthers here are going to default to playing to find out: If the players can figure out some plausible way to learn that information, let’s roll with it and see what happens.

What I don’t need to do, though, is go out of my way to provide them with those leads. The Three Clue Rule, it should be remembered, only applies to essential revelations. If the finding the bad guy is not, in my opinion, an essential revelation, then I’m under no obligation to provide three clues or any clues for it. I’m just saying that I won’t automatically block the players if they come up with some clever idea.

When your first impulse is “you can’t find that information,” however, here are a few things to consider.

First, looking for the thing they want doesn’t find what they want (i.e., the bad guy), but it does find something interesting. In other words, reward the players’ efforts, albeit not in the way they were expecting.

Second, consider rephasing your initial impulse from “there’s no way to find the bad guy” to “finding the bad guy will not be trivial.” In this case, “not trivial” means that there isn’t a direct vector from the PCs to the bad guy. Instead, the PCs will have to work their way through several revelations to get to the revelation they want.

For example: You don’t find the bad guy, but you do learn that the only person who might know where the bad guy is hiding is Sebastian Raoul, his lieutenant. Where’s Sebastian? Well, turns out he’s gone to ground, too. Looking for a lead on Sebastian turns up his accountant. It takes a raid on an armored compound to get your hands on him. He doesn’t know where Sebastian is, either, but he knows that Sebastian’s bank accounts are held in a Swiss bank. So if you break into the bank, you might be able to trace where the account is being accessed from. That, finally, leads you to Sebastian, who can give you a lead on the bad guy. (Although possibly still not directly to the bad guy.)

During this whole sequence, of course, the players are engaged and excited. They don’t feel thwarted. They’re constantly making progress towards their goal!

Meanwhile, the rest of the scenario — whatever it might be — is still going on. Each of these steps along the path to finding the bad guy can also be seeded with additional clues and rewards that can assist or direct the PCs towards the other stuff happening in the scenario.

On a similar note, you can also respond to this impulse by immediately dogpiling the PCs with distractions. Toss lots of scenario hooks at them. Pull out a bunch of proactive nodes. Sure, they want to go looking for the bad guy, but there are vampires attacking the orphanage right now, so that’s going to have to wait. (Note: You’re not making that decision for them; you’re just putting them in a situation where they need to choose between a long-term goal of finding the bad guy and responding to immediate crises.)

DESIGNING VECTOR PATHS

The example of extending the path to a revelation may seem really complicated, but this is why I find thinking in terms of vectors so useful.

To unpack this a bit, it can be natural to think in terms of where the PCs are now and ask yourself, “What do they need to do from where they are to get where they want to go?”

If there’s a clear answer to that, great. But if there isn’t, you can give yourself a real headache trying to figure it out. Which makes sense: You’re basically trying to solve an imaginary mystery for which you haven’t created the clues yet.

This can also lend itself to overly simplistic resolutions: “I’m at Point A, how do I get to Point B?” tends to result in a straight line from A to B, which is exactly what we’re not looking for right now.

Instead, start from where they want to go (or what they want to know) and ask yourself, “How do they get there?” and/or “Why is it difficult to get there?” Then take the answer to that question and ask it again.

So:

• How do they find the Bad Guy? Sebastian, his lieutenant, knows.
• How do they find Sebastian? By tracking his banking activity.
• How do they find his banking activity? By accessing his Swiss bank account.
• Why is it difficult to access the Swiss bank? It has to be identified.
• How do they identify the Swiss bank? By getting their hands on Sebastian’s accountant.
• Why is it difficult to get their hands on the accountant? Because he’s holed up in an armed compound.

Then you just flip this around to determine the path.

The one trick, though, is that the PCs need to understand that this IS the path. Otherwise, they’re just blindly fumbling around. (If you tell them “there’s an accountant named Bartolo Russo holed up in an armed compound,” they’ll have no idea why they should care about that.)

To close the loop, PCs can figure out the path through non-actionable revelations: “To find the bad guy, you have to find Sebastian.” That’s a non-actionable because they don’t know where Sebastian is. You could have them do another investigation to figure out where Sebastian is, or you could pack that into the “find Sebastian” revelation (i.e., the revelation is “you’ll have to find Sebastian, and Sebastian’s only known associate is an accountant”).

One last subtlety I used here is to obfuscate an intermediary step when the PCs were figuring out the path they needed to pursue: They know they need the accountant, but they don’t realize that the accountant can’t send them directly to Sebastian (and they’ll need to go through the Swiss bank). This is a good technique because it stops the resolution of the path from being rote (you discovered all the steps, now you do all the steps); and it can also tighten up the “finding the path” phase of things to reduce the perception of “endless brick walls” without any sense of forward progress.

The particular example given here is also quite linear. This can be fine, but you can add some extra dynamics by providing multiple vector options at a particular step. For example, instead of the accountant being Sebastian’s only known associate, you might have three different known associates the PCs could potentially learn about and use to track him down. (Keep in mind that you don’t need to fully prep a path until the PCs actually take it. For example, you don’t need to prep the accountant’s compound until the players tell you that’s where they’re heading in the next session.)

Go to Ask the Alexandrian #7

Ash wraiths are the undead, burnt remains of corpses. They take the form of a swirling cloud of gray-black ash, usually vaguely humanoid in shape. Although they cannot properly be said to have corporeal bodies, their touch retains the passionate heat of their deaths and is scalding to mortal flesh.

Hauntings. Ash wraiths are most often found haunting ruined crematoriums or lingering near the horrors of execution pyres, but there are also tales of woods being haunted by ash wraith animals for years or even decades after the devastation of forest fires.

From One, Many. Ash wraiths can be created using the animate dead spell, although it requires special knowledge to do so.

Necromancers who perfect the rare art of creating ash wraiths are often able to claim two undead servants from a single corpse. Although the rites which create a skeleton usually consume the flesh of the corpse (if it has not already rotted away), a necromancer can first flense the corpse. The flesh and fat is then burned, providing the ashes for the wraith, while the skeleton is animated separately.

Undead Nature. An ash wraith doesn’t require air, food, drink, or sleep.

ASH WRAITH

Medium undead, neutral evil

---

Armor Class 12

Hit Points 18 (4d8)

Speed 0 ft., fly 30 ft. (hover)

---

STR 7 (-2), DEX 14 (+2), CON 11 (+0), INT 6 (-2), WIS 8 (-1), CHA 5 (-3)

---

Damage Resistances acid, cold, fire, lightning, thunder; bludgeoning, piercing, and slashing from nonmagical weapons

Damage Immunities necrotic, poison

Condition Immunities exhaustion, grappled, poisoned, prone, restrained

Senses darkvision 60 ft., passive Perception 9

Languages understands all languages it knew in life, but can’t speak

Challenge ¼ (50 XP)

Proficiency Bonus +2

---

Ashen Movement. The ash wraith can move through other creatures’ spaces as if they were difficult terrain.

Undead Embers. If damage reduces the ash wraith to 0 hit points, it must make a Constitution saving throw of DC 5 + the damage taken, unless the damage is radiant or from a critical hit. On a success, the ash wraith will reform in 1d4 hours.

---

ACTIONS

Fiery Touch. Melee Weapon Attack: +3 to hit, reach 5 ft., one target. Hit: 5 (1d6+2) fire damage.

Design Note: Ash wraiths are designed to provide an incorporeal form of undead that can be used in a fashion similar to skeletons and zombies. (In other words, minor undead that aren’t mind-searingly terrifying.) They were originally created for the original 1974 edition of D&D, and that stat block can be found here.

Go to Table of Contents

In Storm King’s Thunder there are several factions active in the Savage Frontier which the PCs will either interact with, join, fight, or all three:

• Emerald Enclave
• Harpers
• Order of the Gauntlet
• Zhentarim

For the DM, however, it’s quite difficult to come to grips with these factions, as references to their current activities and resources are scattered randomly throughout the book with only limited cross-referencing.

So I’ve assembled this reference to make it easier for you to juggle these factions in play. The PCs are looking for a faction? A faction member is fleeing to their nearest safehouse or summoning reinforcements? You’ve got a random encounter with a faction member and you want to drop a lead pointing to a local faction operation?

Now you can just consult the reference below and be good to go.

Note: Although I’ve opportunistically included some references to other sourcebooks, this should not be interpreted as a complete survey of those or any other published sources.

Finding a Faction: If the PCs belong to a faction, are in an unfamiliar area, and would like to try to find a local safehouse or operative they can make a DC 15 Intelligence (Investigation) check. The check can be made at advantage in a major metropolis (e.g., Waterdeep) and should be made at disadvantage if they’re in a tiny community in the middle of nowhere (e.g., Nightstone) unless there’s a known presence described below.

If the check succeeds, they find their faction’s local presence. (If you’re at a loss for what that might be, just pull one of the “Wanderers & Random Encounters” listed for the faction below.)

If the check fails, they either failed to find the local faction presence (if it’s described below or if you determine that there should be a local faction presence) or it means that their faction isn’t active in the area.

EMERALD ENCLAVE

• Goldenfields, a major stronghold of the Enclave. (p. 44)
• Fireshear: Emerald Enclave runs a griffon stable overseen by Dasharra Keldabar. (p. 83)
• Jalanthar: Quinn Nardrosz, the head of the Council of Elders, is an Enclave member. (p. 94)
• Shadowtop Cathedral, a meeting place of the Enclave overseen by the treant Turlang. (p. 107)
• Waterdeep: Klarz, the captain of the Koalinth, owes the Emerald Enclave his life.

Wanderers & Random Encounters

• Aerglas, a moon elf who hasn’t been seen in many years. (p. 51)
• Tharra Shyndle, a druid and friend to the treant Turlang. (p. 51)
• Zindra Winterbow, a scout in the area of Triboar. (p. 57)
• Vordana Jezral, a ranger. (p. 71)
• Saarvin, a ranger and self-proclaimed King of Frozenfar. (p. 71)
• Ghalvin Dragonmoor, native of Goldenfields held prisoner in Grudd Haug. (p. 144)

HARPERS

• Bryn Shander: Beldora is the local Harper agent, disguised as a homeless beggar. She has a sending stone connected to Thwip Ironbottom in Hundelstone. (p. 40 & 249; gives quests on p. 44)
• Hundelstone: Thwip Ironbottom, an inventor, is the local Harper agent. Has a sending stone connected to Beldora in Bryn Shander. (p. 44 & 92)
• Silverymoon: A haven for Harpers, but no details given.
• Triboar: Lord Protector Darathra Shendrel is a Harper agent. (p. 53 & 253)
• Yartar: Harper agents are established here. See Inner Circles.

Everlund

• Moongleam Tower: Harper stronghold. Overseen by Moonlord Davianna Yalrannis. (p. 82)
• Krowen Valharrow, a wizard who lives in Moongleam Tower (p. 44 & 60 & 82).
• Dral Thelev: Harper agent living in Danivarr’s House. (p. 60)

Waterdeep

• Open Lord Laeral Silverhand: A friend to Harpers and will agree to meet with them. (p. 157)
• Lord Zelraun Roaringhorn: A Harper agent. (p. 42)
• Captain Zaldar Floshin, captain of the Kelpie’s Kiss. Hires his ship to the Harpers. The bosun, Ilkara Levari, is a Harper agent. (p. 220)
• See Dragon Heist, p. 37, for additional details.

Wanderers & Random Encounters

• Artus Cimber, a former harper who is the last known owner of the Ring of Winter. (p. 1)
• Endrith Vallivoe, retired caravan merchant and friend to the Harpers. (p. 232)

Inner Circles

• A network of teleportation circles controlled by the Harpers. (p. 117-18)
• Everlund Circle: Located in Moongleam Tower.
• Loudwater Circle: Located in the Smiling Satyr tavern.
• Mirabar Circle: Located in stable house loft attended by Zazspar Bronzefire.
• Neverwinter Circle: Located in the attic of a rowhouse.
• Waterdeep Circle: Located in the City of the Dead.
• Yartar Circle: Located in a dilapidated villa.

ORDER OF THE GAUNTLET

• Sir Baric Nylef (Bryn Shander, p. 44 & 249)
• Sir Lanniver (Neverwinter, p. 44)
• Hawk’s Nest (p. 90) is controlled by the Order and raises hippogriffs.
• Helm’s Hold (p. 90, SCAG p. 85) is ruled by a splinter sect of the Order called the Order of the Gilded Eye.

Waterdeep

• Waterdeep has faction representatives. (unspecified in SKT; Dragon Heist, p. 39)
• Halls of Justice, a temple of Tyr located in the Castle Ward. (DH, p. 39)
• Arilosa Adarbretn, captain of the Coin Toss and financial supporter of the Order. (p. 220)

Wanderers & Random Encounters:

• Lady Hariana Hawkwinter (p. 71)
• Sir Jordeth Tavilson (p. 71)

ZHENTARIM

• Nightstone Team, including Kella Darkhope (p. 25) and Xolkin Alassandar’s agents (p. 27).
• Triboar Travelers, a mercenary group based out of Triboar (p. 54). Led by recruiter Urlam Stockspool.
• Fireshear: Zhentarim mercenaries have been hired to guard griffon stables controlled by the Emerald Enclave (p. 83).
• Loudwater: The high lord, Telbor Zazrek, is a paid puppet. (p. 97)
• Mornbryn’s Shield (p. 99) has been taken over Zhentarim strike team led by Oboth Thornstell.
• Rassalanter: Yondral Horn, innkeeper at the Sleeping Dragon, is on Zhentarim payroll. (p. 104)

Daggerford

• The city has hired a large Zhentarim mercenary force led by Nelkin “the Snail” Danniker (p. 80).
• Zhentarim agents in Daggerford are handing out interest free loans to compete with local moneylenders. (p. 53)
• Zirazylym: An undercover bronze dragon and regular customer at the Happy Cow. (p. 80)

Orlbar

• Bargewright Inn (p. 73), controlled by Zhentarim led by militia-master Chalaska Muruin and innkeeper Nalaskur Thaelond. Also the vampire Arik Stillmarsh.
• Zhentarim fortified tower west of town that was recently abandoned due to a giant attack (p. 80).

Waterdeep

• Sees tensions between Zhentarim and Xanathar’s Thieves’ Guild. (unspecified in SKT; see Dragon Heist)
• Captain Drashk, captain of the Lost Cause. (p. 221)

Trade Routes

• Dawn Pass, the Zhentarim have built a stone gatehouse between Llorkh and Parnast (p. 80).
• The Black Road, a trade route controlled by the Zhentarim (p. 77).

Wanderers & Random Encounters:

• Sorelisa Zandra and Naeremos, bounty hunters (p. 43). Looking for Weevil in order to protect him.
• Shalvus Martholio (p. 46 & 250, gives quests on p. 51). Shalvus works for Nalaskur Thaelond (see Bargewright Inn). He later returns to the Bargewright Inn waiting for a new assignment.
• Frylo Nelgorn and a Zhentarim team are meeting fire giant representatives in the ruined city of Nesmé. (p. 100)
• Nilraun Dhaerlost, a Zhentarim mage captured by Storvald and helping him search for the ring of winter (p. 156).
• Jasper Dimmerchasm, who was sent to negotiate with Zalto and is now held prisoner. (p. 184)

Former Holdings

• Llorkh: Zhentarim previously conquered the town, but abandoned it when the mines dried up (p. 96).
• Newfort: Originally founded by the Zhentarim, but they’ve lost their influence. (p.101)
• Thornhold: Formerly held by the Zhentarim, but now controlled by dwarves. (p. 111)

Other

• Everlund: Zhentarim has a strong presence, but no details are given.
• Mirabar: Zhentarim has strong presence, but no details are given.
• Neverwinter: Zhentarim has strong presence, but no details given.
• Silverymoon: Zhentarim has strong presence, but no details given.
• Yartar: Zhentarim has strong presence in Yartar, but no details given.

Go to Storm King’s Remix

The likho is a lithe, slight humanoid with slick, purple-gray skin. Its slim limbs are wiry and muscular. Its face is dominated by a single large eye, beneath which are two thin slits for nostrils and a narrow gash of a mouth filled with needle-like teeth.

It has a strange, ever-changing gait — sometimes walking on its hands, sometimes on its legs, sometimes racing on all four — and will often vault and climb and clamber with wild abandon, slipping in and out of shadowy bowers or leaping out of black waters to surprise those peering into the deeps.

Personification of Misfortune. In the folk tales of the frontier, the likho is seen as the living embodiment of ill fortune and evil. “He’s had the likho on his back” is a saying that describes those who have suffered from a series of misfortunes. “Don’t stare the likho in its face” is a proverb suggesting that one should not tempt fate.

There are many who think this is just a turn of phrase. But, of course, the likho is quite real, and while most who suffer setbacks are just unlucky, some truly are cursed by the likho.

In some isolated communities that have a long history with the likho, lichy is a slang term that means something shoddy or unreliable. Some may also refer to likhoy, those who are too daring or foolhardy (and thus risk bringing ill fortune to both themselves and those around them).

Likho Items. Likho can create special bait items. These are often made to look quite valuable — e.g., a sword with a hilt of gold — in order to tempt the greed of their victims. Anyone touching a likho item will find that it is stuck in place and that they are unable to release it. (Wrenching their grasp free requires a DC 22 Strength check or a remove curse spell.) Furthermore, the likho who made the item is alerted as per an alarm spell. As the likho draws near, the one attached to a likho item will feel their presence growing like a darkness in their mind.

Many are the tales of those who have cut off their own hands in order to escape the approaching likho.

Likho’s Bargain. It is said that a likho can sometimes be bargained with. Its own evil can be turned back upon itself, if one can offer a great temptation or something of great worth related to a deadly sin. (Most commonly greed, like a blacksmith offering to make it a precious item or a wizard offering to conjure it a magical feast.)

In truth, however, the likho rarely honors these bargains: it will take what is offered and then betray the one who made the bargain with it. However, the clever can sometimes trick or cheat the likho.

LIKHO

Small fey, chaotic evil

---

Armor Class 13

Hit Points 58 (13d6+13)

Speed 30 ft.

---

STR 10 (+0), DEX 16 (+3), CON 12 (+1), INT 12 (+1), WIS 12 (+1), CHA 14 (+2)

---

Skills Athletics +2, Deception +4, Insight +3, Stealth +5

Senses darkvision 120 ft., passive perception 13

Languages Common, Sylvan

Challenge 4 (1,100 XP)

Proficiency Bonus +2

---

Adherence: If a creature touches or is touched by the likho, they must make a DC 13 Dexterity saving throw. On a failure, the likho adheres to them and simultaneously vanishes, becoming both invisible and intangible. Truesight or other abilities that perceive the Ethereal Plane allow one to see the likho, which clings to the target’s shoulders from the Border Ethereal.

A character who has been adhered to by a likho feels a weight on their soul and suffers from bad luck. They suffer disadvantage on all checks and must make a DC 13 Constitution saving throw each day at dusk or suffer one level of exhaustion. They do not recover from exhaustion after long rests.

A remove curse spell will break the likho’s adherence, freeing its victim and forcing it to return to the Material Plane.

---

ACTIONS

Multiattack. The likho makes two claw attacks.

Claw. Melee Weapon Attack. +6 to hit, reach 5 ft., one target. Hit: 13 (3d8) slashing damage. If the likho hits with a claw attack, the target is subjected to the Adherence trait.

---

Kaiju already exist in D&D. And, using the rules, you can already fight them.

But these mechanics tend to shrink the scope of these creatures. You can square off with a tarrasque, for example, in basically the same way you would with an ogre and poke at it with a spear until it dies. It doesn’t really matter how many squares the tarrasque takes up on the battlemap; it doesn’t feel like you’re fighting something that’s truly enormous. (Particularly if you picture the scene and realize you’re really just tickling its toenails.)

So what should a fight like this look like?

For our touchstones, let’s consider the Bahamut fight form Final Fantasy VII: Advent Children:

The dragon fight from God of War 4:

And the Dweller in Darkness fight in Shang-Chi: Legend of the Ten Rings:

(Video Coming Soon!)

Which is particularly notable, I think, because it features kaiju on both sides of the fight, with human combatants wedged between them.

In each of these fights, there are also common elements that jump out for me:

• Ranged attacks obviously feature quite a bit. (Although they can usually be described as bouncing almost harmlessly off the creature’s thick hide, unless a particular weak spot can be hit.)
• In order to be effective, characters have to literally be on the kaiju.
• The fights feature lots of terrain being casually devastated… including, frequently, the places where the PCs are standing or were just standing a moment before.

Finally, for something a little different, let’s add literally this entire game:

Shadow of the Colossus has a very different pace from the other examples, which I think is useful for keeping in mind when considering the breadth of what kaiju encounters can be.

HEY! I DON’T WANT THAT!

Some of you reading this are undoubtedly thinking, “I don’t want humans running along dragon spines! It’s silly! I want grounded, gritty fantasy! It’s not realistic to think that a normal human could solo Smaug with a sword!”

Short version: These rules are not for you.

Long version: Neither is D&D. By which I mean that the unmodified rules for D&D already let high-level characters solo Smaug. So if that’s not the sort of thing you want your D&D characters to be doing, you’re already having dissonance with the system. Check out E(X): The Many Games Inside the World’s Most Popular Roleplaying Game for an approach that will let you dial in the experience you want.

DEFINING YOUR KAIJU

There are a lot of big monsters in D&D. What counts as a kaiju?

Some key things that I, personally, would think about are:

• Is this monster big enough that it’s basically part of the scenery? A very active part of the scenery, yes, but basically the size of a building or even bigger.
• Is this monster so large that it’s difficult to imagine someone standing on the ground next to them even being able to reach their vital organs?
• Is this monster capable of trivially destroying human-scaled objects while barely even noticing that they’re doing it?

I think the lowest cut-off that makes sense to me (again, speaking only for myself personally) would be at least the size of a storm giant. (Storm giants stand 26 feet tall, are probably 6-7 feet across at the shoulders, and their knees would be about 8 feet above the ground.) And I’d probably want to aim a little bit higher than that.

So as you’re looking at the kaiju rules below, think about what scale of creature they feel right for. Here are a few options to consider.

OPTION #1: GARGANTUAN CREATURES

The simplest metric would be to just declare all Gargantuan creatures to fall under the kaiju rules. This conveniently includes all our likely suspects: tarrasques, rocs, dragon turtles, ancient dragons, and purple worms.

Using this option, the rules for fighting kaiju would only apply to Large or smaller characters. (Huge or Gargantuan characters are close enough to the kaiju in size that no special rules need apply.)

OPTION #2: THREE SIZES LARGER

Alternatively, we could extend this logic to say that any creature three size categories larger than you is considered a kaiju. This would mean that Small creatures would have to treat Huge creatures as kaiju.

This makes a certain amount of sense. If we use our previous example of a 26-foot-tall storm giant, its size relative to a halfling would be like a 50-foot giant relative to a human. (This would actually be the same height as a tarrasque!)

The drawback, of course, is a practical one: PCs can be both Small and Medium size. When encountering Huge creatures, some of the PCs would consider them kaiju and others wouldn’t. You might consider this a feature (and even a great roleplaying opportunity), but it would undoubtedly add the possibility for confusion and probably some potential issues with balance.

OPTION #3: TWO SIZES LARGER

This is the option that treats storm giants and treants as kaiju-class foes for human opponents. However, it would also mean that Large creatures would be treated as kaiju for Small PCs, and Large opponents are actually quite common in D&D. So this would almost certainly result in the kaiju rules being used frequently.

OPTION #4: BESPOKE KAIJU

It’s a kaiju if I say it is.

You might choose this option if you want to include specific corner cases (like storm giants, who are near the high end of the Huge class). This can also be appealing if you just want to include the occasional kaiju-themed encounter in your campaign, but then not worry about the kaiju rules every single time some big monster shows up for a tussle.

THE KAIJU RULES

In order to engage a kaiju, you enter its space while moving or as a reaction to being the target of a kaiju’s melee attack. This usually requires some form of check (e.g., a Strength (Athletics) to jump onto the kaiju from above or a Dexterity (Acrobatics) to grab on as it flies past). This check is contested by the kaiju’s Dexterity (Acrobatics) check to avoid the little pests.

Being engaged with a kaiju usually means that you are physically on the kaiju in some way. Being engaged is an exception to the normal movement rules preventing you from willingly ending your move in another creature’s space. As long as you are engaged with the kaiju, you will be carried with the kaiju when it moves.

Characters who are not engaged with the kaiju suffer disadvantage on their melee attacks targeting the kaiju. Characters engaged with a kaiju gain advantage on their melee attacks targeting the kaiju.

Shake Loose: As a special melee attack, a kaiju can attempt to shake off anyone currently engaged with it. When they do so, all engaged characters must succeed on a Strength (Athletics) or Dexterity (Acrobatics) check contested by the kaiju’s Strength (Athletics) check. On a failure, the engaged character is shaken loose into an adjacent space of their choice and is no longer engaged with the kaiju. They must also succeed on a DC 15 Dexterity saving throw or suffer 2d6 falling damage (or more if the creature was flying at a height greater than 20 feet).

Siege Monster: All kaiju are given the Siege Monster ability. They deal double damage to objects and structures.

Kaiju Destruction: All kaiju are given the Kaiju Destruction ability. They can deal damage to structures within reach as a bonus action.

Design Notes: These rules are deliberately quite simple. Our goal is not to weigh the system down with a lot of detailed mechanics, but rather to provide a straightforward prompt for DMs and players to dynamically describe these battles.

ADVANCED KAIJU RULES

Flying Characters: Flying characters and characters on flying mounts do not suffer disadvantage when making melee attacks against a kaiju.

Engage with Vantage: If circumstances allow a character to attack a kaiju’s vulnerable areas, then, at the DM’s discretion, it will not be necessary to engage with the kaiju in order to avoid suffering disadvantage on melee attacks against it.

For example, a character might be located on a wall or in a tower that the kaiju is passing by. Or they might be riding another kaiju.

Such vantage points do not grant advantage on attacking the kaiju, but may grant advantage on skill checks to engage the kaiju.

Hey! I Was Standing On That! When a kaiju destroys a structure that a PC is standing on, they can attempt a DC 15 Dexterity check as a reaction to land on the kaiju and immediately engage it.

Helping Others to Engage: This can be done with a standard Help action, granting advantage to the aided character’s skill check to engage the kaiju.

Knocked Off: If a character is knocked off a kaiju, the DM may allow them a DC 12 Dexterity saving throw to grab hold of a lower point on the kaiju and remain engaged. In addition to deliberate enemy action (kaiju gnats or other allies fighting the PCs on the kaiju’s back), the DM might also call for such saving throws (possibly at a higher DC) in response to environmental conditions — when the kaiju smashes through a wall or flies through a waterfall, for example.

ROLEPLAYING KAIJU

Nothing in the rules of 5^th Edition requires motion, but these creatures are simply massive and even a single step that might only be a small adjustment for a human-scale character can easily chew up significant distance.

So you’re under no compulsion, but describe your tarrasques not only staggering back from mighty blows, but actually moving across the battlefield as they do so (and even chewing up their bonus action to unintentionally smash through a wall along the way). Have your ancient dragons constantly swooping back and forth across the battlefield.

Also keep in mind that these gargantuan creatures may not immediately pay any attention to the PCs, or simply disregard them as irrelevant. (In much the same way that we might see a chipmunk or sparrow in the woods and just… not care that much.)

This, in turn, sets up the moment when the kaiju is suddenly VERY MUCH PAYING ATTENTION TO YOU. That’s a big moment. Play into it.

It’s not unusual for the property damage inflicted by a kaiju to unwittingly prove its undoing: Leave large, heavy, sharp objects dangling precariously and then let the kaiju linger under them for a round or two.

REVERSE KAIJU ADVENTURE

The limited range of size categories in 5^th Edition (compared to previous editions) prevents this idea from being directly supported by the rules, but it might be fun to frame an adventure or encounter in which the PCs are the kaiju.

Their opponents might be diminutive Lilliputians or perhaps a scurrying mass of anthropomorphized mice. Either way, the kaiju mechanics work the same in both directions, and you can describe the little folk clutching the PCs’ hair or scurrying inside their armor.

Another option along these lines is to give the PCs temporary (or permanent) control over a gargantuan construct, which can benefit from its status as a kaiju-class combatant.