Originally posted by Bartłomiej Wieszok:NAP had open mana and one card in hand which is a land. AP just crewed Copter then attacked, then NAP said OK so AP cut his life. There are no more verbal exchange about what step it was.
Edited Harm Tacoma (Dec. 2, 2016 03:05:22 AM)
Originally posted by Gareth Tanner:
The NAP player can't dictate the pace of the game, in this situation due to there being a trigger on the stack it doesn't matter what the NAP meant with “OK”, even if they mean “I have no response and no desire to block and would like to move to combat damage” it can't mean that due to the trigger on the stack. I don't think it's reasonable to say that the damage and loot isn't in a single block here, we go from NAP passing priority in Declare Attackers with a trigger on the stack to after combat damage the player looting and damage being dealt, I personally ask NAP do they have a response, if yes back up the damage and let them respond but otherwise I'd leave the game as it is.
Originally posted by MTR:d:^D
An out-of-order sequence must not result in a player prematurely gaining information which could reasonably affect decisions made later in that sequence.
Originally posted by Scott Marshall:
It can be argued that, by learning that NAP not only won't block, but that he has nothing to prevent the damage, AP has gained strategic information that could influence his looting.
Originally posted by Isaac King:
NAP isn't allowed to progress the game state too far and make AP miss his trigger.
Originally posted by Isaac King:
By saying “OK”, NAP has allowed the trigger to resolve. AP took it a little further and assumed that the damage would occur as well, so he did the physical actions out of order. I don't see any information gained here.
Originally posted by AIPG/MTR:Knowing there's no blockers could reasonably affect decisions made during looting.
An out-of-order sequence must not result in a player prematurely gaining information which could reasonably affect decisions made later in that sequence.
Replies have been disabled because this topic is closed.