Uh. That's indeed a problem.
I think this trick (quite ugly, admittedly) may work? This way, it enters as a 0/1, the soulbond "when this enters" trigger can be allowed to resolve, then this becomes a -7/-7 when it is already (possibly) paired
I think there's a mechanical problem here. Soulbond's nested rulings begin with "When this creature enters, ..." - notably not "As this creature enters, ...", meaning that this would as is this die to state-based actions before it could ever get that +10/+10 from the soulbond ability.
typo
cost w->1w
Uh. That's indeed a problem. I think this trick (quite ugly, admittedly) may work? This way, it enters as a 0/1, the soulbond "when this enters" trigger can be allowed to resolve, then this becomes a -7/-7 when it is already (possibly) paired
Used to be -7/-7; reworked in such a way that it can survive until the soulbond trigger resolves.
I think there's a mechanical problem here. Soulbond's nested rulings begin with "When this creature enters, ..." - notably not "As this creature enters, ...", meaning that this would as is this die to state-based actions before it could ever get that +10/+10 from the soulbond ability.
changed name
spelling
That's fair; added a clause to make the process essentially ignore lands
added the clause "If it is a land, put it in your graveyard"
Rebound is a may. This is specifically designed to force being cast again, as a drawback
You misspelled "rebound" as "oath".
I feel lands skew the viability of the two options too much and there needs to be a further distinction for land/nonland.