Hi all,
Did anyone also encounter an issue where Temmet matched an Embalmed creature out of nowhere? I haven't killed or discarded anything on his side (bounce only) and yet he embalmed a creature twice. With Anointed Procession, that's some cheating.
The first time it made my game freeze, where I had to quit. He matched a gem that should have triggered something, but the game just kept waiting for something. I could see empty spaces on the board where the gems were that he matched, not replaced yet by new gems. I had to force quit that one.
The second time I was able to beat him, but again he got an Embalmed creature out of nowhere.
Any ideas? Did I miss something or (yet) another bug?
stikxs said: Cards like https://mtgpq.info/cards/WindsOfRebuke will put cards directly in the library which apparently also triggers the embalm w/o the creature having ever been drawn or played. I just found this out tonight myself. If it is the way embalm is "supposed" to work or not I don't know, but it is what it is until D3 does something about it.
Irgy said: stikxs said: Cards like https://mtgpq.info/cards/WindsOfRebuke will put cards directly in the library which apparently also triggers the embalm w/o the creature having ever been drawn or played. I just found this out tonight myself. If it is the way embalm is "supposed" to work or not I don't know, but it is what it is until D3 does something about it. That's the ones I was referring to. It uses the word "destroy", so I can only assume it's the intention. It even matches the behaviour in real MtG, where you can miill yourself to enable your embalm cards (and assorted other graveyard combos). Otherwise what's the point of milling yourself or your opponent anyway?