Various Fandoms: Recent Activity
| Various Fandoms: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics |
Recent updates to Various Fandoms: (Generated at 2024-04-28 08:52:32)
| Various Fandoms: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
| Mechanics |
Recent updates to Various Fandoms: (Generated at 2024-04-28 08:52:32)
See Hanna.
Can only hit nonenchantment permanents. Black normally doesn't get to blow up artifacts, but I made an exception for flavor puporses. Enchantments are less tangible, so I don't know how Killer Queen would touch them to blow them up. Increased p/t from 3/3 to 4/4.
See Emma.
See Demon.
See
I wanted to include stand enchantments. Protection from nonstands was changed to prevent damage from nonstands, which fits more flavorfully. I also added that spirits can damage stands, because we're already having obnoxiously large reminder text, so let's go full flavor.
See Silver Chariot.
Pairing is a requirement and stands having protection from nonstands addeed.
Added in blockers can't be declared
See Silver Chariot.
So from this I gather: A stand is - creatively speaking - an Avatar creature that is manifested by a creature and fights at its side, taking wounds together.
It seems a new card type is unnecesary if you want to create a creature. You want to create something like augment+host except keeping the entities separate.
The simple way would be to change the card type of this accordingly and clean up the reminder text.
Right now, btw, there is no benefit to pairing Silver Chariot with a creature, but some significant drawback.
Proposed reminder text:
> Stand (When this enters the battlefield, you may pair it with an unpaired creature for as long as you control both of them. If either leaves the battlefield, the other is sacrificed.)
It seems appropriate to improve upon soulbonds wording since the condition here is different. Soulbond has a weird order of trigger condition and effect because it allows you to play the creatures in either order, which you don't.
I think "you may" might not be what you are going for flavorwise considering the Aura-analogy, so I would also remove the option.
It remains a drawback keyword, so you are strongly encouraged to use the remaining abilities to create a mechanical tie between the paired creatures. You don't need to go the exact way soulbond does, but at least give the Soul Ripple a reason to choose one creature to stand for than another.
Stand Attempting to understand the concept or flavor without that reference does make this seem nonsensical.
I used soulbond's reminder text as the basis for creating the stand card type. There is no requirement that the creature to which the stand is attached need attack and vice-versa.
So... which definition of "stand" are you going for, because the once that are most resonant are some kind of Last Stand and a location where stuff or people stand. If you are going for the "vehicle" definition as the name implies... there is already a way to represent vehicles. If you go for the "full outfit of a soldier" definition, there is also Equipment. I'm assuming you weren't going for the "colony of bees" definition.
I don't get the flavor you are going for by the choice of words and I don't get the mechanics, because this seems very creature-like and the keyword is extraordinarily banding-like in all the wrong ways. I suppose you could get a lot shorter reminder text out of this if you at least looked at soulbound as a template to work with.
You seem to just want two creatures that attack at the same time and also the card-disadvantage of Auras but without the easy rules.
I'm not certain why a stand has to die with its creature flavor-wise and neither really vice-versa.
Just as a top-down design this seems like a cardname predestined to be a Vehicle artifact.
So depicting a stand was hard to figure out. I originally was going to make an aura could enter combat like a creature, but I didn't think I wanted a Stand to be subject to all the things that affect auras. Also, the necessary requirements in wording were already bulky, so I opted to just give Stand its own card type. A stand is tied to a creature (the stand user, though I expect there'd be extra effort to include that wording). Some stands can engage in combat like creatures, being able to attack, block, and deal damage. Other stands may not engage in combat and would function differently. Whenever a stand is split from the creature that its paired with, the other now-unpaired part is sacrificed.
This doesn't need to mention logia - might as well remove any indestructible no matter the source.
I have sooo much text and so little idea what this actually does.
There is space for reminder text, so it should be there.
Do you think that needs reminder text?
If I ever do make a One Piece set, this may as well be common.