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
*Dungeons & Dragons
So what's the problem with restrictions, especially when it comes to the Paladin?
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="JamesonCourage" data-source="post: 6119934" data-attributes="member: 6668292"><p>I see it as putting the fiction first, and then making the mechanics to match that. That is, in the fiction, I like that any Paladin that steps off the path loses his powers. To make that match mechanically, we give him a path, and we say "if you step off of this, you lose your Paladin powers."</p><p></p><p>Sure, you don't have to do it this way when designing the class. But, if the world you want includes "step off this path and lose these powers," then you need a "fall" mechanic. Carrots for staying on the path (fate tokens, divine tokens, whatever) aren't good enough, because you don't lose your powers, and thus the mechanics are not accurately reflecting the fiction.</p><p></p><p>Now, there's a good debate as to who dictates when the "fall" kicks in, but sometimes it should be obvious, and the GM should have the final say, in my opinion (as with all things). For instance, if the Paladin kills a Good shopkeeper in cold blood to take his stuff without paying for it, and the player says "no, I don't fall," we have a problem with the class living up to how it is fictionally supposed to function. Thus, the GM should be able to say "um, no, you committed blatant murder so you could steal. You lose your powers." Again, in my opinion.</p><p></p><p>Personally, I know there's a big movement for the carrot rather than the stick, but I like using both. They're both appropriate tools in RPG design at different times (like fail forward and, you know, just failure). And, if the fiction calls for "stick", then go stick.</p><p></p><p>Is a "fall" mechanic absolutely necessary? Well, for the Paladin that I want to play, absolutely. For many (most?) others? Not so much, and I get that. I'm not sure how they're going to resolve it in 5e, but I think it's not a strawman at all to say "the fiction works this way, so we make mechanics match, and following consequences from actions can determine a fall." Just my thoughts, though. As always, play what you like <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></blockquote><p></p>
[QUOTE="JamesonCourage, post: 6119934, member: 6668292"] I see it as putting the fiction first, and then making the mechanics to match that. That is, in the fiction, I like that any Paladin that steps off the path loses his powers. To make that match mechanically, we give him a path, and we say "if you step off of this, you lose your Paladin powers." Sure, you don't have to do it this way when designing the class. But, if the world you want includes "step off this path and lose these powers," then you need a "fall" mechanic. Carrots for staying on the path (fate tokens, divine tokens, whatever) aren't good enough, because you don't lose your powers, and thus the mechanics are not accurately reflecting the fiction. Now, there's a good debate as to who dictates when the "fall" kicks in, but sometimes it should be obvious, and the GM should have the final say, in my opinion (as with all things). For instance, if the Paladin kills a Good shopkeeper in cold blood to take his stuff without paying for it, and the player says "no, I don't fall," we have a problem with the class living up to how it is fictionally supposed to function. Thus, the GM should be able to say "um, no, you committed blatant murder so you could steal. You lose your powers." Again, in my opinion. Personally, I know there's a big movement for the carrot rather than the stick, but I like using both. They're both appropriate tools in RPG design at different times (like fail forward and, you know, just failure). And, if the fiction calls for "stick", then go stick. Is a "fall" mechanic absolutely necessary? Well, for the Paladin that I want to play, absolutely. For many (most?) others? Not so much, and I get that. I'm not sure how they're going to resolve it in 5e, but I think it's not a strawman at all to say "the fiction works this way, so we make mechanics match, and following consequences from actions can determine a fall." Just my thoughts, though. As always, play what you like :) [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
So what's the problem with restrictions, especially when it comes to the Paladin?
Top