Hong Kong Task Force 88 was included in Free RPG Day 2016 as an introduction to Feng Shui 2. (You can still grab a PDF of it for free.) We’ve being using the scenario at conventions as part of Atlas Games’ Special Ops program. Our playtesting, however, has revealed that the scenario is running a little too long to fit comfortably into our four hour convention slots.

These notes, therefore, are designed to streamline the adventure, reorganizing its core structure largely around a 5 Node Mystery (with a twist!). You’ll need a copy of Hong Kong Task Force 88 to provide full background details and stat blocks. These notes are also likely to make more sense if you have already read the original scenario.

INTRODUCTION

A new designer drug is ravaging Hong Kong. DietRiot has exploded both uptown and downtown; it seems equally appealing (and equally available!) to both the upper classes and the lower classes. Reports on what the drug actually does are all over the place: Some describe it as a methamphetamine. Others as a hallucinogenic. It also appears to be almost supernaturally effective as a diet drug.

The authorities have decided action must be taken. A special task force – Hong Kong Task Force 88 – has been formed. You have all been selected (or volunteered) to be a member of this task force.

As you choose your characters, think about why or how your character was selected.

SCENE 1: THE DOCKS

• Generally effective to have 1-2 of the PCs be the “local cops” who are meeting the others at the Docks.
• Allow time for a brief discussion.

THE FIGHT: Blondie calls out some insult from the end of the dock. They turn to see him and a bunch of mooks wielding machetes.

• Blondie (HKTF88, p. 10) – make sure to mention the wifebeater he wears covered in English swear words
• Machete Mooks (HKTF88, p. 11) – 2 per PC

DURING THE FIGHT: At least one of the PCs should see Jian Wu watching the fight from the roof of a nearby warehouse. He has a distinctive dragon tattoo on one cheek. As soon as they notice him, he walks away from the edge of the warehouse and disappears.

SCENE 2: INVESTIGATION MONTAGE

Hard cut from the end of the fight to the precinct headquarters Task Force 88 is based out of.

CHEWED OUT BY THE CHIEF: The local police chief is screaming at them about property damage, disturbance of the peace, wielding weapons (do you know how much paperwork?!), etc. Whatever happened during the awesome fight in Scene 1, he’s pissed off about it. “GET OUT OF MY OFFICE!”

• After the door slams shut behind them, the rest of the detectives at their open office desks give the PCs a round of applause. One of them whispers that the chief is actually very impressed and wants them to keep up the good work.

TASK FORCE OFFICE: The Task Force has been assigned a random office in the precinct headquarters. There’s not a lot in there right now: A thin file folder with the DietRiot case file. An empty file cabinet. A desk. An empty cork tackboard.

• Note: Establish the tackboard because you’ll frame up on it later.

INVESTIGATION MONTAGE: Tell the players you’re going to do an investigation montage: Each of them will choose one line of potential investigation. Likely options include:

• Checking the casefile.
• Trying to track down that guy with the weird tattoo they saw.
• Roughing up local dealers for information.
• Talking to an old friend or other local contact for information.
• Analyzing samples of DietRiot in the crime lab.
• Conducting drug buys to roll up the local distributors for interrogation.
• Putting surveillance on known DietRiot dealers and monitoring their communications.

The actual methods they choose don’t matter except by context. Group them together in ways that make sense and present fast-paced, hard-hitting sequences that rapidly spill out the three major leads:

• There is a victim of DietRiot named Fen. You can talk with her at the Lucky Cat Apothecary.
• Jian Wu (“the guy with the tattoo”) can be found at the Neon 77 club.
• There are a pair of well-connected street dealers named Snake Eyes & Ed who are selling out of the Bird Gardens.

Each of these point to one of the Scene 3 investigations.

SCENE 3: THE INVESTIGATIONS & THE FIGHT

There are three different leads that the PCs can pursue after the investigation montage. Generally speaking, the order in which these scenes occur doesn’t make a difference.

At some point during this sequence, Blondie’s brother shows up. He’s pissed off that the PCs killed/arrested his brother and he’s looking for revenge.

(This probably works best with Scene 3A or Scene 3B, as Scene 3C already has a fight sequence in it.)

THE FIGHT:

• Blondie’s Brother (HTKF88, p. 14): He wears the same wife-beater that Blondie does, but his is covered with swear words in Chinese. And he has a pair of katanas, because everyone knows katanas are better. (To be honest, Blondie and his brother are basically tools.)
• Fist (HKTF88, p. 14)
• Reaper’s Boys (HKTF88, p. 15) – 2 per PC
• Interrogation: If interrogated, these mooks can give up the location of Reaper’s lab (see Scene 4).

