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, OSR, & D&D Variants
*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, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Pathfinder & Starfinder
The Devil's in the Details: Slavicsek reveals the Pit Fiend in all its glory
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="I'm A Banana" data-source="post: 4019360" data-attributes="member: 2067"><p>I like this, in general. All it's missing, for my purposes, is a <strong>For The PC's</strong> entry, for how to use this thing when it's on your side, but if Warlocks can summon them, perhaps that's good enonugh for me. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile :)" data-smilie="1"data-shortname=":)" /> </p><p></p><p></p><p></p><p></p><p>For a lot of people, this breaks verisimiltude.</p><p></p><p>The idea is that in the world, a Wizard looks like X. X, in D&D's case, is a character class.</p><p></p><p>If a Wizard looks like X, then all wizards should look like X. X should be designed for use with both PC's and monsters in mind.</p><p></p><p>However, 4e may decide that a Wizard looks like X if it's a PC, Y if it's a monster, Z if it's a villain, and have DM's juggle three different definitions of what a "Wizard" is in the game world. </p><p></p><p>This isn't inherently a terrible thing, because it lets you design X for PC use, Y for use in overlaying a monster, and Z for use in building a humanoid villain, and makes sure that all of them accomplish the goal of the Wizard enough to make it believable (fireballs and magic missiles and all). </p><p></p><p>However, it comes with a cost, and that cost is the fact that the Gnoll Wizard uses different rules than the Fire Giant Wizard, who uses different rules than the Halfling Wizard, who uses different rules than the hireling Wizard the PC's rented out at the local adventuring guild, who looks different than the Evil Wizard they are all fighting (even the Gnoll and the Fire Giant, who got recruited by the PC's halfway through the adventure, and, accordingly, changed what rules they operate under). </p><p></p><p>They're all called Wizards, and they're all supposed to represent the same thing in the game world (some nerd with a spellbook and a wand), but they use a different rule for each version because, possibly according to 4e's logic, the rules to make a PC Wizard wouldn't make a very good Fire Giant Wizard, because they're trying for different purposes. And if all you want a Wizard to do is shoot fireballs and magic missiles, and that's all any of these Wizards have in common, why not end the confusion dividing them up into different rules silos with different terms to make them truly different?</p><p></p><p>Somewhere between the outcry against "Simulationism!" and the hyperbolic example I had above, there's a comfortable middle ground that can hit both sides pretty well. </p><p></p><p>It's the question of "Do we design one Wizard that works well in a vast multitude of scenarios, knowing that someday, someone, somewhere, will come up with a scenario where it doesn't work?" (where the logic of 3e would have us headed in 4e) or "Do we design a variety of things we call Wizards that do different things depending upon where we put them, but share some broad similarities?"</p><p></p><p>Personally, I'd recommend using both approaches where it makes sense to use them. Thus, you have one "as-universal-as-possible" Wizard rule that you use to make Wizards in as many basic circumstances as you can theorize, and then, when you run into an area where it *doesn't* work, you alter the name a little and fluff it up a little and make a new rule for it.</p><p></p><p>4e seems to be embracing the latter approach even when the former approach would probably work just fine, whereas 3e definately focused on the former to the exclusion of the latter until late in the edition.</p></blockquote><p></p>
[QUOTE="I'm A Banana, post: 4019360, member: 2067"] I like this, in general. All it's missing, for my purposes, is a [B]For The PC's[/B] entry, for how to use this thing when it's on your side, but if Warlocks can summon them, perhaps that's good enonugh for me. :) For a lot of people, this breaks verisimiltude. The idea is that in the world, a Wizard looks like X. X, in D&D's case, is a character class. If a Wizard looks like X, then all wizards should look like X. X should be designed for use with both PC's and monsters in mind. However, 4e may decide that a Wizard looks like X if it's a PC, Y if it's a monster, Z if it's a villain, and have DM's juggle three different definitions of what a "Wizard" is in the game world. This isn't inherently a terrible thing, because it lets you design X for PC use, Y for use in overlaying a monster, and Z for use in building a humanoid villain, and makes sure that all of them accomplish the goal of the Wizard enough to make it believable (fireballs and magic missiles and all). However, it comes with a cost, and that cost is the fact that the Gnoll Wizard uses different rules than the Fire Giant Wizard, who uses different rules than the Halfling Wizard, who uses different rules than the hireling Wizard the PC's rented out at the local adventuring guild, who looks different than the Evil Wizard they are all fighting (even the Gnoll and the Fire Giant, who got recruited by the PC's halfway through the adventure, and, accordingly, changed what rules they operate under). They're all called Wizards, and they're all supposed to represent the same thing in the game world (some nerd with a spellbook and a wand), but they use a different rule for each version because, possibly according to 4e's logic, the rules to make a PC Wizard wouldn't make a very good Fire Giant Wizard, because they're trying for different purposes. And if all you want a Wizard to do is shoot fireballs and magic missiles, and that's all any of these Wizards have in common, why not end the confusion dividing them up into different rules silos with different terms to make them truly different? Somewhere between the outcry against "Simulationism!" and the hyperbolic example I had above, there's a comfortable middle ground that can hit both sides pretty well. It's the question of "Do we design one Wizard that works well in a vast multitude of scenarios, knowing that someday, someone, somewhere, will come up with a scenario where it doesn't work?" (where the logic of 3e would have us headed in 4e) or "Do we design a variety of things we call Wizards that do different things depending upon where we put them, but share some broad similarities?" Personally, I'd recommend using both approaches where it makes sense to use them. Thus, you have one "as-universal-as-possible" Wizard rule that you use to make Wizards in as many basic circumstances as you can theorize, and then, when you run into an area where it *doesn't* work, you alter the name a little and fluff it up a little and make a new rule for it. 4e seems to be embracing the latter approach even when the former approach would probably work just fine, whereas 3e definately focused on the former to the exclusion of the latter until late in the edition. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
The Devil's in the Details: Slavicsek reveals the Pit Fiend in all its glory
Top