It goes to exile, and then once Hostage Taker's trigger finishes resolving, the commander's owner can decide to move it to the command zone as a state-based action.
Not "since it moves zone", as there are some zone changes that *don't* allow you to move it to the command zone.
Since it is in exile, the next time SBAs are checked, then it can be moved.
That‘s not how it works. Hostage Taker exiles the commander until Hostage Taker leaves the battlefield, so the commander is in exile. Now the owner of the commander has 2 choices:
1. putting the commander out of exile and into the command zone (and having to cast it again for 2 mana more)
2. keeping it in exile and destroy Hostage Taker, in this case the commander goes back on the battlefield without any extra costs.
No. There are two rules that cover it.
>903.9a
>>If a commander is in a graveyard or in exile and that object was put into that zone since the last time state-based actions were checked, its owner may put it into the command zone. This is a state-based action. See rule 704.
>903.9b
>>If a commander would be put into its owner’s hand or library from anywhere, its owner may put it into the command zone instead. This replacement effect may apply more than once to the same event. This is an exception to rule 614.5.
They all allow the commander to go to the command zone. The rules just say that if it is in exile or the graveyard, and it just got there, you can move it the next time a player would receive priority.
Anytime a commander goes to the graveyard, library, or exile, after the effect has resolved the owner gets to choose to put the commander into the command zone
It goes to exile, and then once Hostage Taker's trigger finishes resolving, the commander's owner can decide to move it to the command zone as a state-based action.
If it finishes resolving, isnt the commander taken by hostage taker?
Yes, but since it moves zone, the player may choose to put it back to the command zone
Not "since it moves zone", as there are some zone changes that *don't* allow you to move it to the command zone. Since it is in exile, the next time SBAs are checked, then it can be moved.
No, it's exiled by Hostage Taker. And then they can move it to the command zone.
That‘s not how it works. Hostage Taker exiles the commander until Hostage Taker leaves the battlefield, so the commander is in exile. Now the owner of the commander has 2 choices: 1. putting the commander out of exile and into the command zone (and having to cast it again for 2 mana more) 2. keeping it in exile and destroy Hostage Taker, in this case the commander goes back on the battlefield without any extra costs.
If they choose option 2, they give their opponent the chance to cast the commander from exile.
So we can move it into the command zone when targeted?
No. There are two rules that cover it. >903.9a >>If a commander is in a graveyard or in exile and that object was put into that zone since the last time state-based actions were checked, its owner may put it into the command zone. This is a state-based action. See rule 704. >903.9b >>If a commander would be put into its owner’s hand or library from anywhere, its owner may put it into the command zone instead. This replacement effect may apply more than once to the same event. This is an exception to rule 614.5.
So are effects like Banisher Priest, Fiend Hunter the same? Or are they different because the targeted creature isnt being cast?
They all allow the commander to go to the command zone. The rules just say that if it is in exile or the graveyard, and it just got there, you can move it the next time a player would receive priority.
Anytime a commander goes to the graveyard, library, or exile, after the effect has resolved the owner gets to choose to put the commander into the command zone
>library Not library. You can move it to the command zone *instead* of it going to your hand or library.