SCENE 3A: FEN & LUCKY CAT APOTHECARY

• This scene is described in HKTF88, p. 12-13.

Key Clues:

• Reaper’s Card
• Fen’s grandmother thinks the drug blocks chi

SCENE 3B: JIAN WU @ NEON 77

• Neon 77 is a glitzy club of chrome, mirrors, and trance music.
• Or maybe it’s a sedate club with soft-tune jazz disco balls casting starscapes on the walls. Whatever works.

Jian Wu is framed differently in this version of the scenario:

• He has a dragon tattoo on his cheek.
• He’s Reaper’s Kowloon dealer for DietRiot.
• He’s not happy: The money was good; now he thinks it was too good. The drugs are too cheap; there must be some hidden agenda behind all this, but he hasn’t figured out what it is.
• He can point the PCs in the direction of Reaper’s lab (see Scene 4).

SCENE 3C: THE BIRD GARDEN

This scene is heavily revised for this version of the scenario.

• Snake Eyes & Ed (HKTF88, p. 10) are selling DietRiot in the Bird Garden (as described HKTF88, p. 17).
• Rather than an out-of-control talent manifestation, Ed casts spells to summon the fireworks foes (HKTF88, p. 18):
  • He summons the first one on his first turn.
  • On each subsequent turn, he can initiate a 5-shot action. If not interrupted, at the end of those 5-shots another fireworks creature is summoned.

In one run-through of this scenario I had Snake Eyes open up a door in the side of a tree and run through it, emerging back at Reaper’s lab. You could do that; or maybe it just turns into a chase sequence.

Key Clues:

• They know the drug blocks Chi.
• They can point the PCs in the direction of Reaper’s Lab (see Scene 4).

SCENE 4: REAPER’S LAB

This scene is described on HKTF88, p. 20-21.

• Don’t bother including Jian Wu.
• The key framing is that the PCs can observe the grungy warehouse from outside; and then only later catch a glimpse or burst into the gleaming, ultra-clean drug lab inside filled with scientists in hazmat suits watched over by goons in suits with SMGs slung over their shoulders.

THE FIGHT:

• Repeat (HKTF88, p. 21)
• Alora (HKTF88, p. 21)
• Mittens (HKTF88, p. 21) – I gave him the ability to jump around like a cat. Pretty much entirely descriptive, but gave him some nice
• Gangsters (HKTF88, p. 22) – 3 per PC

THE BIG FINALE?

In my playtests, time was generally running out at this point. The fight in Reaper’s Lab provides a great conclusion here, and you can generally wrap it up here.

Alternatively, the action can be carried into Scene 5 with these clues:

• Questioning anyone in the laboratory indicates that the drug design comes from the company DruDekTel.
• Searching Reaper’s unconscious/dead body finds a business card for Curt Raglan of DrukDekTel.
• Looking at the documentation in the lab links the process back to DruDekTel

SCENE 5: DruDekTel HEADQUARTERS

Okay, you know that incredible long-take fight from Tony Jaa’s The Protector? The one where he fights his way up a long spiraling ramp inside an office building before finally reaching the luxurious office of the Big Boss at the top?

You’re not? Okay. Watch that.

Yeah. We’re going to do that: DruDekTel’s HQ has that same architecture, with a big hollow center and a spiraling ramp that goes from one level to the next.

Things they can encounter on their way up:

• Massage parlor.
• Tea shop.
• Office cubicles.
• Slot machines.
• Food court.
• Copy machine nook.
• Video conferencing room.
• Drug research lab.

Have 3-5 levels. Each level has a number of mooks (use Reaper’s Boys and the Gangsters) equal to half the number of PCs.

Curt Raglan’s Office: At the top is Curt Raglan’s office.

• Curt Raglan (HKTF88, p. 22)
• Gangsters (HKTF88, p 22) – 1 per PC

During the fight, have Raglan monologue loudly about the true purpose of DietRiot:

• We will seal magic away forever by blocking chi!
• You fools are putting the entire world in danger! You can’t imagine the real stakes!
• The Guiding Hand will protect him. They cannot possibly win!
• The testing is almost complete! As soon as it stops killing people – well, as soon as they can get the mortality rate down to a reasonable level – they’ll put it in the drinking supply!
• The Four Emperors will never return!

