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
A use for True Strike
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="Li Shenron" data-source="post: 7994166" data-attributes="member: 1465"><p>Hiding because tangential to the main discussion.</p><p></p><p>[spoiler]</p><p></p><p></p><p>As usual the Sage Advice speaks in riddles.</p><p></p><p>Looking at Twinned Spell, we see that this ability can be used to get close to casting 2 non-cantrips in the same round: if you have 2 slots of a certain level X, you can "burn" one of them as a bonus action to get the X sorcery points required to use Twinned Spell on the other slot.</p><p></p><p>There are already some obvious caveats, first of all they have to be <em>same </em>spell, but then technically they are really just 1 casting, so among other things it takes a single counterspell to stop them.</p><p></p><p>So probably the first <em>intent </em>is to simply limit the general usefulness of Twinned Spell to make it less likely that a Sorcerer uses it every single round, consuming her slots at double speed to cast 2 spells for the whole battle. So they put more limitations on which spells you can use it with, but at this point which spells to ban is still arbitrary (for example, they could have said "you can't Twin spells of your current highest spell level", or forbidding concentration spells or spells longer than instantaneous...).</p><p></p><p>But the second <em>intent </em>is probably for playability's sake to avoid Twinned Spell to cause too many rolls at once. That's why you can't Twin area spells, otherwise you might trigger a lot of saves (notice that perhaps for the same reason they did not design a metamagic which e.g. doubles a spell area).</p><p></p><p>Why then no "self" spells? Most self spells don't stack with themselves or simply don't make sense to cast twice anyway. However, <em>some</em> self spells are actually... area spells! For example Lightning Bolt or Prismatic Spray. Basically if the "area" starts from the caster, the spell usually has Range: Self.</p><p></p><p>On the other hand, I think the Sage is wrong when he says that a spell is disqualified if "it <strong>can</strong> target an object". Nowhere in the RAW it says something like that, it only says "targets only one creature" which is not about the spell in general but it's about a particular casting of that spell. In fact the RAW also says "To be eligible, a spell must be incapable of targeting more than one creature <em>at the spell’s current level</em>" (which is once again to avoid lots of rolls if you Twinned a Magic Missile or Scorching Ray even directing all bolts the same creature). If you can Twin a 1st-level Charm Person because it doesn't matter that the spell can't be twinned when you cast it on multiple targets, then you can Twin a Dispel Magic cast on a creature because it doesn't matter that the spell can't be twinned when cast on an object. Unless they update the errata to "To be eligible, a spell must be incapable of targeting <em>an object or </em>more than one creature <em>at the spell’s current level</em>" the RAW allows to Twin a Dispel Magic or Remove Curse, as long as you cast it on a creature.</p><p></p><p>But generally speaking, I cannot think of any ineligible spell which would truly break the game if you allow it to be Twinned. Not a spell casting an object for example, but neither Fireball to be honest.</p><p></p><p>And I generally despise this design approach of adding spanners in the works just to <em>indirectly</em> tone down a character ability, because a savvy gamer will always find enough particular spells which do qualify and will happily use Twinned Spell every round anyway. If they wanted to prevent this sort of abuse, they should have <em>directly</em> prevented it, maybe putting a spell level limit or another usage limit.</p><p>[/spoiler]</p></blockquote><p></p>
[QUOTE="Li Shenron, post: 7994166, member: 1465"] Hiding because tangential to the main discussion. [spoiler] As usual the Sage Advice speaks in riddles. Looking at Twinned Spell, we see that this ability can be used to get close to casting 2 non-cantrips in the same round: if you have 2 slots of a certain level X, you can "burn" one of them as a bonus action to get the X sorcery points required to use Twinned Spell on the other slot. There are already some obvious caveats, first of all they have to be [I]same [/I]spell, but then technically they are really just 1 casting, so among other things it takes a single counterspell to stop them. So probably the first [I]intent [/I]is to simply limit the general usefulness of Twinned Spell to make it less likely that a Sorcerer uses it every single round, consuming her slots at double speed to cast 2 spells for the whole battle. So they put more limitations on which spells you can use it with, but at this point which spells to ban is still arbitrary (for example, they could have said "you can't Twin spells of your current highest spell level", or forbidding concentration spells or spells longer than instantaneous...). But the second [I]intent [/I]is probably for playability's sake to avoid Twinned Spell to cause too many rolls at once. That's why you can't Twin area spells, otherwise you might trigger a lot of saves (notice that perhaps for the same reason they did not design a metamagic which e.g. doubles a spell area). Why then no "self" spells? Most self spells don't stack with themselves or simply don't make sense to cast twice anyway. However, [I]some[/I] self spells are actually... area spells! For example Lightning Bolt or Prismatic Spray. Basically if the "area" starts from the caster, the spell usually has Range: Self. On the other hand, I think the Sage is wrong when he says that a spell is disqualified if "it [B]can[/B] target an object". Nowhere in the RAW it says something like that, it only says "targets only one creature" which is not about the spell in general but it's about a particular casting of that spell. In fact the RAW also says "To be eligible, a spell must be incapable of targeting more than one creature [I]at the spell’s current level[/I]" (which is once again to avoid lots of rolls if you Twinned a Magic Missile or Scorching Ray even directing all bolts the same creature). If you can Twin a 1st-level Charm Person because it doesn't matter that the spell can't be twinned when you cast it on multiple targets, then you can Twin a Dispel Magic cast on a creature because it doesn't matter that the spell can't be twinned when cast on an object. Unless they update the errata to "To be eligible, a spell must be incapable of targeting [I]an object or [/I]more than one creature [I]at the spell’s current level[/I]" the RAW allows to Twin a Dispel Magic or Remove Curse, as long as you cast it on a creature. But generally speaking, I cannot think of any ineligible spell which would truly break the game if you allow it to be Twinned. Not a spell casting an object for example, but neither Fireball to be honest. And I generally despise this design approach of adding spanners in the works just to [I]indirectly[/I] tone down a character ability, because a savvy gamer will always find enough particular spells which do qualify and will happily use Twinned Spell every round anyway. If they wanted to prevent this sort of abuse, they should have [I]directly[/I] prevented it, maybe putting a spell level limit or another usage limit. [/spoiler] [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
A use for True Strike
Top