Timing and counter spell

[Raven316]

Situation : I cast {boros charm} and deal 4 damage to player A. In response player B cast {twin cast} copying my spell and targeting me. Player B then plays  a {counter spell} targeting my casting of {boros charm} ...

Q1: can he target my{ boros charm} after he casted a spell?
Q2: what exactly happens in this situation?

[Double-O-Scotch]

It's quite simple really...

Boros charm is cast
Boros charm is copied so there are effectively two Boros charms on the stack.
The first Boros charm is countered.

That's it!

[Raven316]

It's quite simple really...

Boros charm is cast
Boros charm is copied so there are effectively two Boros charms on the stack.
The first Boros charm is countered.

That's it!

Ok thanks ... I always thought that {counter spell} could only be played right after the spell u want to counter

[Double-O-Scotch]

Keep in mind that if the 1st Boros charm resolves, there is no spell to copy, and it can't be countered. It all happens at instant speed to work so watch the timing.

[Raven316]

Keep in mind that if the 1st Boros charm resolves, there is no spell to copy, and it can't be countered. It all happens at instant speed to work so watch the timing.

Ok thanks again

[Kaleo42]

If that is the order he did it the. He doesnt get to copy your spell.

Cast charm
Cast twincast target charm
Cast counter target charm

Resolve
Counter charm
Twincast has no target and fizzels
Charm has been countered

While it is easy to copy and counter, how you do it is important.

[Pleeb]

It doesn't matter in which order he casts his responses because of how the stack works. You cast your damage spell puting it on the stack. He casts his fork puting a copy on the stack. At this point he can let his copy resolve or not then counter your original spell.
If he goes the other way and counters your spell, the counter effect goes on the stack and he can then cast his fork on your original spell before the counter resolves.

[Gorzo]

It does matter. The stack always matters. And Kaleo is correct.

{Twincast} does not create a copy until it resolves, not when Twincast is cast. If Twincast's target is gone by then, no copy can be made, as the target is invalid.

Because the stack resolves top-down, it absolutely matters. If the player casts the Counterspell first, then responds by twin casting the charm before the counter resolves, he will get the copy. But if he does it the other way around (as described with Twincast first), he will not get the copy.

[Kaleo42]

Always got my back even when I halfa$$ my answers. Thanks.

[Pleeb]

It does matter. The stack always matters. And Kaleo is correct.

{Twincast} does not create a copy until it resolves, not when Twincast is cast. If Twincast's target is gone by then, no copy can be made, as the target is invalid.

Because the stack resolves top-down, it absolutely matters. If the player casts the Counterspell first, then responds by twin casting the charm before the counter resolves, he will get the copy. But if he does it the other way around (as described with Twincast first), he will not get the copy.

Totally my bad. I forgot to take onto consideration that the twincast has to resolve, not just have a valid target.