Upgrade your account to a Community Supporter account and remove most of the site ads.
ShortQuests -- Pocket Sized Adventures! An all-new collection of digest-sized D&D adventures designed for 1-2 game sessions.

Reply to thread

Message: <blockquote data-quote="atom crash" data-source="post: 2109418" data-attributes="member: 22162">I've always assumed that the rule allowing a single Swift Action per round was not so much to force a choice about which Swift Action spell to cast, but merely to limit how many spells you could get off in a round. The designers obviously don't want anyone to be able to get off more than two spells in any given round, and being able to cast two is going to cost you. That's why I agree with Plane Sailing and silentspace and would allow without hesitation acharacter to cast a Swift Action spell as a standard action. If you use a standard action to cast a Swift Action spell, you're using your standard action that you could be using for something else, just like being able to take a second move action rather than a standard action. Therefore I see it as a balanced option.Another limiting factor is that most Swift Action spells I recall from my reading of Complete Arcane seem designed to help a character use a particular standard action (sorry, I don't have my book at hand, but I believe the spell that makes an opponent think he's flanked has a Swift Action casting time; can someone double check?). It struck me that the Swift Action spells seemd to be designed for optimal use to be cast in the same round as the attack or action they benefit. Casting two such spells in a single round would deny the character the opportunity to benefit from them until the next round.</blockquote>

Verification