Program Malfunction and Chester Wars

By tuggs, in UFS Rules Q & A

Hypothetical: I try to use Program Malfunction to pin down my opponent's Chester's Backing, and they respond by committing that same Chester's Backing to cancel the ability. I then respond with my own Chester's Backing to cancel the ability on their Chester's Backing. What happens?

Does my Chester's Backing successfully cancel theirs, and allow Program Malfunction's ability to continue?

Or is my opponent's Chester's Backing no longer a valid target for Program Malfunction at this point, because it is now committed?

Thanks in advance.

-Tuggs

no longer a valid target, since you define your target after the negated negation resolves chesters cant be commited with your effect.

choose another target

Ziephnir said:

no longer a valid target, since you define your target after the negated negation resolves chesters cant be commited with your effect.

choose another target

*STAMP*

you "F Commit"

stop

they "R Commit"

stop

you "R Commit"

no R? continue, resolve the effects, cancelling their R, and allowing your F to go through. now resolve Program Malfunction.

To put it simply, Program Malfunction has the specific text "committed by this ability" then you ask yourself, was chesters committed by this ability? No because it committed itself in response. You do not choose a new target either it just tries to resolve and does nothing but was already committed for cost.

FenMiHuo said:

To put it simply, Program Malfunction has the specific text "committed by this ability" then you ask yourself, was chesters committed by this ability? No because it committed itself in response. You do not choose a new target either it just tries to resolve and does nothing but was already committed for cost.

Not exactly.

You pay the cost for an ability. In the case of Program Malfunction, its just "F: Commit:" THEN it is negated. The "target" is not chosen until the ability begins to resolve. At this point it is too late to Chesters it. Chesters is a response to the ability being PLAYED, not resolved.

It works like this.

You announced an ability, and pay all costs. Ability is then played and "after an ability is played" window triggers (this is the one for CB)

Once the window is closed, the ability resolves.

Basically it comes down to the "commit a foundation in your opp. staging area" being after the colon. If it was before, then it would already be "chosen".

Hope that helps and doesnt just add more confusion

Stamp for Mr. Mazzurco.

Very important fact about UFS. You declare targets and the resolution path when the ability RESOLVES, not when it is played.