I can't help it... I have more and more ideas popping in to my head, and part of me really wants to write them up in a module but there's another part of me that questions what edition to do it for. After all, some would argue that 4E is on its last breath, but 5E is still too far away to create anything concrete for it.
So, at least until I get around to writing some of these, here are the projects I have in the works:
DM2: The Fields of Bone and DM3: The Den of the Dark Mistress
These two modules are a continuation to my level 0 adventure DM1: Death's Edge, which was released as part of the May of the Dead blog carnival.
Part of the reason I haven't continued work on this, besides there not being enough hours in a day (man, if every day had 57 hours in it I'd be unbelievably productive!), is that the latter half of The Fields of Bone is virtually identical to the Reavers of the Harkenworld adventure that comes with the DM's Kit. I mean, the similarity was amazingly uncanny considering I hadn't even looked at Reavers until recently.
I've been considering doing a Kickstarter for this, but I've already expressed my concerns regarding that.
Unnamed Lair Assault style adventure
I got this idea from Twitter in a roundabout sort of way, and it was one of the ideas I had submitted to DDI last cycle only to be told "no".
Premise: The players are all kobolds. While they are away a group of level 1 adventures attacks their lair and kills everything inside, and the kobolds return before the party has left. They must reclaim their lair and get their revenge on the adventuring party that dared attack them!
Part of the design involves giving the kobolds the ability to "buy" traps, creatures, obstacles, etc... that they can place throughout their lair in order to thwart the intruding adventuring party. So basically the DM decides the path the adventures are going to take, the players then buy the traps using resource points (similar to Attack of the Tyrantclaw, I think), and the DM resolves whether those traps caused any damage to the adventuring party. Then the kobolds go in and try to kill the adventurers, which consist of the stereotypical five PCs (fighter, cleric, wizard, rogue, ranger), one animal companion, one familiar and at least two henchmen.
I thought it would be an interesting idea to have the participating players pretend that they themselves are Tucker's Kobolds, and it'll be an experiment to see whether the role reversal - players as monsters and the DM controlling PCs - will work without being too big a headache for the DM.
Module's about 70% written and still needs a map of the lair. I'm walking a thin line because kobold PCs are not exactly GSL compliant, but I think it will be OK.
Unnamed Epic Tier adventure
Nobody knows where they came from; ten foot tall shards of reddish-blue crystal were appearing across the land, and these crystals defied all magical explanation, were impervious to all damage and could not be moved by even the most powerful forces. They remained motionless, seemingly inert, hovering a few inches above the ground, without any rhyme or reason...
...until the seventh day. Without any warning, the crystal and everything surrounding it vanished in the blink of an eye, leaving behind a massive crater over two miles wide and almost half a mile deep. All that remained was gaping hole in the earth; no destruction, no debris... Just emptiness.
In the past the crystals appeared in seemingly random locations - in the middle of a barren field, hovering above the ocean surface miles offshore, atop distant mountains and deep within swamps - so the locals had no reason to be concerned. But now one of these crystals has appeared in the town square of the most populated city on the continent, causing widespread panic and jeopardizing the residents, their homes and their way of life. Something must be done before time runs out and the city is consumed, leaving nothing more than a lifeless crater where it once stood.
I have never done an epic tier adventure. Actually, the only epic tier stuff I've done has been bits and pieces of my Items of Legend supplement. The reason: I am very bad with D&D lore. Epic tier usually involves interaction with gods and primordials, other planes of existence and a lot of things that require detailed knowledge of the world that is D&D. I'm just not comfortable with that as a designer and as a DM.
This adventure is meant to be for the early epic tier - around level 21-23, I'm guessing - which means I can get away with not dealing with a lot of the lore that comes with epic adventures. Yes, a majority of the adventure will take place in the Elemental Chaos, but it won't be bound to much lore there beyond the plane of existence itself.
I'm still debating whether to make this a straight up adventure or something that leans towards the Fourthcore style of play (which is something I've been wanting to do for some time). And, since I have the story in my head but haven't done any actual design work for it, it seems like a good candidate for "DnD Next". Still don't know... Need to think about it...
Untitled RPG or Campaign Setting
For quite some time I've had an idea to create a somewhat post-apocalyptic RPG, or at least an extensive campaign setting. This idea of mine has been somewhat motivated by the fact that I can't legally create Gamma World (*writes check!*) content, so rather than complain about not being able to use the system I thought I'd create my own system and do with it as I please. I haven't decided what engine to use - I've considered d20, AGE, FATE and others - or whether I'll roll my own system, so my plans are still quite up in the air.
The setting is not quite Gamma World (*writes check!*), but it's close. It's a post-apocalyptic world, and although there is a certain extra-terrestrial influence it is "down to Earth", if you will. I have ideas for space travel and other adventures along those lines, which might take it beyond the d20 style of play to something more tactical or more resource-driven (my life has been heavily influenced by Star Control, Starflight, Master of Orion and similar game mechanics), but I don't know if I want to take the core that far "out there".
Writing your own RPG or campaign setting is, needless to say, a helluva lot of work. I'm not sure if I have the time or resources to take on such a thing, and I'm fearful that anything I create might be lost in the sea of RPGs currently out there. And, like I've said before, I'm horrible when it comes to writing "fluff"... and that's kind of important in a project such as this.
So maybe, some day, I might actually make some progress on this. Don't be surprised if I throw up a real Kickstarter to develop this some day.
So stay tuned for my next creation... whenever that may be.
WARNING: THis post might ramble on a lot for little purpose. Read at your own risk.
For the most part, I've been reserving a lot of opinions I may have about "DnD Next" and trying not to actively engage those people who choose to complain about it at the top of their lungs. Doing the latter is harder than I thought, and sometimes I can't help but respond, but lord knows I try. So even though this post refers to one or two specific elements about DnD Next, this is not necessary a criticism of those elements but a concern about the fact that, good or bad, they exist in the first place.
The Development Process
Before I continue, let me try to describe what a product's development cycle is like.
Whenever a version of a product comes to the end of its development, there is inevitably a big meeting of all the employees in which the owners ask "OK, so what features should we have in the next version?" Usually, these meeting are a no holds barred brain dump of information where any and all employees mention even the slightest inkling of an idea they may have for a future feature. It could be something monumental that could take months to develop, or it could be something that even the lowest level programmer could do in minutes, or it could be "are you f%#&ing stupid?!?" quality material... it didn't matter. All these ideas, however nonsensical and unrealistic they may be, are gathered in one enormous list for the higher authorities of the company to mull over. And this list exists for a considerable amount of time without any concept of feature importance or development time needed to create what's on it.
For the next several weeks, especially after a major development push, programmers are allowed to muck around and experiment. A lot of designers will actively create something using the engine as a proof of concept, or they may just BS around and consider it a sort of mini-vacation, at least until the higher authorities decide who does what. While working on Deneba's Canvas graphics package, I spent four weeks writing something that ended up being patented by Adobe and could not legally be included in the product... but it was really cool and fun to do, though!
At some point, the higher authorities meet and begin to set levels of importance on everything in that list. This is when the sales people come in and look at the list alongside the development leads to decide what features they must have in order to make the product more sellable and justify a new version that people will buy; if there aren't enough "wow" features, there's no real reason to spend a ton of development resources for a product people will have no reason to purchase, so they may hold off the new version until they do have sufficient new features to justify it.
But once the list is sorted by importance (with the "are you f%#&ing stupid?!?" items removed, of course) and the group starts to get an idea of how long things will take, they must collectively draw a line in the sand. Anything above the line is a "must have" which is required to be in the product for it to be a viable new version, and anything below the line is a "would be nice once the 'must haves' are done". And then the "must have" list is disseminated to the developers, while the "would be nice" might never get to the developers at all. After all, they wouldn't want the developers to waste time doing stuff that isn't necessary to make the next version bankable.
I need to point out that I've actively worked in development shops where if you're supposed to be doing something on the "must have" list and decide to do a "would be nice" thing, if your superiors found out you might as well start packing your stuff while your fellow developers lay claim to your office space. Why? Because, in the eyes of the higher authorities, the "would be nice" list has no value right now. It does not add to the value of the product and it's ability to be sold, regardless of whether you agree with that choice or not. A feature you might consider cool, fun or whatever might be worthless to a the people that pay your salary.
Depending on the length of your development cycle, you may never finish the "must have" list. Ever. Heck, you might not even get close to finishing it by the time your product goes "gold"; there will come a time where the higher authorities will see the time estimates to complete development becoming longer than the time left before the day the sales people decided the product will launch, and they will start to cut things or push things to the next release. Don't be surprised if something you've been working on for months gets cut in such a way that you may be forced to surgically remove from the current build any trace of what you were doing to begin with (god help you if you were working on a vital system; be ready to work 37 hours a day to get it done before going gold).
And, of course, this is assuming that you will only go gold once... I've worked on a project that went "gold" five times in three days.
The Shotgun Approach
In the above series of events you will note that the "higher authorities" - be they owners, salespeople, marketing folks, customer service, etc. - are the ones that consolidate the ideas and decide what has priority in the development cycle. In software the salespeople carry the most authority in this decision; in order to sell the next version, it has to be better and have sufficient "wow" features to justify current customers forking over money to buy a product they kind of already have.
But in the world outside of software, such as in the world of roleplaying games, it's hard to quantify what "better" is. If you read this blog, odds are you've seen the discussions that can come up: if you ask ten people what makes an RPG "better", you'll get ten different responses. So who decides what is in the next version? Who decides what makes the next product bankable?
In this case, it boils down to the fans. Since the salespeople are inevitably involved, they have to look at the audience and see what elements would provide a higher financial return. This could mean creating an element the majority wants, or perhaps creating an element that is so different from the prior version that its mere existence deprecates everything that came before and forces people to buy a new version (or a mandatory "upgrade"... like Internet Explorer). Sometimes these features might be the personal wants and wishes of the developers themselves, but in those cases they have a very difficult battle to fight; they have to sell their ideas to the higher authorities, and may be forced to accept the higher authorities telling them "you can't do that." I have a sense we've seen this sort of thing at WotC recently, but I digress...
But sometimes you just don't know what's bankable. You have ten possible ways of doing things and don't know which will be the preferred way, the way the majority of people will accept enough to add financial value to the product. So you have no choice to use what I refer to as the "shotgun approach": give it both barrels and try it all.
Rarely you see the "shotgun approach" in video games, but in the early days of mod development it happened a lot. Indie mod developers would look at the list of all the most popular games out there and say "let's do ALL of that!", and you wound up with sixty different versions of CounterStrike. Oh, and people like Team Fortress too, right? Let's railroad in some TF elements in to our CounterStrike clone... now we have BOTH! That'll be awesome, right?
Like I've mentioned before on this blog, while creating the Half-Life add-on The Opera I received numerous requests to add a ROCKET LAUNCHER to the game. Did it fit my theme? No. Did it make any sense to have? No. Did a small handful of players demand it or else they wouldn't play my game? Yup, you betcha!
In cases where somebody is incapable of making the decision of what gets worked on and what doesn't, the simple choice is to develop it all, however mindless and nonsensical it may be, and see what sticks with the audience. If people don't use it, there's no harm to its existence. People aren't going to hate the game because of this one optional feature that we could ignore, right? ... Right?
There's some problems to the shotgun approach:
- Your "to do" list is significantly longer, and now you can't ignore the features you thought "would be nice". You now have to allocate development resources for any small thing on the list, however inconsequential it may be, and hope you don't run out of time before your "gold" date.
- As developers, you will not like doing certain things on the list. It's your game after all, and it doesn't matter how many times you think "this is f%#&ing stupid" ... You gotta do it anyway. Nothing's worse than a developer that doesn't like what he's developing.
- Since the feature list is customer driven, you end up working on things that a minority of people mentioned because you're just not sure if everyone else wants it or not. You have a handful of people saying "yes", but nobody has actively said "no" yet. When the product gets published in any way, the "no" people will be screaming with bullhorns from the rafters.
- Every small thing, however nonsensical, must now fit in to the big picture. You can't add an item that actively conflicts with the core, so every seemingly trivial item must be analyzed to ensure it doesn't break the rest of the game.
- Every small thing adds another test case. It it exists, someone has to try it. After all, god help you if you publish something untested.
- Every small thing requires additional resources true developers don't think much about: layout resources, artwork, editing, copying of that information to other sources of information, etc. Heck, it requires more ink, and that may impact the product's retail price.
- You could be working on things that simply don't belong in the game solely because some people think it does.
Focus on What's Important
So why am I talking about all of the above?
In the recent Rule of Three column on the Wizards of the Coast site, a single line raised my concern and that of a lot of other people:
Mike has drafted some very tight, clean rules for facing that should add a lot of tactical depth to combat, and make movement and positioning even more important than ever.
The reason the above concerns me personally is the thought of what didn't get worked on while Mike was writing a paragraph or two on "clean rules for facing"...? Personally, I'm not against the facing rules themselves; I've never used them in any prior edition, don't know what they are, don't know what impact they will have in the game... I haven't a clue. Yes, if the rule existed I would try to be a diligent play tester and give them a go to see if they add or detract from the game.
I tried to ask how many people actively requested such a feature, and the basic response was that "some" did (Note: the tweets of the person that answered my question have since been deleted). So I inevitably have to imagine the massive amount of requests WotC is facing in terms of features DnD Next should have, and really have to wonder why such a feature - which I can only assume is way down the list of "would be nice" - is getting such visibility. In a playtest that's currently missing what could be seen as an overwhelming amount of content, why is this even being discussed when other more critical elements of the game should come first?
But at a glance you have to question whether they belong as part of the game or not. For a majority of editions D&D has arguably not been a tactical game, and even 4E was tactical to a point. When you start adding things like this, you run the risk of turning the game in to something that it might not be. Knowing which direction your facing has little impact on the roleplaying and combat aspects of the game, and it's a borderline insignificant detail that could be handled via "theater of the mind" anyway. If you take the tactical aspects of the game farther than the roleplaying aspects of it, it stops being ther game you know and risks turning in to CounterStrike: D&D.
Another example: I can't help but wonder how many people told WotC that DnD Next was useless without having half a page dedicated to how long it takes to put on and take off armor. I mean, it took someone a certain amount of time to think about that, right? Was it really that crucial to the game? Will the game be unplayable without it? And how many people asked for it? Hundreds? A dozen? One? Was the WotC blacksmith the only guy that thought it'd be a cool idea?
When there are so many other things that need work and are vital components to the game, why is nonsensical stuff being considered at this point? Focus on what makes the game bankable, sellable, playable, fun...Spend your resources to get the important stuff done, and eventually throw in some of the lesser bells and whistles. Nobody's going to buy or avoid DnD Next because it takes 10 minutes to put on plate mail.
I wondered how much text is involved in describing combat facing, so I decided to check the D20 SRD.
Here is the page on "Combat Facing", which is a heckuva lot more than a couple of paragraphs.
I have a lot of thoughts and ideas that are constantly rolling around in my head, and if the average day contained more than 24 hours I would most probably put them down on paper and publish them for the world to enjoy. But there's always one thing about my publications that makes me somewhat self-conscious and question the quality of my own work: they aren't "artsy".
Like I've mentioned on this blog before, I am not an artist. Sure I can make tactical maps, but that's not what I'm talking about when it comes to being an artist; I'm talking about actual hand-drawn images to give my product a little more of an artistic flair. Every time I finish a product and am about to publish it, I spend weeks trying to figure out what I'm going to do about cover art because I don't consider it a true product without one. My last product, Death's Edge, was published without cover art (the image you see on the listing is a very low resolution stock image; I do not have license to an image of sufficient resolution to publish), and that actually bothers me a great deal. It just feels... wrong... ya know?
I got lucky with The Heart of Fire: I was able to find the perfect image on DeviantArt and I contacted the artist to see about licensing it. The artist allowed me to license it, gave me a very reasonable price for it, and most importantly I was able to afford it at the time. Nowadays the return on investment for 4th Edition products is nowhere near what it once was - I haven't made a profit on any product in ages - so it's hard to justify spending money to commission art or to pay for existing art when you know you're not going to make the money back in sales.
So I've considered Kickstarter as a means to fund the creative aspects of the project and pay for commissioned artists to create the covers and interstitial art in my publications. I have actually written up at least three separate projects in order to fund some ideas of mine... but I've never had the courage to hit the "post" button for a variety of reasons.
My biggest problem is that I don't really consider this a self-sustaining business. That's always been my problem: I do this for fun, so I'm not actively looking at this as a means to put food on the table. As a result, any aggressive efforts to try to make a strong revenue stream from these products feels kind of inappropriate, and it feels kind of awkward to ask complete strangers to spend their hard earned money to have me do what I consider a hobby, a pastime. Sure, you can pay me all you want to buy an existing product, but are people seriously going to pay me to create something that doesn't exist yet and I was going to do anyway simply because I want to?
Secondly, because of the mathematician that I am I've done the numbers a lot, and in the back of my mind I question whether it'll be worth it. If everyone provides just enough funding to get a digital version it's all great because that's considered 100% profit, but once you start getting in to the higher reward levels the profit dwindles. Let's assume that everyone (or at least a majority of backers) decides to get the hard-copy version of the product; if I have to spend $20 to get a $25 backer his reward, I could risk not getting enough margin to pay for the commissioned art in the first place. The two solutions to this - either put the project goal higher or make the cost of the hard-copy rewards higher - put the project at risk of not getting funded.
Finally, and this might sound silly... there's the issue of the video. You see, I am not a salesman, and I am very self-conscious about things like that, so much so that my online persona has no trace of what I look like or even what I sound like. Heck, if it weren't for me putting my Twitter handle on my GenCon badge nobody would have known who the hell I was. So sitting in front of a camera and trying to sell my product to you feels rather awkward, especially when I'm doing what I'm doing for fun and not for profit. I would much rather stay behind the scenes, maintain the notion that I am the "digital rabbit", and have people buy my product because they want it and not because I told them to buy it.
So now I've got this planned product, the next two parts to the campaign path following Death's Edge, that I question whether to do it on Kickstarter or not. I have the project typed up and pretty much ready to hit "post", but it feels both risky and inappropriate for all the above reasons. There are other reasons for my hesitation, such as my plans for The Fields of Bone being almost identical to the Reavers of the Harkenworld module (which is part of the 4E DM's Kit), but that's a small issue compared to all the other issues with Kickstarter mentioned above.
Maybe one of these days I'll come up with something that I feel worthy to be funded in such a way, and maybe that'll be enough for me to come out from behind my rabbit face and try to sell people on it. Time will tell, I guess.
For a while I've been using Sly Flourish's online 4E Dice Calculator for all my campaigns; it's quick and easy and I find it better to use than looking up the entries on a PDF and doing the math to adjust the die sizes. But recently - primarily due to that fact that I'm over my monthly broadband bandwidth limit by a crapload - I've felt the need to have the same functionality as the above web page but in an offline capacity.
So, for now, I've created the standalone application below. It's currently written using the .NET 2.0 Framework and is for use only on Windows machines, but I'm currently investigating making something Java-based so it can be used cross-platform. That's taking me a bit since, quite honestly, I've never written a Java application with a user interface (all the Java apps I've done have either been console applications, plug-ins, extensions and the like)... But I'm getting there.
I'm also considering making an Android applet as well, but that's uncharted territory for me.
I expanded my tool a little bit to include a d20 as an available die size. I know that might sound somewhat weird, but my expectation was to make the tool also support the "adjusted" damage equations provided by C. Steven Ross over at DMG42. The only reason I haven't fully implemented those yet is because I haven't been able to consistantly match his equations, but I may get around to that yet. In the meantime, you are allowed to use d20s to roll damage, and the system will warn you in cases where it's impractical (for example, using a d20 at level 1 is higher than the average damage, so it's not really permitted).
And if you click on the equation, it actually rolls it for you. It's pseudo-random and it doesn't use the means of generating random numbers that other die rolling systems use, but it's better than nothing.
I'd like to thank Sly Flourish for providing the online tool on which this is based. if I ever get around to creating an offline cross-platform version, I'll make it available in the same manner.
If you have any issues or suggestions on how to improve this tool, please let me know.
As the result of a write-up of the ranger "design goals" on the Wizards of the Coast website, there has been a lot of discussion of what a ranger is and what it should be. I figured I'd chime in with an opinion because rangers are the second most common class I play (the first being rogues), and I've played a ranger on more than one occasion in every edition they've existed in in D&D. I felt it necessary to come to their defense.
Before I continue, let's have a little history on the ranger as a class... The ranger existed as a core class as far back as AD&D 1st Edition (it was technically absent the in Basic edition; support for playing a ranger in the Basic edition was provided in Dragon Magazine), and since then it has been a constant presence in the D&D class list despite going through some seriously radical changes in each edition: he went from having favored enemies to quarry damage, his spellcasting power source wavered between primal (druid), arcane and divine, and at one point rangers were even limited to the races and alignments they could be (in 1E, they were forced to be of good alignment).
But with the coming of "DnD Next" many are asking whether the ranger should be its own class at all. Logically, it's very possible that the ranger could be a subset of the fighter or rogue and made more ranger-like through the use of themes. After all, a ranger is arguably not much different than a fighter but with an affinity to natural environments.
Several arguments have been made regarding this, and quite a few of them actually make a very good case and could work quite well as a theme... but a problem exists: the ranger class has a history. It doesn't really matter if a ranger-like PC can be better designed with themes, background, feats or a lot of flavor text; the ranger has to exist as a class because it's been that way for over thirty years. If a player sits down at a game and says "I want to play a ranger," he can't be told "there isn't one" or "here's to play a character that is kind of like a ranger... only not."
In my opinion, there are certain aspects that have become required elements of D&D. Some more than others, of course; players will always have the six attributes, they will always have some sort of AC defense (how it is calculated is another matter), and will always roll d20s to resolve things. Just as there will always be mages and clerics, the ranger has become somewhat of an integral part in all that is D&D, and as such it should always be defined as a class even if it makes more sense for it to be something else.
Finally, many have mentioned that they would like "DnD Next" to contain only the four base classes - fighter, thief, mage and cleric - and create all other types of classes using themes, backgrounds, etc. The problem with this is that it really overcomplicates the class design; all of a sudden, you have a "fighter" that can be defined twenty different ways, and each one of those ways has to be explicitly worded so as not to cause confusion with each other. By separating like minded themes in to a new class, it makes the creation of both classes significantly easier. I won't have to wade through five different ranger-like themes when I want to create a straight up fighter.
So, please, let's keep rangers as their own class. Besides, it'll probably be the only way I'll once again get my velociraptor animal companion!