Teferi’s first ability does not work correctly. The bouncing working differently for the player than the AI (mainly tokens and ghalta).
@Mark_Tedin Can you describe what’s happening when you use this ability as opposed to what you are seeing when the opponent uses the ability?
I’ve noticed sometimes it won’t work at all even with valid targets and with my opponent have 5 (or fewer) cards in hand. Its almost like i can only use it once per battle per something?
At the last event, Teferi returned my topters and my ghalta to my hand. However I can not do the same against the opponent.
Yes. I tested it now. The ability does not work when the opponent´s hand is full.
I mean, technically it shouldn’t work if the opponent’s hand is full. But then again, none of the bounce should work if your opponent’s hand is full (except the ones that specifically say that they do), but many of them do. So IDK.
@Brigby What I’ve seen so far:
PLAYER Teferi
-
Cannot return certain tokens to hand no matter what
-
Can only return creatures while enemy has 5 or fewer cards in hands
AI Teferi -
Can return any token
-
If you have 6+ cards in hand, it will destroy the targeted creature instead, like newer bounce spells
Though, also check with above users if they were playing the latest Journey Through History event, as that one has the permanent support that blocks PW abilities.
@Mark_Tedin Can you describe what’s happening when you use this ability as opposed to what you are seeing when the opponent uses the ability?
Here is a topic I made regarding this yesterday in General as we are unaware if the behavior of his first ability is actually a bug or if some of it is intended.
https://forums.505go.com/discussion/74103/teferi-spiraling-time-bug-or-feature
@Brigby What I’ve seen so far:
PLAYER Teferi
Cannot return certain tokens to hand no matter what
Can only return creatures while enemy has 5 or fewer cards in hands
AI TeferiCan return any token
If you have 6+ cards in hand, it will destroy the targeted creature instead, like newer bounce spells
I have observed exactly this
Thanks for the input everyone. I’m passing this along to the team for review.
I know this is an old thread, but I have observed this behavior recently as well.
I thought it was patched out but, it started happening again.
I thought it was patched out but, it started happening again.
Would you mind clarifying which issue specifically is occurring again?
