So let's say I have Gonk crew, PtL, and EI.
I can do Gonk action #1 as my normal action.
EI to do the second Gonk action.
Since I did an action, I can Push the Limit to focus.
Receive stress from EI, receive stress from PtL.
This would work this way, right?
Yes, that's the way nested actions work with PtL and EI.
Yes, that's the way nested actions work with PtL and EI.
And this is because receiving the stress from EI/PtL and getting the free action after you've performed an action happen at the same time and you can choose what order they resolve?
Yes, that's the way nested actions work with PtL and EI.
And this is because receiving the stress from EI/PtL and getting the free action after you've performed an action happen at the same time and you can choose what order they resolve?
They work as nested actions:
Take Gonk 1 Action
>Start Experimental Interface from Gonk 1
>Take Gonk 2 Action
>>Start PtL from Gonk 2
>>Take Focus Action
>>End PtL
>>Take Stress from PtL
>End EI
>Take Stress from EI
Yes, that's the way nested actions work with PtL and EI.
And this is because receiving the stress from EI/PtL and getting the free action after you've performed an action happen at the same time and you can choose what order they resolve?
No, the stress comes after the free action. Hence the card text "Then receive 1 stress token."
Using Slugrage's example above, the trigger for EI is "after you perform an action" which is the Gonk 1 action, you trigger EI and immediately get to perform a free action (Gonk 2), which in turn can be a trigger for PtL. So if you trigger PtL, you haven't yet reached the stress condition from EI. So you perform the PtL free action (focus), then get the PtL stress. You've now completed the PtL trigger and stress condition that EI allowed you, so you come right back to receive the stress from EI.
There is no nesting, only triggers and resolving.
...which results in nesting.
...which results in nesting.
No, no nesting! Only choices of what to resolve. Nesting would mean there was a preset order. YOU make the order. It's not computer algorithms!
But whatever. Call it nesting. No stress tokens for me.
...which results in nesting.
No, no nesting! Only choices of what to resolve. Nesting would mean there was a preset order. YOU make the order. It's not computer algorithms!
But whatever. Call it nesting. No stress tokens for me.
Actually the easiest way to explain it, is to liken it to a computer program's sub-routine. You get part way through action 1 and trigger action 2, so you leave action 1 to resolve action 2, then return to the point you left action 1 and finish resolving it. So there is an order, because you can only resolve one thing at a time.
Also, you do in fact have to finish resolving all the things triggered by the first thing a card tells you to do before you move on to the second thing a card tells you to do. Nesting.
(I may be stating as fact something that is still theoretical, here, but I think my position is defensible.)
...which results in nesting.
No, no nesting! Only choices of what to resolve. Nesting would mean there was a preset order. YOU make the order. It's not computer algorithms!
But whatever. Call it nesting. No stress tokens for me.
I'm a programmer by trade. It's absolutely like a computer algorithm. Here's some (really bad) pseudocode that shows the nesting and how you can resolve three actions and receive 2 stress without breaking any rules.
DoAction()
if (PTL.Triggered)
{
DoAction();
if (EI.Triggered)
{
DoAction();
ReceiveStress();
}
ReceiveStress();
}
else if (EI.Triggered)
{
DoAction();
if (PTL.Triggered)
{
DoAction();
ReceiveStress();
}
ReceiveStress();
}
I'm a programmer by trade. It's absolutely like a computer algorithm. Here's some (really bad) pseudocode that shows the nesting and how you can resolve three actions and receive 2 stress without breaking any rules....which results in nesting.
No, no nesting! Only choices of what to resolve. Nesting would mean there was a preset order. YOU make the order. It's not computer algorithms!
But whatever. Call it nesting. No stress tokens for me.
DoAction() if (PTL.Triggered) { DoAction(); if (EI.Triggered) { DoAction(); ReceiveStress(); } ReceiveStress(); } else if (EI.Triggered) { DoAction(); if (PTL.Triggered) { DoAction(); ReceiveStress(); } ReceiveStress(); }
Noooooo!!!! No code!!!!!
Ahem, anyway.
I was being only half serious, of course. My intent was to show that it's not mandatory to perform actions and such in a nested manner, and resolve triggers in a 'wrong' way, like taking the stress from PTL before you used EI. Why anyone would want to do this is just silly.
Like I said, anyway.
(Always contrary...I need to not do that as much)
You're making no sense. Everyone else has the right of it.
I was being only half serious, of course. My intent was to show that it's not mandatory to perform actions and such in a nested manner, and resolve triggers in a 'wrong' way, like taking the stress from PTL before you used EI. Why anyone would want to do this is just silly.
Like I said, anyway.
(Always contrary...I need to not do that as much)
Oh, I see what you're doing. I just disagree. A card that tells you to do one thing and then do another thing is not describing an event and another event that is triggered by the first event. You're right that most of the time it doesn't matter, but if it is as you say then Kanan Jarrus (crew) would be able to clear the stress from Daredevil.