Collectible Card Game Headquarters

Hello Sirs,

I have an Azorius deck I've been trying to play in constructed mode Other decks work, just this one giving me problems. There must be a specific card triggering this issue. Note that this usually happens somewhere during the first turn.

Here is the decklist, maybe there is something problematic here?

2 Angel of Serenity
4 Azorius Charm
4 Azorius Guildgate
4 Condemn
4 Court Hussar
2 Faith's Fetters
4 Hallowed Fountain
8 Island
8 Plains
4 Remand
4 Render Silent
4 Sphinx's Revelation
4 Supreme Verdict
4 Windreaver

Here is the bug log:

NullPointerException | Open

Code: Select all

Forge Version:    1.3.16-r21506
Operating System: Windows 7 6.1 amd64
Java Version:     1.7.0_21 Oracle Corporation

java.lang.NullPointerException
   at forge.card.MagicColor.fromName(MagicColor.java:23)
   at forge.card.TriggerReplacementBase.meetsCommonRequirements(TriggerReplacementBase.java:304)
   at forge.card.trigger.Trigger.requirementsCheck(Trigger.java:308)
   at forge.card.trigger.TriggerHandler.runSingleTrigger(TriggerHandler.java:315)
   at forge.card.trigger.TriggerHandler.runWaitingTrigger(TriggerHandler.java:285)
   at forge.card.trigger.TriggerHandler.runTrigger(TriggerHandler.java:177)
   at forge.game.GameAction.changeZone(GameAction.java:230)
   at forge.game.GameAction.moveTo(GameAction.java:370)
   at forge.game.GameAction.moveTo(GameAction.java:351)
   at forge.game.player.Player.playLand(Player.java:1780)
   at forge.game.ai.AiController.playLands(AiController.java:866)
   at forge.game.ai.AiController.onPriorityRecieved(AiController.java:823)
   at forge.game.ai.AiInputCommon$1.run(AiInputCommon.java:74)
   at forge.FThreads$1.run(FThreads.java:115)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)


Thank you gents and have a nice day.

Your decklist is fine.

Take the last snapshot (http://www.cardforge.org/releases/snaps ... -SNAPSHOT/) or the next beta (est. release on May, 31) for a solution to this problem.