Seifer, Balamb Rival

two generic mana one black mana one red mana Legendary Creature — Human MercenaryPower and toughness4/3

First strike

Whenever you attack a player, goad target creature that player controls.

Whenever a creature attacking one of your opponents becomes blocked by two or more creatures, that attacking creature gains deathtouch until end of turn.

Add to list Build a deck around it

Showing Final Fantasy Commander#451

Price

3.18 $

Foil 2.29 $

1 printing

Daily estimate from Scryfall, not a shop quote.

View onScryfall EDHREC

Buy this printingTCGplayer Cardmarket Cardhoarder

Seifer, Balamb Rival rulings

2025-10-02
If, during a player's declare attackers step, a creature that player controls that's been goaded is tapped, is affected by a spell or ability that says it can't attack, or hasn't been under that player's control continuously since the turn began (and doesn't have haste), then it doesn't attack. If there's a cost associated with having a creature attack a player, its controller isn't forced to pay that cost, so it doesn't have to attack that player.
2025-10-02
If a creature you control has been goaded by multiple opponents, it must attack one of your opponents that hasn't goaded it, as that fulfills the maximum number of goad requirements. If a creature you control has been goaded by each of your opponents, the creature must attack an opponent (rather than a planeswalker or battle), but you choose which opponent it attacks.
2025-10-02
Being goaded isn't an ability the creature has. Once it's been goaded, it must attack as detailed above even if it loses all abilities.
2025-10-02
Attacking with a goaded creature doesn't cause it to stop being goaded. If there is an additional combat phase that turn, or if another player gains control of it before it stops being goaded, it must attack again if able.
2025-10-02
Once Seifer's last ability has triggered, it doesn't matter what happens to the blocking creatures. The creature will keep deathtouch even if one or more of the creatures blocking it are removed from combat or leave the battlefield.
2025-10-02
If the creature doesn't meet any of the above exceptions and can attack, it must attack a player other than the controller of the spell or ability that goaded it if able. If the creature can't attack any of those players but could otherwise attack, it must attack a planeswalker an opponent controls, a battle an opponent protects, or the player that goaded it.
2025-10-02
Seifer's last ability triggers regardless of which player controls the attacking creatures.

Seifer, Balamb Rival keyword rules

Goad Rule 701.38

Certain spells and abilities can goad a creature. Until the next turn of the controller of that spell or ability, that creature is goaded.

Goaded is a designation a permanent can have. A goaded creature attacks each combat if able and attacks a player other than the controller of the permanent, spell, or ability that caused it to be goaded if able. Goaded is neither an ability nor part of the permanent’s copiable values.

A creature can be goaded by multiple players. Doing so creates additional combat requirements.

Once a player has goaded a creature, the same player goading it again has no effect. Doing so doesn’t create additional combat requirements.

First strike Rule 702.7

First strike is a static ability that modifies the rules for the combat damage step. (See rule , “Combat Damage Step.”)

If at least one attacking or blocking creature has first strike or double strike (see rule ) as the combat damage step begins, the only creatures that assign combat damage in that step are those with first strike or double strike. After that step, instead of proceeding to the end of combat step, the phase gets a second combat damage step. The only creatures that assign combat damage in that step are the remaining attackers and blockers that had neither first strike nor double strike as the first combat damage step began, as well as the remaining attackers and blockers that currently have double strike. After that step, the phase proceeds to the end of combat step.

Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won’t preclude that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won’t allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).

Multiple instances of first strike on the same creature are redundant.