Enter your email address:

Delivered by FeedBurner

feedburner count

Wizards Ruin Encounters in D&D!

Labels: , , , , , , , ,

If you've read many forums or blogs where D&D is discussed over that past 8-10 years, you have probably heard many players complaining about wizards ruining encounters with spells like sleep or fire ball that take out large numbers of the opposition. While I expect to hear GMs (especially GMs who run more linear and/or more pre-plotted adventures) complaining about players who manage to quickly defeat or defuse a situation they have set up and planned out in detail using some power or ability (or just a good idea) they had not "planned for", the idea that players would object to winning an encounter quickly generally seems alien to me.

I've been playing and running D&D and D&D-like games since 1975 and I can't remember any complaints from players about how wizards ruin encounters by taking out the opposition with a sleep spell or a fireball or other magic. Occasionally players would get upset with a wizard who did this if they slagged the treasure in the process, if they killed someone on the opposing side that needed to be kept alive for some reason, or for some similar campaign/adventure related reason. However, I can't remember a single pre-3.x game session where any player complained that a wizard ending a combat before it really could get started was somehow ruining the encounter simply by quickly taking out the opposition. I've only seen this in WOTC editions of the game -- although I suspect I might have heard it if I had ever played 2e with all the Player's Option books.

Why is were such complaints very rare in TSR editions, but seem much more common in WOTC editions? To be honest, I'm not sure -- but I have a hypothesis. These complains are more common in WOTC editions because the place of combat in the game changed greatly with the WOTC editions. (Note: the change really came with the Player's Option books, but the change there was entirely optional and the Player's Option stuff really wasn't that widely used.)

Combat in TSR editions (pre-Player's Option books) was designed to be relatively abstract and very fast to play out. A single combat encounter seldom took long to play and was seldom seen by players as the main activity in the game -- even among players who played just to fight things. Players who enjoyed combat got their enjoyment from having lots of combat encounters in a session -- not from any single encounter. Wizards were unlikely to be able to pack enough combat-ending spells to end many combats during a game session so it was generally a non-issue even for players who were "combat monsters".

Combat in WOTC editions is very tactical (and really needs minis and battlemats from 3.5 on) and each combat consumes a lot of a session's play time. Detailed combat encounters therefore became the main focus of (and source of "fun" in) the game for many players: they enjoyed the tactical feel of combat and looked forward to spending 30 to 90 minutes of real time in each combat encounter.

Given the above, I can understand why players of WOTC editions are more likely to see a wizard ending a combat with a spell early as a problem while players of TSR editions are more likely to not care. Players of WOTC editions are more likely to be playing because they want a detailed tactical combat that takes a major chunk of time to play through; therefore they are more likely to see a spell or two ending combat quickly as bad because it cuts the part of the game they enjoy most out. Players of older versions of D&D are more likely to thank the wizard who put the goblins to sleep as they administer the coup-de-grace, check them for treasure and move on, thankful that they were spared the risk to their limited hit points.

Is the fact that many players today object to wizards using magic to quickly end a combat encounter wrong or silly? Of course not, but it does highlight one of the major difference between older editions of D&D and newer editions of D&D and show why some people are going to clearly prefer newer editions to older editions and vice-versa. There are major differences between older and newer editions that can't be swept under the rug as some try to do by saying "the game plays the same." It simply doesn't play the same.

The Fall 2011 Cancer Fund Drive is on (through October 15th). Every $10 donated gives you one chance to win a copy of ST1: Up the Garden Path (a rare D&D module published by TSR UK in 1986). Highest donors will also divide a list of other TSR and Judge's Guild RPG items. You can see the complete list of giveaway items and read more about this fund drive in this post: ST1: Up the Garden Path and More to Giveaway (for Cancer Fund Donors). This is in addition to the usual PDF downloads and other benefits of a donation to the RetrpoRoleplaying Cancer Fund. To get help us pay our cancer treatment related bills (and to get access to some special downloads and possibly the above mentioned special items), send a donation in any amount -- small or large -- to me via Paypal. Thank you!

Talysman said...
October 11, 2011 at 12:14 PM  

I think that *is* probably why WotC players complain about about wizards ending combat (and complain about wizards in general.) And there's a related factor: in TSR D&D, you get XP for treasure; in WotC D&D, you only get XP for combat. So, in older editions, the goal is to avoid combat where possible and focus on getting the treasure, while in newer editions, the focus is on combat.

Robert Fisher said...
October 11, 2011 at 2:19 PM  

That’s one of the things I play for! The opportunity to turn even or bad odds into quick victory. Without that, I might as well be reading a book instead.

I used to complain that TSR D&D was too combat-focused. That’s another one of those areas where Wizards D&D renewed my appreciation for TSR D&D.

I agree with Talysman that “encounter” in Wizards D&D seems to mean “combat encounter” more than in TSR D&D. (Although there are certainly groups that run counter that in both ways.) Even encounters that devolve into combat seem to end with it less often in the classic D&D games I play in.

Another piece to this focus on the combat encounter is that some Wizards D&D DM’s spend a lot of prep time on combat encounters. So, if PC action short-circuits a combat encounter, the DM may be left less prepared to continue the session. (Which then gets into the DM prep-time differences between editions.)

That said, we’ve short-circuited a number of combat encounters in the 3.5e game I’m currently playing in, and the DM is one to roll with such things. But our group is pretty “old school” in approach even though we sometimes play systems that aren’t.

Post a Comment

Post a Comment