False Transcendence | False Ascension

[ZephyrPhantom]

NAME: False Transcendence ELEMENT: Darkness COST: 8  TYPE: Spell ATK|HP: TEXT: Target creature gains immaterial and switches sides for 3 turns.	NAME: False Ascension ELEMENT: Darkness COST: 6  TYPE: Spell ATK|HP: TEXT: Target creature gains immaterial and switches sides for 3 turns.

ART: http://www.sxc.hu/photo/1089934 IDEA: Zblader NOTES: A solution to the problematic Immolation + Mind Control combination that usually shoots down Mind Control cards, as well as bringing a trick of it's own to the table - you can't Cremate a creature that's immaterial, but you can "gift" an antimattered creature to your opponent - or perhaps you'll want to steal a creature that will get you the last bit of damage for the victory. Immaterial stays on the creature even after it goes back to it's owner. If the player's field is full, the creature will keep trying to go back until something dies (alternatively it could kill the creature in the last slot and replace it, but I dislike that suggestion due to instakill.) Vs. Antimatter + Antimatter has the potential to permanently negate two creatures - the one that's healing you and another one to negate that healing. - Counterable by Immolation and quick CC such as Reverse Time. Vs. Parallel Universe + Parallel Universe is cheaper and still allows you to buff the creature - useful if you've copied a creature that relies on other cards like a Scorpion or Wyrm. You don't loose the creature 3 turns later. Also costs 1 less quantum. - Opponent doesn't lose his creature. SERIES:

[ZephyrPhantom]

Bump, feedback appreciated.

[Pineapple]

It's too expensive. Counters are cheaper than the cards they counter, and this really isn't that good of a counter in the first place. I'd drop it as low as 4/3 since it just borrows a creature for 2 out of 4 turns. (I assume the switching occurs right after the creature attacks, not when you use the card on the creature.)

Nvm, didn't take the fact that it's also like a 2-turn delay/freeze. What happens if the opponent's field is full when your creature is supposed to move to your opponent's side?

[ZephyrPhantom]

It's too expensive. Counters are cheaper than the cards they counter, and this really isn't that good of a counter in the first place. I'd drop it as low as 4/3 since it just borrows a creature for 2 out of 4 turns. (I assume the switching occurs right after the creature attacks, not when you use the card on the creature.)

Nvm, didn't take the fact that it's also like a 2-turn delay/freeze. What happens if the opponent's field is full when your creature is supposed to move to your opponent's side?

Creature doesn't move at all if the other field is full - it will stay on it's original side.

[Nepycros]

It's too expensive. Counters are cheaper than the cards they counter, and this really isn't that good of a counter in the first place. I'd drop it as low as 4/3 since it just borrows a creature for 2 out of 4 turns. (I assume the switching occurs right after the creature attacks, not when you use the card on the creature.)

Nvm, didn't take the fact that it's also like a 2-turn delay/freeze. What happens if the opponent's field is full when your creature is supposed to move to your opponent's side?

Creature doesn't move at all if the other field is full - it will stay on it's original side.

And what happens to the creature if it's on vacation to the opponent's field, and your field becomes occupied in the meantime? I for one would be terrified seeing this in an Aflatoxin deck.

[Pineapple]

@Nepycros: Same thing, I suppose. And yes, the card being paired with intentionally clogged field is exactly why I brought up the question >: P

[ZephyrPhantom]

And... that's worse than Aflatoxin + Antimattered creatures?

If your field becomes occupied in the meantime prior to return, I would think that there could be three different ways of using the clogged return method:
1) Creature dies.
2) Creature stays.
3) Creature keeps trying to go back until something dies.

I like 3 the best but it may be hard to code.

[AngeDeMort]

If your field becomes occupied in the meantime prior to return, I would think that there could be three different ways of using the clogged return method:
1) Creature dies.
2) Creature stays.
3) Creature keeps trying to go back until something dies.

I like 3 the best but it may be hard to code.

what if it killed the creature occupying the slot?

[ZephyrPhantom]

If your field becomes occupied in the meantime prior to return, I would think that there could be three different ways of using the clogged return method:
1) Creature dies.
2) Creature stays.
3) Creature keeps trying to go back until something dies.

I like 3 the best but it may be hard to code.

what if it killed the creature occupying the slot?

That could work, although that would make this card an instakill card.

[ZephyrPhantom]

Bump due to Crucible submission and for additional feedback.

[Rutarete]

IMO cost seems a bit high. I think 7 | 5 would work