Monday, September 17, 2012

freelancer aspirations: superior implements

This particular entry has a long and winding history, and represents my first attempt at trying to get a gaming-related article published. Back in the fall of 2010, I contacted James Auwaerter about possibly collaborating on a pitch and article to Wizards of the Coast for D&D Insider. That spring, the Player's Handbook 3 had included the first rules for superior implements, and although it was suggested that the keywords used could be used to homebrew varieties not present, there weren't many examples shown. I had several mechanical examples that I thought were good possibilities, but wasn't as comfortable with the story side of what made for a good D&D article.

Jim was reasonably receptive to the idea of working together, and contributed several ideas. The Common/Uncommon/Rare system was just being applied to magic items at the time I originally contacted him, and he suggested that we might also want to come up with several Common magic item enchantments that could be applied to the implements we developed. He also did a lot of work on the story development in the article (below). In fact, it's probably fair to say that Jim did all of the flavor text in the article along with helping polish the mechanics.

Along with a lot of notes about proposed mechanics, the original pitch I sent Jim for some review read as follows:


This crunch-heavy article would expand on the superior implements currently available by both defining two new superior implement keywords and presenting roughly a dozen new superior implements of all types that both take advantage of the new keywords defined and present new combinations of implements and keywords. Our best estimate of the word count is approximately 1500 words.


Jim rewrote the pitch, based on the following general principles:
  1. Don't come in too high. It's easier to come in low and have them ask for more, or (in an article like this) write more than you originally pitched and ask them to pick the best of the selection.
  2. At the time, the magic item rarity rules had just been introduced, and there was a massive gap in what items were considered to be Common. Adding the magic items was a way to help make the article appeal to more possible players.
  3. At the time, the Grifnar's Arms article was only a couple months old, and was one of the best-received short articles in a long time. So, it was an attempt to link the article we were proposing to something else that was recently well-liked. In addition, the word count was boosted to match the length of Grifnar's Arms article, which had lacked any new rules content.
Bazaar of the Bizarre: Tools of the Spellcaster’s Trade
This article would present new superior implements for the discerning spellcaster. It would be in a style similar to the Bazaar of the Bizarre article "Grifnar's Arms" from Dragon 391, introducing Grifnar's elven counterpart, Aldanian. Aldanian would offer several kinds of superior implements as well as some more common magic items.
We intend to define two new superior implement keywords (enduring, to help spellcasters that summon creatures, and expansive, to help spellcasters who favor area effect spells) and present roughly a half-dozen new superior implements for all implement-using classes. We would also provide two or three common magic item enchantments that could be used with multiple types of implements. We estimate this article will be approximately 2000 words. This article is being jointly submitted by Jim Auwaerter and Jeff Dougan.
At the time, Wizards of the Coast didn't guarantee a response to every pitch submitted, and we went our requisite 60 days without hearing anything. We did both think the general idea still had legs, and ended up sending a query (pitch) to Wolfgang Bauer of Kobold Press for possible use in Kobold Quarterly magazine. He liked the general idea enough to let us write up a full manuscript (PDF version here), and sent us some notes about the Midgard campaign setting (used by KQ for a number of their articles). Wolfgang also ended up passing on buying the full article, which we figured out from seeing the tables of contents for the two issues of KQ we might have been considered for & learning that manuscripts didn't remain in the submissions pile from one issue to the next.

Some time in here, the second period in which Wizards of the Coast guaranteed responses to everybody opened up. I got a hold of Jim again and asked him if he felt like it was worth giving it one more go, since this time we'd get some guaranteed feedback. I sent it in along with a few other pitches (it ended up in my second batch of pitches in that window), and waited. For reasons unknown to me, feedback on this particular pitch was missed in the initial pass. However, I ended up following up on its status at the same time as the project that they eventually did pick up, and learned the following reasons for its rejection:
  • At the time we sent this, they had a number of Bazaar of the Bizarre articles (the series under which this would have appeared) in various stages of work, so they didn't want to add more to that series.
  • The mechanics we'd proposed were functional, but the design team didn't want to add more keywords or other new mechanics unless they addressed something vitally needed. There were also some concerns about our new introductions adding an element of "power creep" into the game.
Although I understand the concerns about the number of Bazaar of the Bizarre articles & the potential for power creep, this is one article that I have to admit I'm still disappointed didn't get commissioned for further review.

Thursday, September 13, 2012

Freelancer aspirations: the Cryomancer

Preface: Those who don't have any interest in gaming generally, and role-playing games in particular, will probably want to ignore this post since it talks about my recent experiences in a freelance project submitted to Wizards of the Coast for the Dungeons & Dragons game. I'll do my best to keep jargon out of the article as much as possible if you decide to keep reading, but you've been warned.

