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
Two swift actions in one round
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="Artoomis" data-source="post: 3633486" data-attributes="member: 111"><p>The difference is you add a potential host of possibilities to the Move Action. NOT a good idea. The more actions (other than actually moving) you grant the more deadly each round becomes. This is NOT a good idea as a bad choice for one round becomes more unrecoverable than it is already.</p><p></p><p>Overall, it is not a good idea to allow Move Action to be used for actions not intended to be related to moving in some way or already defined as a move action (you currently can use move actions for drawing a weapon, for example).</p><p></p><p>I am certain if you allowed this you'd be the victim of all sorts on unintended consequences as a result of allowing that move action to be used for many things not already defined.</p><p></p><p>The real answer for this is to choose one of the following:</p><p></p><p>1. Not allow Swift/Immediate actions to be used in place of a Move or Standard Action. This does not seem to me to be a very good choice as being unreasonably restrictive.</p><p></p><p>2. Define (perhaps as it comes up each time) every Swift/Immediate Action as doable either in the place of a Move Action or in place of a Standard Action. Careful, though - Move Actions may be done twice a round! Odd things may happen in some cases. This way carries extra administrative burden and some very significant risk of unintended consequences.</p><p></p><p>3. Allow Swift/Immediate actions to also be taken as a Standard Action, but not as a Move Action. This seems to be to be an excellent way to go. It's very simple and easy to adjudicate and solves the weird problem of a Swift Action not being allowed to be done more "deliberately," as it were.</p><p></p><p>As for the badge and spell under discussion, they are both Swift Actions precisely so only one may be used - else one or the other could have been a "Free Action." Under my proposal you could use both, but that would be useless.</p><p></p><p>Swift Actions are designed to force you to choose one. Once you've done one, you do not get another (or an Immediate Action). Free Actions are for when you do not care if it gets done more than once in a round, or in addition to a Swift/immediate Action. Allowing one to give up a Standard Action to do a Swift Action seems only slightly generous. Allowing one to give up a Move Action to do so seems like being overly generous.</p></blockquote><p></p>
[QUOTE="Artoomis, post: 3633486, member: 111"] The difference is you add a potential host of possibilities to the Move Action. NOT a good idea. The more actions (other than actually moving) you grant the more deadly each round becomes. This is NOT a good idea as a bad choice for one round becomes more unrecoverable than it is already. Overall, it is not a good idea to allow Move Action to be used for actions not intended to be related to moving in some way or already defined as a move action (you currently can use move actions for drawing a weapon, for example). I am certain if you allowed this you'd be the victim of all sorts on unintended consequences as a result of allowing that move action to be used for many things not already defined. The real answer for this is to choose one of the following: 1. Not allow Swift/Immediate actions to be used in place of a Move or Standard Action. This does not seem to me to be a very good choice as being unreasonably restrictive. 2. Define (perhaps as it comes up each time) every Swift/Immediate Action as doable either in the place of a Move Action or in place of a Standard Action. Careful, though - Move Actions may be done twice a round! Odd things may happen in some cases. This way carries extra administrative burden and some very significant risk of unintended consequences. 3. Allow Swift/Immediate actions to also be taken as a Standard Action, but not as a Move Action. This seems to be to be an excellent way to go. It's very simple and easy to adjudicate and solves the weird problem of a Swift Action not being allowed to be done more "deliberately," as it were. As for the badge and spell under discussion, they are both Swift Actions precisely so only one may be used - else one or the other could have been a "Free Action." Under my proposal you could use both, but that would be useless. Swift Actions are designed to force you to choose one. Once you've done one, you do not get another (or an Immediate Action). Free Actions are for when you do not care if it gets done more than once in a round, or in addition to a Swift/immediate Action. Allowing one to give up a Standard Action to do a Swift Action seems only slightly generous. Allowing one to give up a Move Action to do so seems like being overly generous. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Two swift actions in one round
Top