- \n
- This simple question had an equally simple answer, that being \u201cno you can\u2019t\u201d because among the other things protection does, it stops a card from being targeted by spells and Vindicate specifically says \u201ctarget\u201d on it.<\/span><\/li>\n<\/ul>\n
![\"Council\"](\"http:\/\/blogs.magicjudges.org\/greatlakes\/files\/2017\/01\/Council-210x300.jpg\")
<\/a>Having established that, we moved onto the less obvious question; can you vote for, and subsequently kill a Progenitus<\/a> with Council\u2019s Judgement?<\/p>\n- \n
- While the normal use of Council\u2019s Judgement is fairly similar to Vindicate<\/a>, the wording is very important here. Because Judgement doesn\u2019t specifically use the word \u201ctarget\u201d it is unaffected by abilities like Protection\/Hexproof\/Shroud which all care about the word \u201ctarget\u201d specifically.<\/span><\/li>\n<\/ul>\n
Next up we talked about how Targeting vs Choosing make a difference in being able to respond to things. We started with asking, can the activated ability of Spectral Searchlight<\/a> could be responded to?<\/p>\n
- \n
- Because Spectral Searchlight uses the word choose, it still qualifies as a mana ability, which means that it can not be responded to. Contrast this to Witch Engine<\/a> which does say \u201ctarget\u201d in its ability and as such does not qualify as a mana ability. Because of this it can both be responded to and the choice to player for its ability will be known before it resolves.<\/span><\/li>\n<\/ul>\n
In the same vein of when choices are made vs when targets are declared, we looked at the card Abzan Advantage<\/a>. I asked what happens when a player casts it saying what they like to bolster onto ahead of time, and then the opponent kills that creature with Abzan Advantage still on the stack?<\/p>\n
- \n
- Luckily for our Abzan Advantage player, Bolster uses the choose wording and not target. As such, any decisions are made on resolution, so when the spell resolves they can bolster onto a different creature, assuming they still have one. In this scenario the player casting Advantage was slightly out of sequence in declaring a creature for Bolster, and while this is a fairly common play pattern for players, the difference is key when these situations come up in how we handle them.<\/span><\/li>\n<\/ul>\n
Our last question of the day delved into the IPG for a bit. I asked how we would handle a player who cast Council\u2019s Judgement saying \u201ckill your Batterskull<\/a>\u201d and then upon confirmation of the spell\u2019s resolution from the opponent says \u201cOk I vote for your Jace, the Mind Sculptor<\/a>.\u201d In this scenario what rule, if any had been broken? And more importantly, what was the appropriate board state to arrive at?<\/p>\n
- \n
- For starters every agreed that we would hold the player casting Council\u2019s Judgement to their original choice and kill the Batterskull. While targeted cards require announcement and locking in on casting, choices are made on resolution. Because of this there is some room for abuse in wording, and as such there is a specific shortcut in MTR 4.1 that covers announcing a choice that would be made later when casting a spell or activating an ability. Announcing a spell in the way our player did is proposing a shortcut that they skip to the resolution of that spell with the choice announced, and as such we hold them to that unless the opponent responds, which they didn\u2019t in this case. <\/span><\/li>\n
- There was much more discussion that occurred regarding if a penalty should be given here. However, for shortcut violations like this, policy does not support any penalty unless we are looking into cheating (which is possible given that one play definitely seemed to be trying to break shortcut rules to gain an advantage over their opponent). However, assuming no malice, there is no penalty for trying to go against a shortcut you already announced, you just don’t get to do that and the game moves on.<\/span><\/li>\n<\/ul>\n
- For starters every agreed that we would hold the player casting Council\u2019s Judgement to their original choice and kill the Batterskull. While targeted cards require announcement and locking in on casting, choices are made on resolution. Because of this there is some room for abuse in wording, and as such there is a specific shortcut in MTR 4.1 that covers announcing a choice that would be made later when casting a spell or activating an ability. Announcing a spell in the way our player did is proposing a shortcut that they skip to the resolution of that spell with the choice announced, and as such we hold them to that unless the opponent responds, which they didn\u2019t in this case. <\/span><\/li>\n
- Luckily for our Abzan Advantage player, Bolster uses the choose wording and not target. As such, any decisions are made on resolution, so when the spell resolves they can bolster onto a different creature, assuming they still have one. In this scenario the player casting Advantage was slightly out of sequence in declaring a creature for Bolster, and while this is a fairly common play pattern for players, the difference is key when these situations come up in how we handle them.<\/span><\/li>\n<\/ul>\n
- Because Spectral Searchlight uses the word choose, it still qualifies as a mana ability, which means that it can not be responded to. Contrast this to Witch Engine<\/a> which does say \u201ctarget\u201d in its ability and as such does not qualify as a mana ability. Because of this it can both be responded to and the choice to player for its ability will be known before it resolves.<\/span><\/li>\n<\/ul>\n
- While the normal use of Council\u2019s Judgement is fairly similar to Vindicate<\/a>, the wording is very important here. Because Judgement doesn\u2019t specifically use the word \u201ctarget\u201d it is unaffected by abilities like Protection\/Hexproof\/Shroud which all care about the word \u201ctarget\u201d specifically.<\/span><\/li>\n<\/ul>\n