Yada, yada, yada, and so forth.

Many moons ago, I wrote Prep Tips for the Beginning DM, a super-streamlined set of guideposts for a first-time DM to follow. The advice was aimed specifically at D&D/Pathfinder GMs, and over the years I’ve received a number of queries about how GMs can get started with other systems. The truth is that the advice is largely transferable. For example, here’s how you could get started running a fairly typical cyberpunk campaign where the PCs are a crew that runs heists and similar jobs in the style of William Gibson’s Neuromancer.

(You might be starting up a new Shadowrun campaign. Or maybe you’re hyped about the upcoming Cyberpunk 2077 and want to run a game like that for your friends. Whatever works. This advice is widely applicable.)

(1) Start with a simple run featuring a location-based crawl. Keep it simple! Make it a single building with maybe a dozen rooms. Keep the challenges inside the building firewalled (i.e., the PCs can generally muck around in Room A without also bringing everything in Rooms B-Z down on their heads) with the possible exception of a roving security patrol that will also respond to triggered alarms. Keeping things compartmentalized will make it easier for you to run; it’ll also give your players a chance to figure out their characters and the system.

(2) Do a couple of those. You can slowly start building the complexity. Introduce adversary rosters so that the complexes become more dynamic and active. This will increase both the challenge for your players in planning out their runs and the complexity for you in actually GMing those runs.

(3) Take a look a the Three Clue Rule and use it to create a linear investigation scenario: Go to Location A, find clues that lead to Location B. At Location B, find clues that point to Location C. Repeat until you reach the conclusion.

LINK IT TOGETHER

It’s okay to just run a purely episodic campaign where each run is independent from the last. But here’s a simple example of how you can link all of these things together: The PCs are hired by somebody to do a couple of jobs. Then their patron calls them with another job, but when they show up for the briefing they find him dead. Now they need to figure out who did it.

Discovering who their patron was, what he really wanted, and why he was killed will either wrap up the mini-campaign or wrap up Act I of the ongoing campaign and give you a nice launchpad for the rest of the game.

Note: You don’t need to prep all this before you start play. In fact, you shouldn’t because you’ll be learning stuff in play that you’ll want to implement in the next scenario you design.

All you need to get started is #1: A simple run.

As you’re wrapping up Act I, take a look at Don’t Prep Plots and Node-Based Scenario Design. Use those to build an Act II.

Read More at Gamemastery 101

The Necropolis had been built upon a low bulging hill that lay just along the Cliffs of Lost Wishes at the eastern edge of the city. As they moved a little further into the Necropolis, therefore, they were able to look over the top of the mausoleums and see seemingly endless rows of gravestones dotted with crypts of various sizes running up the hill. In the farthest distance, an the edge of the cliffs themselves, they could see an enormous, castle-like building.

I’ve talked about foreshadowing here on the Alexandrian before.

In Random GM Tip: Foreshadowing in RPGs, for example, I talk about the difficulties of foreshadowing in a non-linear, improvised medium (and three techniques you can use to work around that).

Random GM Tip: Adaptation & Reincorporation discusses how meaning is built over time through the repetition and reincorporation of creative elements. I also discuss the fact the foreshadowing can be thought of as the repetition or reincorporation of material at a point in time before the moment you actually created the material for.

For example, I know that certain features of the Necropolis are likely to become important later in the campaign, and so when the PCs arranged a funeral for Elestra’s python viper, I made a point of including some of those features (like the Dark Reliquary) into my description of the Necropolis.

This is also an example of opportunistic foreshadowing.

I didn’t plan for Elestra’s python viper to die. And I didn’t plan for her to arrange an expensive funeral for it. So I didn’t plan this bit of foreshadowing. I simply seized the opportunity while improvising the scene.

(You may note that this is not exactly hardcore foreshadowing, either. It’s literally just describing something that the characters happen to see. Which is fine. The point is to pre-establish elements so that when they later become the primary focus, they’ve already become an established part of the players’ understanding of the world.)

Session 20 is actually filled with examples of opportunistic foreshadowing.

When the PCs head to the Cathedral to seek advice from Silver Fatar Rehobath, that’s actually an example of how foreshadowing can build on itself: I had included Rehobath on the guest list for the Harvesttime party at Castle Shard because I wanted to establish his presence for later in the campaign. That’s an example of planned foreshadowing. It also put Rehobath on the PCs’ radar, though, and helped prompt them to seek his counsel here.

