auto={C(-0/-1,1)}:all(this) Add{G} limit:1
other wise it parsed as a non=activated ability, don't worry tho, i change activated manaproducers a long time ago so that they dont use the stack, so all this will do is enable using "limit:"...
Angelic Chorus
Lavaborn Muse
Pestilence
Living Artifact
Hypnotic Specter
there is test for each of these.
btw living artifact hard code was wrong, it was allowing you to remove counters at any phase, the soft code is actually correct. updated living artifact test to the correct version in next rev
also fixed a case where "thatmuch" was never set, i now also store the amount on the source of the trigger as well.
the old method was fine when wagic only supported 200 cards, this is so far from the case now. this will avoid bugs being introduced when we add support for a card in soft code.
what this was essentially doing was it would load every set but the hardcode card as soft code, and if you used the card which was originally hard coded, you get a bug where soft and hard code are both loaded.
auto=lord(*[saproling;forest]) transforms((saproling forest creature land,setpower=1,settoughness=1,newability[{t}:add{g}]))
this is close enough for me, its 99% correct in my books, you can declare either forest and saprolings as attackers, target them as thier respective new types, the only thing that is not correct about it is that they can tap for mana the turn they come into play, however they have summoning sickness and can not attack.
im am not going to change the attack/block rules or manaproducer reactToClick just to satisfy this bug in the only card in MTG that does this.
Temporary Insanity
Tower of Coireall
Tower of the Magistrate
Transguild Courier
Unified Strike
Vampiric Sliver
Verdeloth the Ancient
Veteran's Voice
Warbreak Trumpeter
Waterspout Djinn
Weight of Spires
Wild Growth
Withering Wisps
Wrap in Vigor
Yore-Tiller Nephilim
Zirilan of the Claw
Zombie Mob
added a few new cards i found along the way:
Ersatz Gnomes
Extravagant Spirit
Ghastly Demise
Ghostfire
Moonlace
color "artifact" is actually colorless, it does not add the subtype artifact to cards.
1st
had to revise the syntax for my "type:" variable it is now type:blah:location, using the pipe line created nasty returns in some combinations of abilities as the parser confused the pipeline in type: with the one in TC.
2nd
more of a correction then a bug fix, i noticed that upcost had instances where it could still trigger its effect in the draw phase becuase the condiational for the ability resolve was in the update, i left the class mostly untouched but move the resolve out of update and into a receiveEvent for upcost, which triggers only once after you declared that you are leaving the upkeep before draw step begins.
3rd
reworked the construction of multiability to only produce a single multiability with all the abilities in the string instead of nested multiabilities, it is considerabily easier to debug and creates 1/3 less objects for the engine to deal with in comparison to the old method.
also noticed issues with transforms parsing which i was able to easily correct by making it parse transforms in double brackets, transforms((effects))...updated primitive in next revision.
test suite passes, and varified that the fix doesn't effect how "&&" ability works with transforms.
[card]
name=Spore Frog
auto={S}:fog oneshot
text=Sacrifice Spore Frog: Prevent all combat damage that would be dealt this turn.
mana={G}
type=Creature
subtype=Frog
power=1
toughness=1
[/card]
as we all remember spore frog was originally a issue ticket, preventalldamage was not working in all cases, or the effect stuck permanently.
as general advice, a card is "supported" if it is atleast 99% correct. this change was un merited as they showed no issues and had no tickets open.
and i know im not to "revert" anyones changes, but it will be MY email box that gets hit with 5 new bug reports concerning these cards. and i just don't have time to mess around with things that were a nonissue.
