mirror of
https://github.com/correl/mage.git
synced 2024-11-15 11:09:30 +00:00
Changed generic counter to CounterType.DOOM
This commit is contained in:
parent
4e23049fbb
commit
4b434f92b3
1 changed files with 2 additions and 2 deletions
|
@ -42,7 +42,7 @@ import mage.constants.SubType;
|
|||
import mage.constants.Outcome;
|
||||
import mage.constants.SuperType;
|
||||
import mage.constants.Zone;
|
||||
import mage.counters.Counter;
|
||||
import mage.counters.CounterType;
|
||||
import mage.game.Game;
|
||||
import mage.game.events.GameEvent;
|
||||
import mage.game.events.GameEvent.EventType;
|
||||
|
@ -113,7 +113,7 @@ class BaronVonCountPutCounterEffect extends OneShotEffect {
|
|||
// but it can still be proliferated to put an additional doom counter on itself (the new counters can be removed and aren't placed on the "numbers" - i.e. they don't influence the card's
|
||||
// functionality in any direct way). To simplify things, I merely put a do-nothing Doom counter on Baron that can be proliferated, etc., in addition to the value that tracks the
|
||||
// the placement of the functional "counter". This only has fringe incorrect interactions with a few cards like Thief of Blood which now gets an extra counter from Baron.
|
||||
new AddCountersSourceEffect(new Counter("doom")).apply(game, source);
|
||||
new AddCountersSourceEffect(CounterType.DOOM.createInstance()).apply(game, source);
|
||||
}
|
||||
return true;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue