Go to Table of Contents

Random encounters can be used to achieve several different effects. In the case of the Avernian Hexcrawl, they’re designed to provide flexible content that will give a dynamic life to the Avernian wastelands, either as the PCs travel between keyed locations or while fleshing out those locations during play.

When using the Avernian Random Encounters, you may find it useful to check out:

• 5E Hexcrawl: Encounters, which breaks down the basic mechanics for random encounters. You can also use these tools to tweak the encounter check procedures described below.
• Hexcrawl Tool: Tracks, for details on running encounters from the Tracks results.
• Random GM Tip: Encounter Distance, which can be used to add encounter distances to your encounter generation procedures.
• Breathing Life Into the Wandering Monster, which looks at the actual practice of using procedural content generators at the gaming table.

The random encounters will use material from several sources, which are referenced using abbreviations:

• MM = Monster Manual
• TOF = Mordenkainen’s Tome of Foes
• GTM = Volo’s Guide to Monsters
• DIA = Descent Into Avernus
• EIA = Encounters in Avernus
• IE = Infernal Encounters
• EGD = Emirikol’s Guide to Devils
• SSA = Scientific Secrets of Avernus
• BOF = Book of Fiends 5E
• DDAL09-19 = Avernus Rising: Fang & Claw

ENCOUNTER CHECKS

Roll 2d10 and 1d12.

• A roll of 1 on 1d10 indicates an encounter. (Double 1’s indicate two simultaneous encounters.)
• A roll of doubles on d10’s (other than double 1’s) indicates that you should roll on the Designed Encounters table. Otherwise roll on the Procedural Encounters table for each one. (If you roll a designed encounter you’ve already used, roll a procedural encounter instead.)
• If the PCs are traveling on/along the Styx, there’s a 50% chance that any procedural should be rolled on the Styx Encounters table instead of the normal table.
• For each procedural encounter, check Track %, then Lair %.
• A roll of 1 on 1d12 indicates the PCs have encountered the keyed location in the hex. (If there are multiple keyed locations in the current hex, determine which one is encountered randomly.)

These results can be combined into a simultaneous encounter. (For example, rolling doubles on the d10’s and 1 on the d12 would indicate a scripted encounter taking place at the hex’s keyed location. Or you might roll a procedural tracks encounter plus a location encounter, indicating that the PCs have found tracks at they keyed location.)

DESIGN NOTES

I don’t typically use designed encounters (for reasons discussed here), unless there’s some specific design goal or advantage to be gained. In this case, as described above, I’m drawing encounter material from a wide variety of sources, and several of these include really good prepackaged encounters. It would be silly not to include this material, even though it adds a little extra complexity to our encounter checks.

Actually, I’m hoping that by using multiple dice and checking for doubles, that I have at least managed to streamline the number of dice rolls. (I was also quite pleased to easily generate simultaneous encounters with this system, which I felt were particularly important to include (a) given the fractious nature of Avernus and (b) to provide significantly more variety to the encounters.)

For procedural encounters, the tables have been designed to usually generate an encounter between 7^th Level Deadly (8,500 XP) and 12^th Level Hard (15,000 XP) for five PCs. Since multiple encounters can occur simultaneously, this creates a functional range from 8,500 XP to 30,000 XP (which is Deadly for 15^th level characters).

(Some encounters are an exception to this towards the lower end, where interesting or relevant fiends have been included even if would take a bajillion of them to hit the desired challenge range. They’ll either be scenic in nature or provide a little extra color when generated simultaneously with another encounter.)

This distribution is generally achieved on some form of bell curve, so the extremes will be relatively unusual. The net effect, however, is that Avernus will be very dangerous when the PCs first arrive and they will never be able to feel completely safe in Hell. This is deliberate because, well… It’s Hell. But it should also be mitigated to some degree because not every encounter should be thirsting for the PCs’ blood (which you can simulate using the Avernian Reactions table, or improvise according to your own predilections).

It is also possible to generate a very rare dangerous devil. These fiends are individually Deadly encounters for Level 12 to Level 18 characters (22,500 XP to 47,500 XP). They are obviously incredibly dangerous, particularly if they get combined with another encounter. Things to consider include:

• Assuming either indifference or a non-hostile intent on the part of these devils (e.g., the PCs see them flying far overhead or they offer the PCs a standing offer for their souls).
• Choosing to ignore the dangerous devil encounters entirely (or selectively ignoring them as appropriate).
• Increasing the Tracks % for these encounters (possibly to 100%) so that the PCs become aware of the danger without being immediately confronted by it.

Or just roll with it and let the dice fall where they may.

Go to Part 7H-B: Designed Encounters

Remixing Avernus – Capsule Reviews: Adventurers League Season 9 (Part 2 – Betrayal in the Blood) Remixing Avernus – Part 7C: Avernian Hex Key (Hexes G1 thru H6) Remixing Avernus – Part 7E: Warlords of Avernus