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
*Pathfinder & Starfinder
Get pedantic on Feeblemind
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="Cheiromancer" data-source="post: 3165361" data-attributes="member: 141"><p>Many wizards enjoy hefty bonuses to their intelligence. If <em>feeblemind</em> only affected the base score but not inherent or enhancement bonuses it wouldn't have anywhere near as dramatic effect. So I'm agreeable to the notion that the feebleminded state can't be mitigated by bonuses to intelligence or charisma. I'm inclined to say that the new stats count for the purpose of ability damage or drain; a single point of damage will reduce them to 0, and thus incapacitate them. </p><p></p><p>My general heuristic is that one spell trumps a lower level one in the absence of specific wording. And that defensive spells trump offensive spells. If a 5th level <em>irresistible force</em> meets a 5th level <em>immovable object</em> then the <em>immovable object</em> wins. If an 8th level divination spell is written so that it "ignores magical protections" I wouldn't allow it to trump a <em>mind blank</em> unless it said "ignores magical protections such as <em>mind blank</em>". If it were 9th level that said it "ignores magical protections" I would allow it to do so, even in the absence of a specific mention of <em>mind blank</em>.</p><p></p><p>I consider healing/curing/removing to be defensive, and so should trump offensive spells of the same level, unless mentioned by name or description. A spell that afflicts or curses a subject is offensive, of course. </p><p></p><p>If <em>break enchantment</em> said it didn't cure <em>feeblemind</em>, that would be the end of the matter. Similarly if <em>break enchantment</em> mentioned <em>feeblemind</em> by name (instead of by description) there would be no rules question to explore in this thread. As it is, the literal meaning of "until" seems to conflict with the description of <em>break enchantment</em>.</p><p></p><p>The question of designer intent was raised. Did the same person who designed <em>feeblemind</em> also design <em>break enchantment</em>? Were these spells revised or reviewed by someone with a different set of intentions? I don't think this is a profitable line of inquiry. You have to go down to the principle that the spell means what it says. If I as a designer didn't want <em>feeblemind</em> to be broken by <em>break enchantment</em> I would either have to raise the level of <em>feeblemind</em> so that the description of <em>break enchantment</em> wouldn't apply, or change the description of <em>break enchantment</em> so that it didn't apply to fifth level instantaneous enchantments. Or call out <em>break enchantment</em> either by name or description ("cannot be reversed by spells of fifth level or less," maybe with additional text like "such as <em>remove curse</em> or <em>dispel magic</em>." Actually, this wording would make the conflict more explicit; each would say that it trumps the other. In the absence of this wording, I think the position of <em>feeblemind</em> is weaker.) If I don't do this, then I am like someone who puts both an <em>irresistible force</em> and an <em>immovable object</em> in the same book; I create an interpretive puzzle for DMs.</p><p></p><p>I accept that "feebleminded" is a state (like "slain by death magic") and that a creature "remains in this state until a heal, limited wish, miracle, or wish spell is used to cancel the effect of the feeblemind". However this language is trumped by the <em>break enchantment</em> spell description, which says it can reverse an instantaneous enchantment of 5th level or lower. I take "reverse" to be equivalent to "cancel" - is there any dispute on this? In the case of a conflict between two spells of equal level I would resolve the conflict in terms of the spell which is curative or restorative, in accordance with my general policy of how to break ties of this sort.</p><p></p><p>The question, for me, boils down to how to resolve the question of what happens when an <em>irresistible force</em> meets an <em>immovable object</em>. I don't think designer intent is the best approach. I assign precedence to defensive/curative over offensive, but there may be a better way to approach such a question.</p><p></p><p>Can we agree that this is the question? Can we agree that <em>feeblemind</em> imposes a state that remains "until a heal, limited wish, miracle or wish spell is used"? Can we agree that <em>break enchantment</em> can reverse a 5th level instantaneous enchantment? Can we agree that <em>feeblemind</em> is a 5th level instantaneous enchantment? Can we agree that these statements are inconsistent, and that a procedure needs to be developed that resolves these inconsistencies?</p><p></p><p>If so, then I submit that the procedure of giving precedence to defensive/curative over offensive is worthy of consideration, and I invite people to suggest other ways in which conflicts between spells may be resolved. I am sure there are lots of alternatives.</p></blockquote><p></p>
[QUOTE="Cheiromancer, post: 3165361, member: 141"] Many wizards enjoy hefty bonuses to their intelligence. If [i]feeblemind[/i] only affected the base score but not inherent or enhancement bonuses it wouldn't have anywhere near as dramatic effect. So I'm agreeable to the notion that the feebleminded state can't be mitigated by bonuses to intelligence or charisma. I'm inclined to say that the new stats count for the purpose of ability damage or drain; a single point of damage will reduce them to 0, and thus incapacitate them. My general heuristic is that one spell trumps a lower level one in the absence of specific wording. And that defensive spells trump offensive spells. If a 5th level [i]irresistible force[/i] meets a 5th level [i]immovable object[/i] then the [i]immovable object[/i] wins. If an 8th level divination spell is written so that it "ignores magical protections" I wouldn't allow it to trump a [i]mind blank[/i] unless it said "ignores magical protections such as [i]mind blank[/i]". If it were 9th level that said it "ignores magical protections" I would allow it to do so, even in the absence of a specific mention of [i]mind blank[/i]. I consider healing/curing/removing to be defensive, and so should trump offensive spells of the same level, unless mentioned by name or description. A spell that afflicts or curses a subject is offensive, of course. If [i]break enchantment[/i] said it didn't cure [i]feeblemind[/i], that would be the end of the matter. Similarly if [i]break enchantment[/i] mentioned [i]feeblemind[/i] by name (instead of by description) there would be no rules question to explore in this thread. As it is, the literal meaning of "until" seems to conflict with the description of [i]break enchantment[/i]. The question of designer intent was raised. Did the same person who designed [i]feeblemind[/i] also design [i]break enchantment[/i]? Were these spells revised or reviewed by someone with a different set of intentions? I don't think this is a profitable line of inquiry. You have to go down to the principle that the spell means what it says. If I as a designer didn't want [i]feeblemind[/i] to be broken by [i]break enchantment[/i] I would either have to raise the level of [i]feeblemind[/i] so that the description of [i]break enchantment[/i] wouldn't apply, or change the description of [i]break enchantment[/i] so that it didn't apply to fifth level instantaneous enchantments. Or call out [i]break enchantment[/i] either by name or description ("cannot be reversed by spells of fifth level or less," maybe with additional text like "such as [i]remove curse[/i] or [i]dispel magic[/i]." Actually, this wording would make the conflict more explicit; each would say that it trumps the other. In the absence of this wording, I think the position of [i]feeblemind[/i] is weaker.) If I don't do this, then I am like someone who puts both an [i]irresistible force[/i] and an [i]immovable object[/i] in the same book; I create an interpretive puzzle for DMs. I accept that "feebleminded" is a state (like "slain by death magic") and that a creature "remains in this state until a heal, limited wish, miracle, or wish spell is used to cancel the effect of the feeblemind". However this language is trumped by the [i]break enchantment[/i] spell description, which says it can reverse an instantaneous enchantment of 5th level or lower. I take "reverse" to be equivalent to "cancel" - is there any dispute on this? In the case of a conflict between two spells of equal level I would resolve the conflict in terms of the spell which is curative or restorative, in accordance with my general policy of how to break ties of this sort. The question, for me, boils down to how to resolve the question of what happens when an [i]irresistible force[/i] meets an [i]immovable object[/i]. I don't think designer intent is the best approach. I assign precedence to defensive/curative over offensive, but there may be a better way to approach such a question. Can we agree that this is the question? Can we agree that [i]feeblemind[/i] imposes a state that remains "until a heal, limited wish, miracle or wish spell is used"? Can we agree that [i]break enchantment[/i] can reverse a 5th level instantaneous enchantment? Can we agree that [i]feeblemind[/i] is a 5th level instantaneous enchantment? Can we agree that these statements are inconsistent, and that a procedure needs to be developed that resolves these inconsistencies? If so, then I submit that the procedure of giving precedence to defensive/curative over offensive is worthy of consideration, and I invite people to suggest other ways in which conflicts between spells may be resolved. I am sure there are lots of alternatives. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Get pedantic on Feeblemind
Top