Push, Knockdown, and Grab from the respective eidolon feats all require the eidolon's last action to be a successful Strike. If I were to use this sequence with Act Together, I think I would have to strictly do it this way.
1st action: Eidolon Strike
2nd action: Act Together (Eidolon Push + Summoner single action)
I wouldn't be able to do it the other way where we Act Together with the Strike and then Push because Act Together becomes the eidolon's last action instead of a Strike. Is that right?
Act Together doesn't play well with rules regarding 'last action used' or 'next action is'. Those rules for things like Knockdown and Metamagic weren't written with Summoner in mind - mostly because the Summoner class hadn't been written yet.
So if the GM wants to be an antagonist of the players, then they could indeed rule that the Eidolon's 'last action used' was Act Together, not Strike. Or even that you have to have the Eidolon use their half of Act Together first before the Summoner can take their half - otherwise the 'last action used' was the Summoner's action, not the Eidolon's Strike. And if you try to rearrange your action usage to avoid that by having Act Together be the Summoner's action and the Eidolon's Strike and then have the Eidolon use Knockdown, then the GM can still rule that the 'last action used' was Act Together.
But honestly, I just wouldn't bother with that. Playing under an antagonist GM isn't fun. For Summoner, 'last action used' and 'next action is' should only be looking at the actions that each half of the pair actually took - not actions that the other half took, and not the meta-action Act Together.
From its wording, I read that Act together is always the first action and is then followed by the Eidolon or Summoner's action or activity that uses the same number of actions as Act together and then the single action of the other character.
It says 'and', but not 'then'. So the wording of the rule itself leaves it open to interpretation.
And the examples aren't fully exhaustive, IMO. Both examples to run it with the activity first and then the single action.
But the examples also only give simple actions (Strike and Stride) as the single action - not any 1-action cost activities such as casting Boost Eidolon. I assume that those are allowed, but that also isn't clear from the wording of the rule due to the ambiguity of the word 'action' in the game rules generally.
| 1 person marked this as a favorite. |
Act Together doesn't play well with rules regarding 'last action used' or 'next action is'. Those rules for things like Knockdown and Metamagic weren't written with Summoner in mind - mostly because the Summoner class hadn't been written yet.
Oh yeah, metamagic is interesting too. If it was read as literally as possible, this would result in the opposite sequence compared to push/knockdown/grab. The metamagic action has to be within the Act Together and be used before the separate Cast a Spell.
So if the GM wants to be an antagonist of the players, then they could indeed rule that the Eidolon's 'last action used' was Act Together, not Strike. Or even that you have to have the Eidolon use their half of Act Together first before the Summoner can take their half - otherwise the 'last action used' was the Summoner's action, not the Eidolon's Strike. And if you try to rearrange your action usage to avoid that by having Act Together be the Summoner's action and the Eidolon's Strike and then have the Eidolon use Knockdown, then the GM can still rule that the 'last action used' was Act Together.
Thankfully the order of actions can't be GM bullied in this context. The Knockdown action specifically call for the monster's (eidolon's in this case) last action and doesn't care about anybody else's. Whatever the order, the summoner and eidolon would each have their own individual 'last action used.'
The summoner performs and spends the actions for Act Together, and then you both perform the subordinate actions in tandem, so you could do it the latter way if you want because the eidolon's last action would have been Strike
I think I need a refresher on subordinate actions. I thought that meant the activity that contains them gets their traits but does not assimilate their identity. For example, Sudden Charge is technically not considered a Stride or Strike despite having the traits and properties of both, is it?
|
Act Together doesn't play well with rules regarding 'last action used' or 'next action is'. Those rules for things like Knockdown and Metamagic weren't written with Summoner in mind - mostly because the Summoner class hadn't been written yet.Oh yeah, metamagic is interesting too. If it was read as literally as possible, this would result in the opposite sequence compared to push/knockdown/grab. The metamagic action has to be within the Act Together and be used before the separate Cast a Spell.
So if the GM wants to be an antagonist of the players, then they could indeed rule that the Eidolon's 'last action used' was Act Together, not Strike. Or even that you have to have the Eidolon use their half of Act Together first before the Summoner can take their half - otherwise the 'last action used' was the Summoner's action, not the Eidolon's Strike. And if you try to rearrange your action usage to avoid that by having Act Together be the Summoner's action and the Eidolon's Strike and then have the Eidolon use Knockdown, then the GM can still rule that the 'last action used' was Act Together.Thankfully the order of actions can't be GM bullied in this context. The Knockdown action specifically call for the monster's (eidolon's in this case) last action and doesn't care about anybody else's. Whatever the order, the summoner and eidolon would each have their own individual 'last action used.'
The summoner performs and spends the actions for Act Together, and then you both perform the subordinate actions in tandem, so you could do it the latter way if you want because the eidolon's last action would have been StrikeI think I need a refresher on subordinate actions. I thought that meant the activity that contains them gets their traits but does not assimilate their identity. For example, Sudden Charge is technically not considered a Stride or Strike despite having the traits and properties of both, is it?
For Metamagic use, it would be either Metamagic + Act Together (= Summoner casts a spell and Eidolon gets a single action) or Act Together (= Metamagic and Eidolon gets a single action) and Summoner casts a spell. Which would be bad if the spell is a boost to the Eidolon's action.
I might consider that Act Together just plays identically to the action each character takes within it as far as yhe character is concerned. So Metamagic + Act Together would be OK at my table.