This project has only just reached a point where I can openly discuss it, thanks to some bad news received about it yesterday afternoon. Some background:

Wizards of the Coast currently runs two open submission periods every year for those who aspire to write freelance projects for Dungeons & Dragons Insider, the online version of what used to be Dragon and Dungeon magazines. Over the last year (two cycles), I've submitted roughly 20 pitches (two with co-authors attached) and had three projects commissioned to the state of a first draft. I got more-or-less final verdicts on two of those three projects yesterday, one of which will result in a paycheck and one of which was a rejection without request for further revision. I'm not at liberty to discuss the former project until it comes out, but I figure I'll put some lessons here on the other project.

For those who aren't gamers or otherwise into fantasy genre fiction, a cryomancer is a kind of magician whose abilities are all focused on cold. Here's the original pitch:



Class Acts: Wizard: The Cryomancer

Fire mages are flamboyant and hard to avoid noticing; wizards who specialize in cold magic are rarer. Calculating, implacable, and unforgiving, those who command the glacial ices are rare and worthy of attention. Their comparative rarity is attested by the lack of a singular figure associated with cold magic, although many famous archmages have included magical cold within their eponymous spells (including both Bigby’s Freezing Grasp and Otiluke’s Freezing Sphere).

 The pitch I sent included a little bit more, like some details on estimated word count and particular mechanical elements. In the initial response, I was given two directives to consider: first, that elemental specialists needed to have some way to deal with creatures that were resistant or immune to their element of choice. For example here, a cryomancer needs a way to cope with meeting a frost giant or a white dragon. the other directive I got was to focus more on the story side of the article than the mechanics. This PDF represents the draft I submitted, minus some internal notes to the produced & development teams on certain elements of story, credits, and the art order.

One challenge for me was that the lore of D&D doesn't really have any famous wizards who are known primarily for their use of cold magic. There are a number of D&D wizards who have used cold in some of their famous spells (Bigby's Icy Grasp made it into the 4th Edition Player's Handbook; Otiluke's Freezing Sphere was present in all of the first 3 editions of the game), but I didn't have a single wizard around whom I could build the story. I ended up dividing it up among three wizards, two of whom have lore that goes way back in the game and one of whom was my first 4th Edition character.

The discussion of "naturalist" vs. "elementalist" varieties of cryomancy came about rather late in the writing process as I wrestled with balancing not creating large quantities of new story elements out of  whole cloth
with the directive to focus more on the story elements of the article. I was also trying very hard not to make the whole thing "pyromancers are like X, cryomancers are like Y," although a little bit of that still slips through.

I heard back yesterday with the article's rejection, and I'm actually not surprised. The mechanics were OK, but not inspiring, and I did got a bit too far with the story elements. It's been said by Wizards of the Coast staff in previous public places that, if a draft has promise but just isn't quite there, they'll work with you to make the work the best it can be. (From the project that will result in a paycheck, I can say that's true. I can't elaborate more right now, but will probably try to write something like this about that project when it becomes public.) Overall, this article just didn't have anything they could point to as being fixable.

I'm still very new at the RPG-freelancer thing, but I agree that the article definitely didn't deserve to get bought as-is. I think I was hoping that there would be a little more guidance on ways to help the story become more cohesive, perhaps because I think the idea of a winter wizard still has lots of potential. I just wasn't the person to get it there -- at least, not with my current degree of skill. Maybe I'll come back and revisit this idea someday, after I've got some more design experience. If I do, I'll be sure to let people know.



Wednesday, September 5, 2012

Preparing for September 25th - #TrueLove

Trigger warning: link to a post describing what should be considered sexual assault

On September 25th, 1987, one of the most important movies of my generation premiered. It's had tremendous influence on geek culture, although not as blatantly as (for example) Star Wars. That movie is a wonderful ode to action, adventure, and True Love. It is, in a title, The Princess Bride.

Returning to the internet after a holiday-weekend absence, I was appalled to read about something that happened during a party connected to PAX Prime (which is rapidly becoming one of the biggest geek-culture conventions). [Edit: In looking up the link for the post describing the event in question, the victim makes it clear that party had no kind of official connection to either the convention] A woman was, in effect, sexually assaulted by another attendee at the party, and the security guard her friends tried to get involved gave a reaction along the lines of, "What do you expect me to do?"

There's a connection between these two things, I promise. It's this: as somebody who's been happily married for 14 years, I know that not all geeks are socially maladjusted. I know that we have the ability to be in stable, reasonably healthy relationships, and that many of us appreciate just exactly what True Love can be.

So, I propose to the geek community that on September 25th, we all tweet, post, and otherwise put onto all of our social media sites of choice our appreciations of True Love, in an effort to make it the top trend of the day across the Internet. Who's with me?