To my understanding, Defensiveness is supposed to trigger the instant you try to cast a spell. Its function could nullify the spell, saving the enemy the bother of trying to Block it. But I was standing in melee range to an Ogre Magicker and I saw this: BATTLE LOG: Player=Gary,Scenario=Pass Lookouts,Room=PASS (Sir Knight),RoomID=153147,Event=PlayAction,Action=Powerful Spark,Instigator=Cloudspell,Targets=Paragon BATTLE LOG: Player=Gary,Scenario=Pass Lookouts,Room=PASS (Sir Knight),RoomID=153147,Event=TriggerFail,Trigger=Unreliable Block,TriggeringActor=Paragon,AffectedActors=Paragon,TriggerType=Action,TriggerLocation=Hand BATTLE LOG: Player=Gary,Scenario=Pass Lookouts,Room=PASS (Sir Knight),RoomID=153147,Event=TriggerSucceed,Trigger=Defensiveness,TriggeringActor=Cloudspell,AffectedActors=,TriggerType=Action,TriggerLocation=ActorAttachment BATTLE LOG: Scenario=Pass Lookouts,Room=PASS (Sir Knight),RoomID=153147,Msg=Powerful Spark was cancelled. BATTLE LOG: Scenario=Pass Lookouts,Room=PASS (Sir Knight),RoomID=153147,Msg=The active player is now Sir Knight Sure, Defensiveness saved me from a Powerful Spark, but AFTER checking my Unreliable Block. Is this a side effect of changing to a "Saving Roll" mechanic?
It's actually a consequence of the way we order trigger checks. All cards in hand are checked first, then all attached cards.
So, I think the way we were doing the trigger checking was wrong. It was: - For each player, starting with the current one, for each group, check all cards in hand. - For each player, for each group, check all character attachments - Check all terrain attachments. This means that, as you noted, Defensiveness triggers after a block, since the block is in hand and Defensiveness is an attachment. I've re-ordered this to: - For each player, for each group, check all cards in hand and then all cards attached to members of that group. - Check all terrain attachments. I believe this is the correct order - it got messed up when I fixed the ordering of the terrain attachment checking.
