So a surprising card interaction occurred to me last night. Here's the situation: A targaryen player has flipped Threat from the North and plays Flame Kissed on a Stark unique character… say Robb Stark. So normally this results in Robb being killed or discarded (can't be saved). The first player chooses for him to die, the Stark player plays Rhymes with Meek to save him from the kill, thus preventing the strength reduction from discarding him.
Do I have that right?
Cwethan said:
So a surprising card interaction occurred to me last night. Here's the situation: A targaryen player has flipped Threat from the North and plays Flame Kissed on a Stark unique character… say Robb Stark. So normally this results in Robb being killed or discarded (can't be saved). The first player chooses for him to die, the Stark player plays Rhymes with Meek to save him from the kill, thus preventing the strength reduction from discarding him.
Do I have that right?
As long as it's not cancelled, almost. Once it attaches, Robb gains "cannot have… strength raised or lowered," which brings his STR up to his printed value. Plus, this prevents Flame Kissed from even being relevant, since it has the stipulation of there being no other attachments on the character.
If he's above 0 STR, the "discard at 0" effect that used to apply will not be able to discard him, either. Since the First Player chose the "kill at 0" to go first, the "discard at 0" had not initiated yet. By the time it would get a change to initiate, its play restrictions are not met because the character is no longer 0 STR.