Collectible Card Game Headquarters

The validcard-property "counters" had some niggling little annoyances that were fixed in r10546 (namely being unable to compare against svars other than "X" or "Y" and needing a workaround in order to compare with integers > 9). Unfortunately the solution required a syntax change. A simple one, yes, but it'd definitely be annoying if you didn't know about it.
The property name ("counters"), the comparator ("LT/LE/EQ/NE/GE/GT#") and counter type are now separated by underscore.

This has been a public service announcement.

Hellfish, want to give an example or two?

Well, I guess I was a bit unclear, but the change is quite simple really:
Before:

Code: Select all

countersGE1P1P1


After:

Code: Select all

counters_GE1_P1P1


It removes the necessity for things like

Code: Select all

...countersGEXLEVEL...
SVar:X:Number$12


EDIT: Also, as stated above, you can use arbitrary svar names rather than juts X & Y.

I've noted that Arcbound Worker does not enter the battlefield correctly - it just dies (when there are no permanents that would increase toughness of all your creatures). There must be some State Based Effects Check while counters are not put yet.

Is that related to counters mechanics or my changes to PlayerZones location?
I've attached a deck for your convinience.

Hellfish wrote:Well, I guess I was a bit unclear, but the change is quite simple really:

I probably could have figured it out, but I had just woken up and didn't feel like it. Easier if there is a concrete example along with the post, so I don't have to try to find a card that does it.

Max mtg wrote:I've noted that Arcbound Worker does not enter the battlefield correctly - it just dies (when there are no permanents that would increase toughness of all your creatures). There must be some State Based Effects Check while counters are not put yet.

Is that related to counters mechanics or my changes to PlayerZones location?
I've attached a deck for your convinience.

I haven't checked what's causing this, but it must have been a very recent change. I've used Chaotic Goo this weekend (saturday?) and it worked - today it does not.

Sloth wrote:I haven't checked what's causing this, but it must have been a very recent change. I've used Chaotic Goo this weekend (saturday?) and it worked - today it does not.

That was my fault, sorry.

Well, at least I'm learning Forge's internals (not only pretty quest and deck management)