21:30 - You attack with at least 1 Pirate and 1 Vehicle speciically, the trigger goes off. Your opponent responds by exiling your Vehicle. That spell is resolved, the Vehicle gets exiled, Swashbuckler's trigger than goes to check to see if it's able to resolve. It checks and only sees 1 Pirate attacking and cannot resolve this spell. If the trigger was worded "whenever YOU attack", things would be different. Swashbuckler's trigger cannot "remember" the Vehicle was declared attacking, once it's its turn, it double-checks to see who is declared attacking and there is just a lone Pirate attacking. That's how I see it.
I am quite familiar with the rules, and it seems a bug to me: there's no need for this trigger to be false when it checks on resolution, as the condition is still true. MtG cards can and do remember plenty of stuff that has left the board. I also don't quite get what you mean by "if the trigger was worded *whenever you attack* ", as that's exactly how it's worded.
@@mrknarf4438 How is the condition true? The trigger checks on resolution after a one whole total creature was exiled right before... and it sees two attacking creatures? OK.
@@mrknarf4438 bro, you're wrong... it's fine. don't be all mtg try-hard about this... the trigger checks after 1/2 creatures was exiled... and sees 2/2 creatures. That makes no sense, man.
im not convinced that's how it works. could very well just be a bug. but im not a judge so, i really dont know, but i dont think you should be making speculation when you dont know how it works either
Because of the if clause inside the ability, it checks for the “has attacked” state in the middle of resolving the ability, allowing your opponent’s removal to fizzle the ability
That doesn't seem right to me. If it were worded something like "If a Pirate and a Vehicle each attacked this turn...", then your explanation would make sense: the game looks for currently-living creatures and asks them if they attacked. But as written, I think "If you attacked with..." refers to creatures declared as attackers during the Declare Attackers step, not creatures currently attacking.
I agree with Alan, looks like a bug to me. It should trigger as soon as you declare attackers, which wouldn’t give the opponent a chance to react and stop the effect at that point
Yeap, it’s bugged. Because of the way arena is coded (it directly reads the text off the cards) it might have gotten confused and forgot to trigger. In the past, fiery cannonade would be uncastable without a pirate on board due to the wording.
Can you explain in further detail how the opponent would be forbidden to respond to this trigger? There is a HUGE difference between "giving a chance" to "you literally cannot stop it". EX: Most Valuable Slayer. You could target the creature MVS targeted and what happens? Trigger goes off but there is no creature. It's not like the creature "still got First Strike for a split second". If you kill MVS instead, the trigger still goes off and checks to see if it's still able to resolve. MVS being dead isn't crucial to the spell resolving. Now, imo, it says you need both a Pirate AND a Vehicle, specifically. Not two Pirates, two vehicles... in order for this spell to resolve you NEED A PIRATE AND A VEHICLE ON THE BATTLEFIELD WHEN THE TRIGGER CHECKS. The card is working as intended.
My son's name is Mako, named after the shark. We pronounce it like 'may-ko'
That's a really cool name.
No hate but glad someone said it 😂
I think you overlooked the shark pirate 5 drop many times. It has a loot actived ability that would be great in your deck specifically.
21:30 - You attack with at least 1 Pirate and 1 Vehicle speciically, the trigger goes off. Your opponent responds by exiling your Vehicle. That spell is resolved, the Vehicle gets exiled, Swashbuckler's trigger than goes to check to see if it's able to resolve. It checks and only sees 1 Pirate attacking and cannot resolve this spell. If the trigger was worded "whenever YOU attack", things would be different. Swashbuckler's trigger cannot "remember" the Vehicle was declared attacking, once it's its turn, it double-checks to see who is declared attacking and there is just a lone Pirate attacking. That's how I see it.
came here to see the "why" for that. thanks!
I am quite familiar with the rules, and it seems a bug to me: there's no need for this trigger to be false when it checks on resolution, as the condition is still true. MtG cards can and do remember plenty of stuff that has left the board.
I also don't quite get what you mean by "if the trigger was worded *whenever you attack* ", as that's exactly how it's worded.
@@mrknarf4438 How is the condition true? The trigger checks on resolution after a one whole total creature was exiled right before... and it sees two attacking creatures? OK.
@@mrknarf4438 bro, you're wrong... it's fine. don't be all mtg try-hard about this... the trigger checks after 1/2 creatures was exiled... and sees 2/2 creatures. That makes no sense, man.
im not convinced that's how it works. could very well just be a bug. but im not a judge so, i really dont know, but i dont think you should be making speculation when you dont know how it works either
Hell yeah finally some new draft
when and whenever, that's hilarious glad I learned this watching the video!
Etymology is Maori, so would originally be "Mah-Ko", however in English, it's "May-ko" anyhow.
It’s mako, like cake, yo!
Yep. May-koe
either the swashbuckler is bugged or its required that both cards triggering the effect still on board when combat ends
Im hoping this helps my greasefang deck in brawl
Does a not have attacked until damage is dealt?
Mawko, polo
Because of the if clause inside the ability, it checks for the “has attacked” state in the middle of resolving the ability, allowing your opponent’s removal to fizzle the ability
That doesn't seem right to me. If it were worded something like "If a Pirate and a Vehicle each attacked this turn...", then your explanation would make sense: the game looks for currently-living creatures and asks them if they attacked. But as written, I think "If you attacked with..." refers to creatures declared as attackers during the Declare Attackers step, not creatures currently attacking.
I agree with Alan, looks like a bug to me. It should trigger as soon as you declare attackers, which wouldn’t give the opponent a chance to react and stop the effect at that point
Yeap, it’s bugged.
Because of the way arena is coded (it directly reads the text off the cards) it might have gotten confused and forgot to trigger.
In the past, fiery cannonade would be uncastable without a pirate on board due to the wording.
Can you explain in further detail how the opponent would be forbidden to respond to this trigger? There is a HUGE difference between "giving a chance" to "you literally cannot stop it". EX: Most Valuable Slayer. You could target the creature MVS targeted and what happens? Trigger goes off but there is no creature. It's not like the creature "still got First Strike for a split second". If you kill MVS instead, the trigger still goes off and checks to see if it's still able to resolve. MVS being dead isn't crucial to the spell resolving.
Now, imo, it says you need both a Pirate AND a Vehicle, specifically. Not two Pirates, two vehicles... in order for this spell to resolve you NEED A PIRATE AND A VEHICLE ON THE BATTLEFIELD WHEN THE TRIGGER CHECKS.
The card is working as intended.
@@nickh4519Agreed, this is a bug
Guess I’ll get mythiced 😂😂😂😂
Mawko lol
Very first game broke arena haha
Its may-koe
Shark w pointy nose and creepy eyes
Not how it's pronounced in the original Māori.
@Tylerb7 thanks dude 😎😎😎