[fixed/closed]0-casting cost spells
Posted: 20 Oct 2013, 02:36About half of the 0 casting cost, non-artifact spells are showing up as colorless in hand and on the stack. All are correct in the deckbuilder. It may well just be a display error for some while in-hand, but all (except perhaps Evermind) are really the colors they look like on the stack. I haven't tested any of their colors in-hand.
Testing methodology: For on-stack, five copies of Deathgrip, each laced and sleighted to a different color; I can't think of a straightforward way to test Evermind. For in-hand, probably Persecute is the easiest way?
Affected: Evermind, Intervention Pact, Living End, Pact of the Titan, Restore Balance, Slaughter Pact, Wheel of Fate
Working correctly: Ancestral Vision, Crimson Kobolds, Crookshank Kobolds, Hypergenesis, Kobolds of Kher Keep, Pact of Negation, Summoner's Pact
(The giant that Pact of the Titan makes is colorless too. That, at least, I've fixed in f4b49db.)
It also occurs to me that they probably all will show up correctly (while still having their actual, in-game colors wrong) with the drawcardlib distributed with OoAv2. That version tries too hard to "fix" spells that the game engine reports as colorless (which it usually does for activation cards on the stack, other than the top one) - this is the same reason Ghostfire shows up as red. The snapshot here is a bit more conservative.
Testing methodology: For on-stack, five copies of Deathgrip, each laced and sleighted to a different color; I can't think of a straightforward way to test Evermind. For in-hand, probably Persecute is the easiest way?
Affected: Evermind, Intervention Pact, Living End, Pact of the Titan, Restore Balance, Slaughter Pact, Wheel of Fate
Working correctly: Ancestral Vision, Crimson Kobolds, Crookshank Kobolds, Hypergenesis, Kobolds of Kher Keep, Pact of Negation, Summoner's Pact
(The giant that Pact of the Titan makes is colorless too. That, at least, I've fixed in f4b49db.)
It also occurs to me that they probably all will show up correctly (while still having their actual, in-game colors wrong) with the drawcardlib distributed with OoAv2. That version tries too hard to "fix" spells that the game engine reports as colorless (which it usually does for activation cards on the stack, other than the top one) - this is the same reason Ghostfire shows up as red. The snapshot here is a bit more conservative.