MArcomage

Just a few text changes:

Disipation -> Dissipation
opponents -> opponent's
Loose -> Lose

Sorry, it's just that these things bug me. I like the card, though. I assume it takes from nonzero resources first, or might you luck out by trying to take away more bricks than you have when you still have some gems left?

Sorry. It are things I should do correctly. Not alway too alert, as you see.

I intended it to do maximum resource damage to the player. So if the attack is higher then the number of resources you have, you end up broke.

Cool. I think that's how it should be.

Discard Dragon squadron, but lose ~67 stock. This would be very interesting.

Resources not stock ;-)

200 resources = ~67 stock. My math is perfectly sound.

Not alway too alert, as you see...

And what about cards with attack based on other cards with keywords, like Phoenix or Rainbow Dragon? Or cards with additional attack based on previous turn, like Vulture or Eternal Guardian? Or cards with additional damage from Frenzy or Charge keyword? Or cards with wall nullifying, like War Elephant?

From a programming standpoint, cards with additional attack or wall reduction or added keyword damage wouldn't take those values into account as those numbers aren't part of the card's retrievable Attack value. Battalion of fear would likely be untargetable.

I'm not sure about cards like Rainbow dragon, though, where the Attack value is "8N." That's an excellent question. It's probably asking too much of this card to calculate the damage it would do if played and compare it to the other cards on hand.

Battalion of fear / Rainbow dragon aren't different cases. The first basically has attack 1N (N=recruits), the latter 8N (N=keywords).

When I created the concept I assumed it would take only base damage into account. Taking conditional damage into account might be fun, but I'm not sure it's implementable.
*Turns eyes to Mojko / ultramage*

I'm afraid attack value of a card cannot be referenced by a other card's effect.

Ow wait...
It's even that bad...

I'll leave the concept as it was rejected (as example of unimplementable cards ;-)).
Made a rebuild.