Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Dungeons & Dragons
Working in the Game Mine
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Aberzanzorax" data-source="post: 5970067" data-attributes="member: 64209"><p>I'm not calling 4e monsters bland. I'm calling monsters without weaknesses that show up in game bland. I put equal weight/blame on encounter design for 3e and 4e in that regard.</p><p> </p><p> </p><p>You asked if we were talking about encounter design, and, in a sense, no, I'm not talking about <em>encounter</em> design. I'm talking about <em>monster</em> design.</p><p> </p><p>I <em>am</em> talking about monster design primarily as it relates to the encounter, however. And you're correct to not read too much into my examples...they're just there for facilitating understanding (well, that was the intent, anyway).</p><p> </p><p> </p><p>I'm, in a nutshell, primarily saying that a monster isn't there to fulfil a role. It may "fall into" a role, sure. Naming that role helps to categorize monsters (especially for dm selection). But my point is that monsters are there to be evocative monsters...and that any given monster might fulfil multiple roles. It might also be poor at some roles, and rather than searching out a different monster, or creating a variant, it can be good adventure design and good writing to use the monster in a sub par way to highlight its weakness. </p><p> </p><p> </p><p>Regarding the ogre archers and the distinction between encounter design versus monster design...I'm designing a monster who has pros (strength and hp) and flaws (clumsy). The rock throwing/archery point was meant that the ogres would be bad at it. I'm making it an easy encounter to highlight a flaw of the monster. The Ogres do not want a ranged encounter (but it makes sense in context that one would occur). The player (characters) are happy to have a ranged encounter against these up-close monsters. If there are "ogre rock thrower" variants who are bad up close, but great ranged attackers, then we don't have this phenomenon occurring.</p><p> </p><p> </p><p>I'm not really discussing 4e or 3e in any way...I'm mostly theorizing about what I believe to be good design. You (Pemerton) state:</p><p></p><p> </p><p>I think that's what I most need to clarify. </p><p> </p><p>No, I don't mean exploiting numbers or terrain (at least not necessarily). I mean, simply put "let goblins be goblins". </p><p> </p><p>What would the goblins do to keep invaders out of their lair? Some would do x, some y, some z. I think there's an advantage to having "regular goblins with bows, regular goblins with short swords, and regular goblins holding a defensive line". The point there is that if they are good enough at more than one thing (rather than breaking them down into super-specialized sub groupings), then more than one meaningful encounter can take place, and it will be different, but the same. It's the sameness I'm arguing for as a good thing...that players develop a base understanding of "goblin" and know that the, say, archery might be bad for themselves, but that they'll wipe the goblins when the critters are forced to fight hand to hand. </p><p> </p><p>To put it another way, I think there is something lost when there are goblins who are good archers for the archery combat, and goblins who are good tunnelers for the tunnel ambush, and goblins who are brutish for the elite combat. While this varies the combats, it makes goblins more meaningless as a race (because in 2 levels it's orcs who are good at all three, and then bugbears, ogres, giants, etc). But those are comparisons amongst very similar species. </p><p> </p><p>What about elves versus goblins, versus dwarves, versus mephits? Each has their own schtick, generally, but that schtick is lost between the tough elf, the flying goblin, the nimble dwarf and the tricky mephit variants (if they exist). </p><p> </p><p> </p><p>I've not thought much about edition so far. I think everything I mention has been a problem in both 3e and 4e. Designing a monster for a role (named or not) is the issue I take ubrage with. </p><p> </p><p>However, let's bring up 4e. One great element is that goblins, orcs, elves, mephits, etc. are all, on a base level, quite different from one another. I'm not arguing to erase that difference...I applaud it. What I'm arguing against is goblin skirmisher versus goblin lurker versus goblin elite (here we're editionless again, as this also occurred in 3e). If its a goblin only campaign, then that variety is welcomed...the players will deal with a lot of e.g. goblin lurkers and get to know them. But if it's a one shot adventure to hit a goblin lair...then let the players learn the enemy, and give the enemy more than one thing to do. Sure, maybe their king is tougher (an elite or a brute or a solo). But hit players with the same goblins several times so the players learn what they are good at, moderate at, and poor at...and let the players adapt to this. Allow players to force goblins to get close because they're weaker that way. Do not make each goblin encounter essentially a "new monster" by introducing too many variants of "goblin". Yes, every encounter will be new and challenging, and different, but the continuity and the learning curve suffer.</p><p> </p><p> </p><p>Well...I tried to be more clear...but it's late here, and I'm not sure I was. Hit me with questions for more clarity if ya like and I'll post a response tomorrow.</p></blockquote><p></p>
[QUOTE="Aberzanzorax, post: 5970067, member: 64209"] I'm not calling 4e monsters bland. I'm calling monsters without weaknesses that show up in game bland. I put equal weight/blame on encounter design for 3e and 4e in that regard. You asked if we were talking about encounter design, and, in a sense, no, I'm not talking about [I]encounter[/I] design. I'm talking about [I]monster[/I] design. I [I]am[/I] talking about monster design primarily as it relates to the encounter, however. And you're correct to not read too much into my examples...they're just there for facilitating understanding (well, that was the intent, anyway). I'm, in a nutshell, primarily saying that a monster isn't there to fulfil a role. It may "fall into" a role, sure. Naming that role helps to categorize monsters (especially for dm selection). But my point is that monsters are there to be evocative monsters...and that any given monster might fulfil multiple roles. It might also be poor at some roles, and rather than searching out a different monster, or creating a variant, it can be good adventure design and good writing to use the monster in a sub par way to highlight its weakness. Regarding the ogre archers and the distinction between encounter design versus monster design...I'm designing a monster who has pros (strength and hp) and flaws (clumsy). The rock throwing/archery point was meant that the ogres would be bad at it. I'm making it an easy encounter to highlight a flaw of the monster. The Ogres do not want a ranged encounter (but it makes sense in context that one would occur). The player (characters) are happy to have a ranged encounter against these up-close monsters. If there are "ogre rock thrower" variants who are bad up close, but great ranged attackers, then we don't have this phenomenon occurring. I'm not really discussing 4e or 3e in any way...I'm mostly theorizing about what I believe to be good design. You (Pemerton) state: I think that's what I most need to clarify. No, I don't mean exploiting numbers or terrain (at least not necessarily). I mean, simply put "let goblins be goblins". What would the goblins do to keep invaders out of their lair? Some would do x, some y, some z. I think there's an advantage to having "regular goblins with bows, regular goblins with short swords, and regular goblins holding a defensive line". The point there is that if they are good enough at more than one thing (rather than breaking them down into super-specialized sub groupings), then more than one meaningful encounter can take place, and it will be different, but the same. It's the sameness I'm arguing for as a good thing...that players develop a base understanding of "goblin" and know that the, say, archery might be bad for themselves, but that they'll wipe the goblins when the critters are forced to fight hand to hand. To put it another way, I think there is something lost when there are goblins who are good archers for the archery combat, and goblins who are good tunnelers for the tunnel ambush, and goblins who are brutish for the elite combat. While this varies the combats, it makes goblins more meaningless as a race (because in 2 levels it's orcs who are good at all three, and then bugbears, ogres, giants, etc). But those are comparisons amongst very similar species. What about elves versus goblins, versus dwarves, versus mephits? Each has their own schtick, generally, but that schtick is lost between the tough elf, the flying goblin, the nimble dwarf and the tricky mephit variants (if they exist). I've not thought much about edition so far. I think everything I mention has been a problem in both 3e and 4e. Designing a monster for a role (named or not) is the issue I take ubrage with. However, let's bring up 4e. One great element is that goblins, orcs, elves, mephits, etc. are all, on a base level, quite different from one another. I'm not arguing to erase that difference...I applaud it. What I'm arguing against is goblin skirmisher versus goblin lurker versus goblin elite (here we're editionless again, as this also occurred in 3e). If its a goblin only campaign, then that variety is welcomed...the players will deal with a lot of e.g. goblin lurkers and get to know them. But if it's a one shot adventure to hit a goblin lair...then let the players learn the enemy, and give the enemy more than one thing to do. Sure, maybe their king is tougher (an elite or a brute or a solo). But hit players with the same goblins several times so the players learn what they are good at, moderate at, and poor at...and let the players adapt to this. Allow players to force goblins to get close because they're weaker that way. Do not make each goblin encounter essentially a "new monster" by introducing too many variants of "goblin". Yes, every encounter will be new and challenging, and different, but the continuity and the learning curve suffer. Well...I tried to be more clear...but it's late here, and I'm not sure I was. Hit me with questions for more clarity if ya like and I'll post a response tomorrow. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Working in the Game Mine
Top