Totally Lost picking one of your own supports and not opponents'

Totally Lost picking one of your own supports and not opponents’

Confused…how did you lose from that?

Totally Lost is doing lots of funky things right now. I’ve had it used on me and never drew the creature that supposedly was sent to the top of my library.

Subtle joke. Well played.

I don’t know whether this is a bug or not - the card text reads “move target creature to the top of your opponent’s library. If you can’t, move a support instead

It can be argued that this legitimately applies to any support, and that were an opponent support intended this would be explicitly stated.

I hardly ever use this, both because of this problem and the excessive mana cost.

MOD NOTE / Moved to Bugs subforum / BK

It doesn’t explicitly state an opponent’s creature either. If this card is working properly then the wording should be altered to be less confusing. If not it should be fixed!

This bug still in 3.6

This bug still in 3.7

This card is a staple for me in mono-blue.
I noticed yesterday, definitely post-3.7, that it was red in my hand while the opponent had no critters nor supports in play.
I had, I think, 2 supports in play and 0 critters…it was early in the match.
Those 2 supports, however, might’ve been Dovin and Kasmina vanguards.
I will have to double-check this later as this thread got me, once again, second guessing myself.
I actually came here to see if there was a thread about giving negative counters to token stacks (Ob Nix’s Cruelty) causing a hard crash…I’ll keep looking for that.

The last malfunction I had with Totally Lost was this one:

Both me and Greg had no creatures in play, and we both had some supports in play. Totally Lost picked one of my supports.

I played Totally Lost yesterday since a very long time in my deck. I cast BSZ, which got me two fully charged Totally Lost cards. My opponent didn’t have any creatures on the board and we both had supports on the board. Both the Totally Lost cards bounced a treasure token that belonged to me.

Hi everyone, I can confirm that this is a currently known issue.