The inclusion of Prelate Adlam as the priest who recognizes Tee and gets her an audience with Rehobath, on the other hand, is an example of opportunistic foreshadowing. (He has his own significant role to play in future events.)

There’s also the White House: A gambling house that I know will become the center of attention later in the campaign. I’d already put together a planned bit of foreshadowing for the White House at this point (you’ll get to see that play out starting in Session 34; the actual pay-off starts in Session 91), but that’s no reason to forego the opportunistic foreshadowing here when Tee goes looking for a place to gamble.

The mrathrach game she sees being installed is also opportunistic foreshadowing, as is the strangely garbed knight she sees later in the Dreaming. (Tee’s training in the Dreaming Arts will frequently offer incredibly rich opportunities for both planned and opportunistic foreshadowing.)

If you want another example of planned foreshadowing, check out Running the Campaign: Foreshadowing Encounters.

SESSION 20A: FUNERAL FOR A PYTHON VIPER

April 27th, 2008
The 8th Day of Kadal in the 790th Year of the Seyrunian Dynasty

It was only a few all-too-short hours later before they were rousing themselves out of bed once again.

Ranthir was one of the first to wake up. For several days he had been eagerly looking forward to reading the sealed letter that the Iron Mage had given to them at Castle Shard during the Harvesttime party. He had placed the letter on his bedside table the night before, and the first thing he saw upon opening his eyes was the letter lying open.

IRON MAGE’S LETTER

My dear friends—

I am sorry that I could not deliver these instructions to you in person so that I might answer all of your questions. But, sadly, necessities of another nature will make that impossible by the time all of the particulars are known.

By the time this letter opens – which shall be no later than the ninth day of Kadal, if all goes well – the particulars will be known, and thus I have ensorcelled this parchment to reveal them to you.

On the twenty-first day of Kadal, the Freeport’s Sword – a privateer vessel from the Teeth of Light – shall arrive in the Docks of Ptolus. It carries a crate bearing my seal – a plated visor beneath crossed wands.

I ask that you report to Captain Bartholomew upon the arrival of the vessel, collect the crate, and keep it safe. I shall return for it no later than Nocturdei.

I stress that all of this is of the utmost importance. Many lives could be placed in great danger if the crate is not kept safe from the others who seek it.

THE IRON MAGE

(more…)

When I joined Atlas Games as the RPG Producer in December 2018, I inherited four of the best roleplaying games ever published: Feng Shui, Over the Edge, Ars Magica, and Unknown Armies. I knew that to do these games proper justice in the future, the first thing I needed to do was fully grasp their past. These were all games which I had played before (although, ironically, none of them in their current edition), but there was still a lot for me to learn. From day one, therefore, I embarked on a year-long project to not only bring every one of these games to my gaming table, but to also read every single supplement ever published for them.

As I worked my way through the corpus of Over the Edge supplements at the beginning of the year, I reflected on how difficult it is to produce scenario support for this type of RPG. Over the Edge is one of those games which presents an incredibly awesome setting filled to the brim with all kinds of amazing things for players and GMs to explore, but which — for precisely that reason! — doesn’t have a specific scenario structure that’s universally shared by its players. Without that universal scenario structure, it becomes very difficult to create published scenarios that can be reliably used by individual GMs.

(Which is not to say that Over the Edge hasn’t had some truly great scenarios written for it over the years. My personal favorites include Robin D. Laws Unauthorized Broadcast, Stephan Michael Sechi’s Welcome to Sylvan Pines, Jeff Tidball’s “In the SACQ”, Chris Pramas’ “The Jackboot Stomp,” and Greg Stolze’s “The Furchtegott File.” But although I love all of those scenarios, it would be virtually impossible for me to fit them all into the same campaign. Which is kind of my point.)

By contrast, for example, it’s very easy to create plug ‘n play scenarios for Shadowrun: Because every group is assumed to be shadowrunners who get jobs from a Mr. Johnson, all you need to do is frame your scenario as a job being offered by a Mr. Johnson and it can probably be used in 99% of Shadowrun campaigns.

One solution, of course, would be to simply eschew producing published scenarios for the game. There are any number of similar games which have done the same, focusing their product lines on cool setting supplements that give GMs even more awesome options for their campaigns. This , however, would be in significant conflict with my belief that roleplaying games flourish only in the presence of strong scenario support:

