Dezhem |
1 person marked this as a favorite. |
Question the First
Is spending a ki point that's called out by a feat in order to provide an additional effect (such as Ki Throw), a swift action?
Special: A monk may gain Ki Throw as a bonus feat at 10th level. A monk with this feat can affect creatures larger than his own size by spending 1 ki point per size category difference.
Does not list what sort of an action it is. The closest reference can be found under the Qinggong archetype, where emulating Feats is expressly called out as a free action.
At 4th level, as a swift action, a maneuver master may spend 1 point from his ki pool before attempting a combat maneuver. He can roll his combat maneuver check for that maneuver twice and use the better result.
This ability replaces slow fall.
Neither does this.
Question the Second
Is Flurry of Manoeuvres ineligible for spending a Ki point for an extra attack? It replaces Flurry of Blows, which is called out by the Ki Pool ability in the CRB. Considering that The Maneuver Master came out in UC, what's the ruling on things like this, where a core ability is replaced by a similar ability and thus loses out on some base feature?
laarddrym |
Ki Throw does not require you to spend a ki point, or it would say so in the description. Look at the feat Enhanced Ki Throw: that one requires a ki point, but not a swift action, you just have to burn the ki to deal the damage.
Reliable Maneuver does require a swift action to spend the ki point, because it says so in the very beginning of the description. Spending ki points doesn't always mean you need to use a swift action.
Hope that helps!
laarddrym |
It really shouldn't be. If your GM determines that Ki Throw requires a ki point and a swift action, then it leaves no room for a character to ever be able to take Enhanced Ki Throw, which by that ruling would ALSO require a swift action and a ki point.
As a monk or a ninja, you already have a limited ki pool, and you already have alot of things that take up swift actions. Economy of ki pool and economy of (swift) action is already limiting enough, the GM should NOT be putting more restrictions in an already restriction heavy area, especially when it is not supported by RAW.