Moving on to Critical Hits

Sorry for my neglect, blog followers, but I totally forgot to explain that I've stopped updating this site.

You can find my new posts in the Minor Quests column at critical-hits.com! Come see my stuff and all the contributions of that community.

Slaying Stone Kiris Dahn Map

There wasn't any budget for new art or maps for The Slaying Stone, but I definitely needed a city map. So I made it myself, using more of a pictorial map style. There were a couple reasons for this: One is that I figured it would be faster, and the other that I think it works better for an adventure to focus on the important places in an adventure rather than show every little building. In theory, the map was supposed to go up on the D&D website, but it still hasn't (and I was laid off before the adventure came out, so there's not really much I can do about it).

Here's the process I used to make the map, plus a big, printable version at the end.

Drawing the Map
I drew the map separately from the "Kiris Dahn" name and the compass rose. Starting with a pencil sketch of the most important places (skipping details like the trees and the small buildings), I then went back in with a Memory brush pen. (It's kind of like a spongy material shaped like a brush for doing flowing lines with permanent ink.) Here's a photo I took during inking:

Detail Inking
After inking, I erased the pencil lines, then went back in with a brown pen brush to add details in a lighter value. On a separate piece of paper, I made the Kiris Dahn name and compass rose. (I just used cheap printing paper since I knew I'd be heavily photoshopping this.) I then scanned the maps. The WotC scanner had some solidified gunk on it that left some big dirt smudges in the scanned images. They looked enough like they could be wear and tear on the PCs' copy of the map that I didn't try too hard to remove them.

Making a Map
To put it on a semi-parchment background, I tore the edges off a manila envelope, crumpled it up, flattened it back out, and scanned it. After manipulating it in Photoshop to make it lighter and less saturated, I put together a document with the illustrations layered on top. Here's the raw background image alongside a detail from the final document:

The Final Version
I ended up with a map that does what I wanted it to: emphasize the important places of Kiris Dahn and look like a reasonable prop for the PCs to possess. Most RPG maps, in my opinion, look too modern to hand out and keep verisimilitude. Not many D&D NPCs would have Photoshop or satellite imagery to make their maps, nor would every city's cartographer be a master draftsman. Finally, here's the final map, at its original size (click for the full-size image):

Slaying Stone Skill Challenges

In threads about The Slaying Stone on RPGnet and ENWorld, and in a tweet by @NthDegree256, I've seen repeated comments that the skill challenges don't have clear failure results. For instance, Skywalker said, "The module as written doesn't give full details as to what a failed result entails."
(Then gives some good suggestions.) I thought I'd cover some of these challenges and give suggestions. (The Keep Hidden challenge already includes failure conditions.)

So MASSIVE SPOILERS AHEAD.

Sneak into Gorizbadd
If the PCs fail to enter the town by one of these options, they still have two other possible paths. Let them revise their strategy and try another way to enter the city. This is extra, and you probably shouldn't assign XP since they failed already. Consider making the second attempt require fewer checks, just so you don't spend too long in the challenge. Alternatively, if the PCs attempted to enter the kobold slums or the forest, they could enter the city at a location they didn't intend to (possibly after being swept down the river or getting lost). This could lead to a combat encounter or a tiring slog through mud or underbrush (causing them to lose healing surges or other resources).

Claim the Stone
If negotiations with Tyristys fail, the dragon commands the PCs to leave. Now, the dragon is still there. The stone is still there. Give your players some time to come up with a crazy plan to get it. I'll just cover a few eventualities:

• The dragon tells the PCs to prove themselves. If the PCs didn't totally bomb the challenge, the dragon might ask them to do something for her in return for the stone. This works especially well if the PCs didn't do much in Gorizbadd before heading to see Tyristys. Give the PCs a quest, possibly one that incorporates one of the setpiece encounters of the adventure that they might not normally see otherwise.
  
• The PCs wait until the dragon leaves to eat, then steal the slaying stone. Even though the dragon didn't care too much about the stone, she still has a dragon's pride. Anyone who steals from her invites her wrath, and she tears the town apart looking for the adventurers. Maybe the PCs need to escape or hide during an intense skill challenge chase. Or perhaps Tyristys just bides her time and causes trouble for the PCs later in their adventures.
• The PCs bribe the dragon. What diplomacy can't solve, gold might. If the PCs try to offer gold and loot, you should let it be successful only if the amount they're giving really hurts. They should be at a disadvantage later. You might have to give them away to make up their lost loot, but make them work for it.
  
• The orcs make a better offer. Since the PCs aren't the only ones after the stone, the orcs might go to talk to the dragon after the PCs' talks break down. The orcs might get the stone despite their obvious unworthiness. Perhaps Vohx offers up one of his underlings as a sacrifice to the dragon. If the orcs get the stone, it's time to fight it out. The orcs won't use it, or all the work they've done to get the damn thing and get paid will be wasted. Though they love to fight, an orc will run away with the stone if the Severed Eyes look like they're going to lose and die.
  

Keep in mind that this challenge has two parts. If the dragon thinks the PCs are trustworthy, but inept, she might behave differently than if she thinks they'll betray her.

4E Success or Failure: Paragon Paths

About this Series: This post is part of a series about some of the new concepts in 4th Edition, particularly ones I had a hand in designing. It will judge which aspects succeeded and failed, and rate how close the mechanic came to its goals and how beneficial it is to the game experience.

This is all my opinion, and your tastes or experiences might give you a higher or lower opinion of whatever I'm talking about. There's also a wide span between the great examples of each mechanic and the weakest, so I'll often qualify my opinion when I'm talking about the potential versus the reality.

Today's topic is Paragon Paths

Last time, when talking about epic destinies, I said:

I'm covering this first partially because I want to talk about paragon paths soon, and I plan to call back to some of the things I'll say here. The two have similar goals: They aim to enhance the feel and themes of each tier and provide more character differentiation.

I'll say off the bat that I don't think paragon paths accomplish what they're supposed to do as well as epic destinies do. Mostly, this is because they're muddled and inconsistent. I'll explain why I think that is later on. But first, what went right?

Successes

• Mechanical Subsystems: The best paragon paths build on the core of a class but add a new mechanic that changes the way you play. They have a sort or subsystem or game within the game that is too involved to really put in feats (not that that stopped anybody from doing so). The prime example is the Life-Stealer (PH 141). It takes a normal warlock function (collecting souls from defeated enemies) and tweaks it (by having you check which origin the creature was), then ties that mechanic into the path's powers (by having them care about which life sparks you have). Paths let you group all these mechanics in one place instead of having a toolbox of feats, items, and powers you have to take to gain full advantage (which not only makes it easier to design, but easier to build the character).
• Theme Extension: My second favorite paths behind subsystem paths are those that extend a common power/build theme. Examples include the hospitaler (PH 101) and wild mage (PH2 151). Since the paladin has options for healing, you can pick a bunch of healing powers before grabbing hospitaler, making it a continuation of your existing theme. Wild mage gives your already random sorcerer a bigger batch of random mechanics. I like these paths because they feel organic. Later, I'll describe how many paths just don't.
  
• Expands Races and Other Marginal Mechanics: There are plenty of ways to build and bend your character's class abilities, from powers to magic items to feats. Races and other smaller mechanics have less potential to define your character, but paragon paths that grow out of them help out some. This was a later development, but racial paths, channel divinity paths, and the like let you get more mileage out of those mechanics.
  
• Boosts Your Action Points: It's nice to have a default part of the game that makes your action points better. I prefer ones that give you something extra when you spend an AP rather than give you a different benefit instead of your extra action.

Failures

Note: In my article on epic destinies, I described three "successes" for them. They were epic feel, big impact with few additions, and broad acquisition possibilities. I'm listing these again so we can contrast what paragon paths do in these areas.

• Why is this Paragon?: Let's start off with what I consider the biggest sticking point for paragon paths (and the paragon tier as a whole, for that matter): What "paragon tier" means isn't clearly defined, or at least wasn't clear in our minds when we were designing the paragon paths system. Epic tier's easy: You take on the powerful forces that control the world. It's act 3, where you finish out your story with a bang and become a legend. Act 1 was easy, too: You were just starting out, taking out the small-time punks at the bottom of the ladder. Act 2 is always tougher, and paragon paths suffer for it. There are some vague tropes that define paragon (planar travel, growing power and fame), but it's harder to say what it means to be a paragon tier hero. Some paths, like guildmaster thief, hint at your stature. Most just kind of intimate that you've gotten...better...at some...stuff. I'd draw a line between paths and destinies at an a/the point: You're a daggermaster, but you're the archmage. I think paths would be more compelling if that point were moved back a bit. At heroic tier, you're one of several clerics in the world. At paragon, you're Kord's sole herald, though there have been many before you. At epic, Kord makes you a demigod, something he's never done before. (Not a perfect example, but you get the idea.)
  
• You Got Prestige Classes in My Paragon Paths: Frequently during design, paths were described as the replacement for prestige classes. To some degree, this made sense. In 3E, a prestige class was kind of a mark of accomplishment; you had built your character up to the point where you could take the PrC. That's kind of roughly approximate to paragon tier. But in the end, I think this comparison hurt paragon paths and prevented them from feeling as unique as they should have. Prestige classes were flexible, representing some amount of training in whatever they were about. Like most things in 3E, you could go as deep or shallow as you pleased, and you could acquire the PrC at a variety of points in your character's life. Paragon paths, though, appear at 11th level and lock you in. This isn't bad in and of itself, but it does mean that straight-up converting prestige classes to 4E doesn't really make satisfying paths. Since "prestige class" meant so many things and covered so much ground, "paragon path" ended up working that way, too.
• Too Many Little Boosts: Before the final version of the 4E rules, classes had a ton of little class features at various levels. Fortunately, we learned our lesson and pared them down. Unfortunately, paragon paths didn't get the memo and ended up a little bloated. I said in the last post that epic destinies get a lot of mileage out of a few mechanics and a lot of story. Paths get a little mileage out of a bunch of mechanics and too little story.
  
• The Good with the Bad: Chances are, you'll find something to dislike in a path. Maybe the 16th-level feature bores you, or you don't really want the utility power. Taking a path might mean taking some crap you don't care about to get the stuff you want. This problem is actually worse than in 3E because the designer has to fill all those slots. Prestige classes were more free-form, so if the designer didn't think of a good mechanic, he or she could exercise the option to just not include one. Path design can force you in a corner, where you know the features are, by design, not quite significant to bother including.
  
• Abrupt Shift: I mentioned in the miscellaneous section of the epic destiny article that it can be jarring that everybody assumes a destiny at once. I've promoted that to a "failure" here because it's even more egregious at 11th level, mostly because the paragon tier doesn't seem as different from heroic as epic does from paragon. Fortunately, this is an easy fix. Since there are so many mechanical elements in a path, the DM can give one out early to indicate a PC moving toward a path.
  
• The Drastic Alteration: It's possible for paths to both have a really cool concept and be wrongheaded or frustrating. These are the ones that drastically change some of your class's trappings. Wizard of the spiral tower is the first example. Yes, it's cool to be a wizard who uses a sword to channel magic. But it's not cool to wait till 11th level to do so! Occasionally, a character even has to kinda suck for a while to set up for a path that will change the game. (Certainly not as common as in 3E, but it happens.) Really, this type of path should be altered to fit in the "extension of existing theme" category mentioned above by giving feats and powers that set the foundation for the theme, but are good on their own.
  
• Lack of Flavor: More often than with destinies, paths grow out of mechanics first and story/world concepts second (though I'd say it's still story-inspired most of the time). One of the reasons is that they're less broad, and another is that you don't really have that much room to write story background for them! They can be really light on story hooks, and even the ones with cool backstories might be passed over in favor of the mechanically best paths. And, honestly, a lot of players just don't care. Some don't pick a path—or even think about it—until leveling to 11th. A path needs to give some solid roleplaying hooks if it's going to have an impact on the game beyond "I have another power." (And I'd argue that it should.)
  

Miscellaneous

• Simply the Best: Paragon paths are narrow enough that, when it comes time to select them, you can easily pare down your options to the cream of the crop. With a set bunch of abilities arrayed by level, it's not hard to compare one path to another and just take the mechanically best one. This is harder with classes, which have varying roles and a lot of options, and epic destinies, which rely on a few big mechanics that often go beyond the normal rules and are therefore harder to compare based on pure numerical advantages. Since a paragon path is a pretty big choice, I think fewer people take chances on a "weak" path than they do on a "weak" power or feat. You have about 14 slots for class powers, 18 slots for feats, and 1 paragon path slot that equates to three powers and some features. This worse/better/weirder the more choice you have. You're looking at all the class, race, and power source paths (along with the ones for anything you've multiclassed into), so you get even more pressure to find the perfect one.
  
• Proliferation: In the compendium, there are 80 epic destinies. How many paragon paths do you think there are, between books and D&D Insider? The answer is 418—about 5 times as many. If I'm doing my math correctly, paragon path powers account for 1/5 of all powers in the game. I try to avoid designing new paths for the simple reason that there are already a ton nobody will ever take.
• Power Restrictions Limit Design: As with destinies, I'm going to put "hard to design" stuff in miscellaneous. Being difficult to design for a professional shouldn't take points off (though if DMs were intended to make them, it would). This topic mostly ties into the broadness of paths. Theoretically, you could make a path that fits a wizard, rogue, and druid. But you have these attack powers, and you have to consider what weapons, implements, and ability scores all those classes use. Now, I'll grant that this isn't an impossible hoop to jump through, and the problem might lie more in the base setup of scores and items, but it does make them harder to design and harder for the player to process if they have all the extra language they need to work.
  

The Score
So I'd say paragon paths don't live up to their name or really achieve their intended goal, though as I wrote this I found more to like about them than I'd initially expected. Let's give them a grade of:
C-

Minis Gallery 2

I've just dropped a bunch more minis photos to a Picasa Web Album. Most are older (though some are pretty good), but also has the most recent mini I completed. Enjoy!

Behind the Design: DDXP Notes

This is the first page from the oldest WotC notebook I've found (though I think I have an older legal pad somewhere). Click the image to enlarge it. It runs down some suggestions from a fan seminar at D&D Experience (when it was in DC). Since this came before the 4E announcement, you'll see suggestions for 3.5 products and Dungeon Tiles. The group was primarily made up of RPGA players, leading to requests for RPGA content on the podcast.

It's interesting to see what suggestions became reality, like ship Dungeon Tiles (as an RPGA DM Reward), non-collectable minis, and RPGA details on the podcast. Having each D&D Insider subscriber become an RPGA member automatically didn't happen, sadly. One cool part was the idea that there should be more "insider info" at DDXP. Of course, the next year at the con was when people got the very first chance to play 4th Edition!

You'll see at the bottom that rumors were already out there about 4E (though they were just as likely based on conjecture as on leaks). Unsurprisingly, the invested RPGA/Living Greyhawk players weren't too excited about the idea. Then again, few people were before details started coming out. I remember the chill that went through the room during the 4E announcement at GenCon.

Behind the Design: Torog Planning for Underdark

Listening to a podcast (The Tome Show, I think), I heard them talking about the grotesque image of Torog in Underdark. I meant to find the sketch I did to get his look straight in my head, but can't find it! I did some of the work on Torog and his treasure palaces (uncredited, sadly), and I did find the brainstorming/planning notes I'd put down. See the larger image here.

Much of it's based on the plans Rob Heinsoo had made, and I was looking for ways to flesh out and refine those ideas and roughs. You'll see my brief notes for the torture palace sidebars (which became "torture dens," I think).

I went pretty nasty and gruesome with the images and descriptions of Torog. What good is the god of torture if he isn't scary? I think the editors justifiably toned it down for the final book.

If I do find the sketch, I'll put it up!