• Published scenarios are the single best way for GMs to grok how the game is supposed to work.
• Ready-to-play scenarios are the best way to convince GMs to try running the game for the first time.
• Incredibly cool scenarios are a great way to get people excited about running the game. (There’s any number of scenarios I’ve personally run because I just needed to see what would happen at the table; or that were so amazingly cool that I just had to share them with my players.)
• There are a lot of would-be GMs who, frankly, need the scenario support: Their time is limited and without published adventure material they won’t be able to run the game.

There’s also the fact the fact that I think published scenarios often improve campaigns in their own right, resulting in cool stuff that wouldn’t be possible otherwise.

Nonetheless, I knew that if I produced a typical scenario anthology for Over the Edge, a high percentage of the scenarios — no matter how good they were! — wouldn’t be usable by any given GM simply because they weren’t sympatico with their campaign. That would make the book substantially less valuable to everybody. I needed to fix that problem.

So I reached out to existing Over the Edge GMs to talk about the campaigns they had run and the campaigns they were looking forward to running with the new edition of the game.

What I slowly came to realize was that there were, in fact, several broad categories that most Over the Edge campaigns fell into. The specifics were different enough to create a crazy kaleidoscope of endless possibility, but the categories were tight enough that a GM operating within a given category would generally be able to adapt scenario hooks aimed at that category. So for the upcoming Welcome to the Island adventure anthology, I instructed my writers to include hooks for the following categories:

• Agents: Why would someone hire the PCs to get involved in this scenario? (Or, alternatively, why do the PCs need to do this on behalf of their patron without explicit orders?)
• Burger: How would someone who literally just got off the plane and caught a taxi from the Terminal get involved in this?
• Cloaks: Why would the various conspiracies on the Island care about this scenario (and send their trusty agents, the PCs, to deal with it)? Or, alternatively, what opportunity do the PCs become aware of and how do they become aware of it?
• Gangs: How do street-level operatives get tangled up in the scenario?
• Mystics: If the PCs are focused on mystic shit, how does that angle them into the scenario? Does someone/something seek them out due to their mystic powers? Do their mystic powers trigger or respond strongly to the situation? Does ancient arcane lore or a prophecy point them at the scenario?

It was also necessary to keep the hooks tight: Scenario hook sections in published adventures have a tendency to bloat up and claim more of the scenario’s word count than their utility warrants. This would be particularly true if people started writing up elaborate, multi-scene hooks for five different options. All we really needed was one or, at most, two paragraphs for each hook. (In no small part because, in my experience, GMs are going to heavily customize the hook to the specifics of their own campaign in any case.)

This actually lead to some initial confusion as we put this into practice. There was more than one person who produced a draft featuring stuff like, “Here’s stuff that Agents might find potentially interesting about what’s going on.” But I pushed: Brevity doesn’t equate to generality. A scenario hook needs to be specific. What is the specific thing that gets the PCs involved in the current situation?

HOOKS AT THE END

In the future, I will recommend that writers actually write their scenario hooks last. (Or possibly second-to-last depending on how you look at it.)

It probably won’t come as a surprise to most people reading this, but I want scenarios that are situations, not plots. You don’t necessarily need a specific hook in order to design a really cool, interactive situation filled to the brim with exciting stuff for the PCs to explore and for the GM to actively play. Requiring five different scenario hooks for each scenario actually emphasized this: Since the scenarios could not be dependent on any one on of these hooks, the scenarios quickly became independent of all of them, making it much easier for a GM who didn’t find any of those specific hooks interesting to nevertheless find a multitude of ways to draw their PCs into the situation.

At the same time, the fact that the scenario still needed to hypothetically support any one of those hooks also resulted in a richer scenario no matter which hook you used. The requirement necessarily forced the designers to create situations that were more dynamic, complex, and interconnected than they might have otherwise.

This is where this advice is potentially useful for homebrewers, too: If, for example, you use the Three Clue Rule to offer several options by which the PCs might become engaged with a given scenario, you will find that the need to include those three clues will inherently cause you to design more depth into the scenario. And that depth, in turn, will make it easier to improvise ways for the PCs to become engaged even if the three methods you’ve prepped don’t work for some reason.

For similar reasons, I suspect that even GMs who don’t have campaigns fitting one of the five broad categories I identified will nevertheless find it much easier to incorporate the scenarios in Welcome to the Island into their odd-ball campaigns. Having three to five different hooks makes it more likely that one of them can be trivially adapted to unusual circumstances. Or might feature a GMC similar enough to someone close to the PCs that you can make the whole thing intensely personal instead.