Lightning Bolt vs. Reflection

By Delkondros, in Talisman Rules Questions

I posted this on the support page as well...I'm a newbie so please be patient with me if that was not the right thing to do.

Player A casts Lightning Bolt on Player B at the beginning of Player B's turn. Player B casts Reflection on Player A. Is this allowed? According to the text of the LB Spell, that character is stunned (may do nothing apart from negating this Spell with Counterspell) for the duration of that turn. I think that since Counterspell is capitalized in the text, then only that spell can be used to negate LB. However, Reflection does say any spell that has just been cast is turned back onto that character. What is the proper resolution for this circumstance?

Delkondros said:

I posted this on the support page as well...I'm a newbie so please be patient with me if that was not the right thing to do.

Player A casts Lightning Bolt on Player B at the beginning of Player B's turn. Player B casts Reflection on Player A. Is this allowed? According to the text of the LB Spell, that character is stunned (may do nothing apart from negating this Spell with Counterspell) for the duration of that turn. I think that since Counterspell is capitalized in the text, then only that spell can be used to negate LB. However, Reflection does say any spell that has just been cast is turned back onto that character. What is the proper resolution for this circumstance?

In terms of timing, Reflection works exactly as Counterspell and it's not mentioned in other cards only because it's an expansion Spell Card.

The Lightning Bolt is reflected onto the caster (player A) who can only cast a Counterspell if able. If he's stunned, he can do anything for the duration of that turn, which in most cases has no effect on the game since he will take is next turn as normal. The strange thing happens only if the stunned Character is attacked during that turn; he can't do nothing, including engaging a battle, so he can't be attacked either. Strange situation that should receive a FAQ entry, IMO.