Tuesday, October 8, 2013
Deal Me Another Hand, Frank.
One of the problems that seems to occur more often in modern gaming modules than in older one is the problem of static monsters; in other words, if there is an orc in room b6 then no matter how much noise your players make there will always be that orc in 6b. Your players could take a pick axe to the wall, blow holes in the fabric of reality with earth shattering wails that tear at their sanity and deafen everyone in a twelve mile radius and that orc will still be in 6b. His brother could be flayed alive, screaming his name, and that son-of-a-bitch will still be in 6 fucking b!
Over the years I have read countless opinions on the subject and it always comes down to a blame game. Bad Dungeon Masters blame game designers for not providing them with an efficient module that expressly details what each monster will do in the myriad of possible situations that happen during actual play. While terrible game designers will loudly complain that everyone playing their module must be an idiot because clearly they’re unable to run a good game.
Forget that noise.
Instead of complaining you should do something about the problem at hand. Your monsters should be active participants in the game reacting to the actions of the players. If the players are breaking down walls and causing a huge ruckus then the monsters should be working together to set ambushes that mess those kids up.
When I first started running Dungeons & Dragons (D&D) I tended to treat traps as an exercise in dice rolling to overcome the chall...
THE 2014 EDITION OF THE GREAT BLOG ROLL CALL IS UP! PLEASE UPDATE YOUR LINKS SO THAT THE DEAD BLOGS ARE OFF YOUR LISTS! I don...
A couple of days ago, in the post So You Like Looking in Sacks , I was talking about +Chris Tamm of Elfmaids & Octopi 's fantast...
Last year I started the Best Reads of the Week series to help publicize some of my favorite blogs and to help the community as a wh...