





Creating a Non-Lethal Solo Monster
WARNING: This post contains some serious spoilers for the end of Act One of my campaign, The Coming Dark. If you are currently one of my players on the WotC forums, I would prefer you stop reading now.
Almost every "solo" monster I've seen in the world of D&D has one specific purpose: kill the party. There's no question about it, a solo's objective is to inflict as much pain and misery as possible. It even says so in the Dungeon Master's Guide on page 55:
They have more hit points in order to absorb the damage output of multiple PCs, and they deal more damage in order to approximate the damage output of a group of monsters.
But does it really have to be that way? For that matter, do they have to deal any damage at all?
Scene Description
At the end of Act One in my campaign, there is a distinct possibility that one of the enemy will surrender and be taken alive. He will beg and plead that the party protect him from "it", and if they do he'll tell them anything they want to know. He never says what "it" is... But the party finds out soon enough: a creature has been sent to get him.
This creature is called a "Shadow Retriever". It has one specific purpose: recover the prisoner before he talks. And, for whatever reason it may be, they don't just want to silence him; they want him alive. So rather than send an army to get him, they send one creature. And it's a big one.
For the record, this creature is a Level 3 Solo Controller, going up against five level 1 PCs and an NPC ally (a Level 2 Soldier). Most people would consider that a TPK in the making, but that's assuming the Shadow Retriever actually attacks the party.
By design, the Shadow Retriever advances directly towards its intended target, effectively avoiding the rest of the party that gets in its way, until it accomplishes its mission. And only then does that it turns in to a no holds barred killing machine, but it should be considerably weakened by then.
The Retriever was an exercise to see how the party handles a creature that doesn't actually want them dead. In the original design it was meant to drop a boatload of detrimental effects on the party, leaving them to wonder how exactly they were going to kill this thing, only to realize there may not be a reason to take it on in the first place. The Retriever turns in to more of an annoyance than a threat.
Differing Tactics
In order to define the tactics of this creature, I made the creature have two different modes: a "recovery mode" and an "assault mode".
"Recovery mode" is its not-so-threatening version, when it has to complete its mission by targeting a single individual. In this mode it's not a destructive killing machine of chaos and hate, but rather it has tunnel vision and zeroes in on a single target until it has it. It honestly doesn't care about anyone else.
"Assault mode" is just what it sounds like: the destructive killing machine that everyone expects a solo to be. But, by the time it gets to this mode, it should have taken a fair share of damage while moving towards its intended target. Where most solo monsters have special powers that takes over when they become bloodied, this creature radically changes tactics by then and uses the powers it had since the beginning. It is now a credible threat.
There is one problem with the above: if the party leaves no prisoners, the retriever has no reason to go in to "recovery mode". Fine then... that's what the party gets for being so mean, I guess.
If a DM sees the stat block and uses that only, it will most definitely be a TPK. This creature can do a ton of damage while being rather resistant itself (since it's insubstantial) if played straight up according to the stat block and not taking its mode and related tactics in to consideration. It has destructive attacks just waiting to be used, but the DM must be aware that the creature wouldn't use them in whatever mode it's in. For this reason I considered making two separate stat blocks, but I thought that may be even more confusing.
A History of Revisions
This monster has gone through at least four major revisions. The first time I ran this monster in a playtest it was significantly weaker and the party plowed through it without any problem. So when I beefed it up a little, it became overly dangerous.
Here are some of the recent changes:
- The Retriever is a controller, so it has the ability to drop a truckload of effects on the party: it spawns wisps that restrain their targets (-2 to attacks, grant CA), it created a cloud (as a sustainable effect) that reduced lighting condition in an Aura 3 (so creatures with normal vision have to fight it as if it was partially concealed), and it had a rechargable power that could potentially blind the entire party (everything gets total concealment). With all those attack penalties, despite it having fairly low defenses the party could barely hit it.
- Originally, powers like Cloud Drift and Obscuring Cloud were rechargable powers. I made them both encounter powers now.
- The Retriever was originally "insubstantial", and that wasn't the modern day "insubstantial" (force damage doesn't get reduced, radiant damage removes trait until end of next turn)... It was "insubstantial" all the time. That effectively doubled its hit points to close to 300, which is comparable to solos many levels higher.
- The Smoke Wisps it generated now immobilize instead of restrain. Restraining had too many detrimental effects to be imposed by a Level 2 Minion.
In my current playtest (on the Wizards of the Coast online forums), almost the entire party is blind and one of them is restrained. They can't hit the broad side of the barn at this point, so the retriever happily waded through them and grabbed its target.
I've had one player already say that he "expects this to be a TPK" for the reasons I describe above: they can't hit the thing, are suffering through a ton of effects, and the creature seems to be able to do whatever the hell it wants.
In a manner of speaking, this monster becomes something closer to a trap/hazard or skill challenge: the creature has its intended target and is slowly lumbering away... How do you stop it? How do you free the captive prisoner? Do you even want to? Do you care that the guy that tried to kill you twenty minutes ago is being dragged off by something rather evil looking?
Suggestions
Even though this is a major spoiler for my campaign, I'm posting this so that others can see it and comment on it.
What do you think? Is this creature too lethal, too weak or just right?
Download PDF: The Coming Dark, Scene 1-8: The Shadow Retriever
(EDIT: Sorry... Corrected link. I'm having some issues with my hosting provider right now, and had a hard time uploading the PDF in the first place)
The Coming Dark, Chapter One – Campaign Preview
***WARNING*** If you are one of my players from the Wizard of the Coast forums, this could be some major spoilerage. I trust you to use your judgment when reading this, and if you do I hope you know to put it out of your mind come game time.
I've been kicking around the idea of providing a "preview" of my campaign, but the hardest part in doing such a thing is deciding what content to include that isn't horrifically spoilerish. Besides the introductory material, I'm hesitant to include any information in the individual scenes that might shed light on to what is going on in the campaign.
In any event, I have put together the attached "Campaign Preview." It doesn't show much, but it includes:
- The campaign introduction and character creation guidelines.
- The detailed description of Solis and the surrounding area, including maps of Solis itself and its surrounding area.
- What is pretty much a "random" encounter just outside the village of Solis.
- An encounter with a new type of enemy in my campaign: the "shadowtouched".
- Another small, non-critical encounter which is actually based on the "Hall of Spiders" encounter I had originally planned for the campaign.
- Appendix A, which contains most of the stat blocks for all the important NPCs in Solis.
- One sample piece of artwork and writing: the first page of the Book of Light.
- An explanation as to why I made this campaign in the first place.
It's not much, but it's something. Anyway... Here it is:
The Coming Dark, Chapter One - Campaign Sampler
I considered at one point giving Solis and the surrounding area the full "campaign setting" treatment, but I decided not to because it gives Solis too much scale. I *want* Solis to be small and helpless, surrounded in mystery, unaware of what evils lurk beyond its walls.
I am putting the finishing touches on TCD1, which for the most part involves editing it for the umpteenth time and creating the graphics for a few more handouts. Mechanically, it's definitely done and is actually in the hands of an "elite few" who have been curious about what the hell I'm up to.
It will be released in the very near future, and we'll see what happens then.
The Ubiquitous Sunrod
Many posts have been written about the single most common magic item in D&D 4e: the sunrod. Now it's my turn.
I was recently writing up the last area in Chapter One of my campaign The Coming Dark, and it involved rain. The atmospheric effects were somewhat inspired by the conditions in and around the setting in the Last Breath of Ashenport published in Dungeon #156, July 2008.
In that module there are very specific conditions in every outdoor encounter:
Rain (within Ashenport): Rain reduces visibility. All creatures more than 1 square distant have concealment (-2 to attack rolls). Perception checks take a -2 penalty. The rain automatically extinguishes any unprotected flames. At the end of every full minute (1o rounds), characters carrying protected flames, such as lanterns, should roll a saving throw. If they fail, those flames are extinguished as well.
Thunderstorms (outside Ashenport): The combined effects of precipitation and wind reduce visibility dramatically. Adjacent creatures have concealment, while creatures more than 1 square distant have total concealment (-5 to attack rolls). Perception checks take a -5 penalty. The storm automatically extinguishes any unprotected flames. At the end of every round, characters carrying protected flames, such as lanterns, should roll a saving throw. If they fail, those flames are extinguished as well.
The important issue above is the concept of "unprotected flame". First of all, it doesn't make a distinction between natural flame and magical flame. But is a sunrod a "flame"?
I assumed that it wasn't, as do most others on Twitter... but I have a tendency to be thorough, so I decided to look it up and see for myself.
For an item that every character has (two of them are included in every Adventurer's Kit), there isn't a whole lot of information about it. I couldn't find it physically described anywhere within the D&D 4e core manuals.
It's first appearance in 4e is in the Player's Handbook, under the section "Adventuring Gear" on page 221:
Sunrod: This minor magic item sheds bright light to a radius of 20 squares for 4 hours before burning out.
That's it?!? The single most common magic item in the entire game and it only gets a non-descriptive, one line blurb? You don't know if it looks like a torch, a glowstick, a candelabra, a human bone... Nothing. The only thing we know is that it's a "rod" that sheds light. For the record, the Compendium entry says the same thing, adding that you buy them in sets of two for 4 gp.
The only other mention in the core manuals that I know of is in the Dungeon Master's Guide under the "Fantastic Terrain" entry of Ember Moss (page 67):
Ember Moss
This strange Underdark moss is a useful ingredient in creating everburning torches and sunrods. It is highly flammable and burns bright. A character in a square with ember moss takes an extra 5 damage from all fire attacks and takes a -4 penalty to saving throws to end ongoing fire damage.
By that description alone, one would think that sunrods are fire-based, but again: nowhere is it mentioned that sunrods are actual flame.
So I decided to try and go a little farther back. In the D&D 3.5e Player's Handbook, it appears under the "Special Substances and Items" section (page 128):
Sunrod: This 1-foot-long, gold-tipped, iron rod glows brightly when struck. It clearly illuminates a 30-foot radius and provides shadowy illumination in a 60-foot radius. It glows for 6 hours, after which the gold tip is burned out and worthless.
It also appears, described as such, in the d20 SRD and in the "Goods and Services" and "Exploration" sections.
That description is significantly better - it sounds like a road flare - and one has to wonder why that text was left out of 4e. Also, it is worth noting that not only is the 4e description open for interpretation in many ways, but it is also arguably much more powerful: it illuminates an area 200' wide - over six times the width of the 3.5e sunrod - with bright light for four hours.
I'm having a hard time thinking of a modern day equivalent that could illuminate that much. To put it in perspective, here are other light sources listed in the 4e Dungeon Master's Guide on page 67:
Candle: Dim light in a Radius 2 (10'), 1 hour duration
Torch: Bright light in a Radius 5 (25'), 1 hour duration
Fireplace: Bright light in a Radius 5 (25'), 8 hour duration per load of fuel
Lantern: Bright light in a Radius 10 (50'), 8 hour duration per pint
Campfire or Sacrificial Brazier: Bright light in a Radius 10 (50'), 8 hour duration
Small fire creature: Bright light in a Radius 5 (25')
Medium fire creature: Bright light in a Radius 10 (50')
Large fire creature: Bright light in a Radius 20 (100')
Sunrod: Bright light in a Radius 20 (100')
Magma: Bright light in a Radius 40 (200')
Huge/Gargantuan fire creature: Bright light in a Radius 40 (200')
So in comparison, the common torch only illuminates an area 50' wide for one hour and a campfire only illuminates an area 100'. There are only two things listed in the DMG that outshine a sunrod: a volcano and "large/huge/gargantuan fire creature".
A sunrod must be like a signal flare; an area 200' wide is over half a football field. That's a lot!
Also, theoretically, sunrods cannot be extinguished by normal means; although I cannot find any place where it is discussed, many of the people I've asked online have stated that sunrods could conceivably work in high winds, pouring rain and even underwater.
With all that, why would anyone ever use a torch? You don't even need it to light things on fire: the Adventurer's Kit comes with flint and steel. And, if that doesn't work, there's always things like the wizard's Prestidigitation power (which explicitly states it can be used to light torches) or any other spell with the word "fire" in it that the resident sorcerer is just dying to cast.
Furthermore, even the Everburning Torch seems like a waste at this point. For the price of one Everburning Torch (50gp), you can buy twenty-five sunrods and get 100 hours of uninterrupted illumination in an area four times as wide as the torch. Does the torch seem practical at this point, especially considering you have to carry it around with a free hand?
So there's this magic item that is dirt cheap and far superior to all the other items that have similar function within the same price range. And from the moment every PC straps on their armor and weapon they already have two of them in their possession. And... There's no description? It's existance is glazed over as if these things would never be used by anyone. What happened?
When I brought up the subject of sunrods online, the DMs of the world pretty much agreed on the same opinion: they hate sunrods. And, when you think about it, you do have to agree with them; sunrods subvert pretty much everything:
- There is no need to worry about having one hand free to hold them. You can fasten them to your shield or tape them to your own body if you like. You can put one in your hair for all we know; without any guidelines on how they work, there's no way to determine what risk they may have (after reading the "Dangers" section on glow sticks in Wikipedia, it sure is tempting to come up with something).
- There is nothing you can do to plunge the party in to darkness. Lighting of the area becomes a null issue (although it might upset the drow in the party).
- With such a massive area of illumination, there's little chance of a monster hiding in some shadowy corner. Then again, some will argue that using a sunrod is telegraphing the party's position, as if to say "Hey, monsters! Yoo hoo! We're OVER HERE!!!"
As a result, I've heard many DMs effectively ban the use of sunrods, or at least make them extremely rare.
Me personally? I don't give lighting much consideration. Sure, if a room is dark I'll let the drow in the party have his fun and sneak around, but once the encounter begins I don't concern myself on whether the humans can see well in dim light or not. I have enough things to keep track of in combat.
But back to the issue at hand... Nothing indicates that sunrods are fire, so rather than have a very heated debate with the players I have no choice but to exclude them from the effects of the weather. I'll have to find some other way to make them miserable.
I have decided I really don't like sunrods in the manner they are presented (or lack thereof). I am tempted to take the advice of the people on Twitter and make sunrods extremely rare in my campaign setting.
The Architectually Unsound Fortress of Evil
While I was attending college at the University of Miami I worked as a lab tech on the School of Architecture's computer lab. While there I had access to all sorts of neat things, such as AutoCAD 10 (it was 1990... Humor me, OK?).
Let me clarify that I am not an architect: I'm a computer programmer. While some students were creating thirty story buildings with enough digital detail to impress Frank Lloyd Wright, I was thrilled creating empty 10'x20' rooms with extremely blocky furniture. Students around me were designing the Chrysler Building while I was designing a residence that looks like a shipping container. I spent four days designing a desk.
But even then I assumed certain things about designing a building: leave no space unused.
Bartoneus over at Critical Hits wrote an article called "The Architect DM: Negative Space in Dungeons", which mostly talks about dungeons... But what if it's not a "dungeon", at least in the classical sense?
One area of my campaign is a residence of sorts, a rather large keep or castle in a remote location. I began to design it as a normal residence would be designed: bedroom here, laboratory of death there... All with thin walls, almost as if the entire building was drywall on the inside. Then I went to look at other similar modules for research, and saw that quite a few modules had walls at least five feet thick, even if they were outdoor ruins (I do have to admit, the official Wizards of the Coast modules I looked at are pretty proper in this regard; the walls on their single story buildings were actually thin). Granted, quite a few structures were still "dungeons" in that they were carved out of solid rock, but why would a free standing building - a hovel, for example - have such an absurdly thick outer wall?
In a way, it makes sense in large structures and fortifications: you're designing a building that is meant to last and would have been built in a time similar to the Middle Ages. They didn't make buildings out of reinforced cinderblock, concrete and steel. There was no such thing as "drywall". Walls were solid stone, meant to support the massive building above them. Outer walls that were five feet thick were probably conservative (note: The moathouse near the village of Hommlet has an 8' thick outer wall I believe, at least according to map scale), and anything smaller and without some serious internal support would collapse under the weight of the giant fortress of evil built on top of it.
I looked blankly at the structure I designed, trying to imagine how a four story building of solid stone with paper thin walls would hold up. It did not bode well.
There's also some other things I noticed... Think about what you have in your own home. The "home" I was designing had no kitchen, which is just as well because it had no food storage, or a dining room for that matter. It also had five residents in it... but no bathrooms (when I posed this concern to someone else, their simple solution was "add a chamber pot in each room". Ew!). And, in what is apparently typical in D&D lair design, it had an easily activated death trap where pretty much anyone can trigger it.
The residents wouldn't last a week. They'll either die - painfully - or resort to cannibalism and eat each other. And, if they do survive, they'll be quite... uncouth.
But if I add a kitchen, I encounter the other problem prevalent in D&D campaigns: every room has a purpose, right? A kitchen can't just be a kitchen; there has to be a monster in it, or a trap, or treasure, or a major plot element... something! No? It's Chekov's Room, right? (WARNING: That's a TV Tropes link! Click at your own peril!) It must be important eventually!
All you DMs out there... Try to think of how many times you'd have to repeat to your players "it's just a kitchen" before they'll move on somewhere else (if you say "only once", you're lying). No matter how many times you tell them there's nothing in it, I bet you still had to roll at least one Perception check because the PCs requested it (or, in some cases, they rolled it themselves... "31! So what's really in this... 'kitchen', hmm?"). If they insist, I'm tempted to put a Sphere of Annihilation inside the stove just to "reward" their persistence.
The other option is to either make the walls out of unobtanium or infuse the structure with arcane power. "What prevents the building from collapsing under it's own weight?" "Uh... Magic!"
I haven't modified the area yet - it still has paper thin walls - but I'm seriously considering it.
And now I know why ProFantasy's Campaign Cartographer has about fifteen different clip art elements for a chamber pot.
Why We Do What We Do
Over ten years ago (god, has it really been that long?!?) I was part of a team called the Redeemed Assassins, creating a "total conversion" for Half-Life called "The Opera". It wasn't an easy time for anyone involved in the group; there was a lot of personal turmoils that made the completion of the game an impossible goal. And yet we persevered, making an intense sacrifice to finish the game we loved creating and after two years it was finally released. And, when it was released, some would argue that it wasn't well received (we released at the same time that the 800lb gorilla that was CounterStrike was taking over all the servers) and the game died a quick death.
On or about the same time I attended a convention where another individual was showing his game to the world, a game that he created because he wanted to, a game that he created in the manner that he himself wanted and not caring about what others thought about it. A game that took him several years to develop, all the time dealing with his own personal ordeals and internal strife in the company he founded. And when he released it, everyone hated it... But at the time he didn't care. He created the game he wanted to create, damn all the critics. And he had the personal satisfaction that he accomplished his own personal goal; he didn't give a damn what people thought.
That person was John Romero, and the game was Daikatana. Even if you weren't born eleven years ago (Daikatana was released eleven years and two days ago, on May 23rd, 2000), you've probably heard the story.
Before and after the development of "The Opera" I got asked the same question a lot, sometimes even by my own family: "Why?" Why suffer such a hard time creating something that gives us no financial gain? Why create something that only a handful of people would play?
Every time I was asked that question I provided the same response: if, through all my efforts and painstaking work, I create a product that ONE person in the world really enjoys, that's all it took. One person, that's all. Granted, I didn't have a bright yellow Ferrari Testarossa and almost Playboy model Stevie "KillCreek" Case to fall back on... but that didn't matter. I wasn't in it for personal profit. If I could make one person out - just one - there like what I've created, that was enough to make the whole ordeal worthwhile. Sure, I got more bad press and user backlash than you can possibly imagine, and some of it was quite painful to hear (nothing's worse than hearing "your game sucks" over and over again, especially on your own forums or through hundreds of emails), but in that festering cloud of hate I managed to find a few people that liked it. To me, "The Opera" was a success and a memory I will never forget.
A lot of independent game designers have lost that mindset. They have dollar signs in their eyes, hoping to create the game that everyone wants even if it means selling their own soul. I've met some game designers that have created products played my millions, and some of them are downright miserable because they're doing something they don't like to do (few will admit it, but you can tell). Everyone's looking for revenue these days, and they end up struggling to create what the fans want even if they themselves hate it because it's not what they enjoy. Heck, I know a few game designers that don't even play their own games because they dislike them so much.
Why am I talking about all of this? First of all, I am about 90% complete with The Coming Dark's first chapter (tentatively titled Into the Light), and even though I'm not done it clocks in at a staggering 138 pages (including handouts). It's a behemoth, a virtual phone book of a campaign that takes the players from level 1 all the way to just shy of level 5. And that's just the first part of a three part series!
Looking at what I've created, I can't help but think "nobody's ever going to play this." It's simply too unwieldy, something that has such a broad scope that many would consider it impractical to run because of how long it will actually take to complete.
You know what? That's fine by me. I created the campaign I wanted to create, damn the critics, and I feel happy that I accomplished what I did. Even if I shelve it or bury it in my hard drive for all eternity, I'm still going to spend just as many months on the next chapter because I want to. Not because I have to in order to survive, not because I expect to make a living doing this, but because I want to. It makes me happy, and if I'm lucky maybe one person out there... just one... will be happy too, and that is all I need to know.
There's another reason why I write this... Recently the folks over at Save Versus Death released the Fourthcore Armory: A Compendium of Treasures Mythic and Deadly. In terms of what it represents and how it was intended to be used, it's a brilliant collection that captures the essence of that which is known as "fourthcore" (4C for short).
But the style of play that is 4C isn't for everyone, and I see the 4C creators getting their fair share of flak from would-be haters and people who think that 4C is a bastardization of the game that is D&D. I've been in that same boat... I've had people hate every fiber of my being for creating something that wasn't what they wanted, as if I was their own personal software engineer and game designer creating something that they alone will play. Getting yelled at for your creation is something I consider a rite of passage, a sign that you're doing something right, a sign that you are one of the elite few. I mean, after all, you've created something that's worth complaining about (nowadays everyone complains about everything on the Internet, but in 2001 the art of the Internet argument was just getting started)!
I have no doubt that the creators of the Fourthcore Armory poured their heart and soul in to a product that they really enjoyed making, probably not thinking at the time what the world will think about it. I admire the time and effort they have put in to creating something that a fraction of the massive D&D community may ever actually play because it's simply not their style. They didn't do it for the people that won't ever play it; they created the armory for the few people that do.
Rest assured... There are people out there who love what you've done and the efforts you are going through to make 4C a modern day reality. I'm only aiming for one person in what I do, but you have many more that are ecstatic and overjoyed for that which you have created. You're beating me already!
Be proud, enjoy the praise, and to hell with all the critics that bash that which you take so much personal pleasure in.