Bug Reports (snapshot builds)

[Agetian]

What happened exactly was: I played a land, then I used Reach Through Mists and spliced some other Arcane spell onto it (but I don't remember which), and I copied that spliced result with Uyo Silent Prophet (I think two lands were returned to my hand as a result). I believe the Sire of the Storm effect also kicked in. All of it happened in my Main 2 phase. That's how I arrived at the 8 cards in my hand, and it won't let me discard the 8th one afterwards in my Cleanup phase.

- Agetian

[DeadSpeak]

Hey everyone,

Using the forge-1.3.5-20130109.132128-4 build, I've been playing a Burn at the Stake deck, with Battle Hymn, and I've encountered this problem:

When I cast Battle Hymn, it doesn't go on the stack, it just resolves. Even if my opponent doesn't have any mana open, shouldn't Battle Hymn go on the stack anyway?
And, Battle Hymn then disappears... it's not in the graveyard or the exile zone... just gone...

Also reg. this build, in constructed matches, my opponents doesn't play anything, they just put lands into play and discards when they have too many cards in hand.

Has anyone else experienced either of these two things?

- DeadSpeak

[ArsenalNut]

Hey everyone,

Using the forge-1.3.5-20130109.132128-4 build, I've been playing a Burn at the Stake deck, with Battle Hymn, and I've encountered this problem:

When I cast Battle Hymn, it doesn't go on the stack, it just resolves. Even if my opponent doesn't have any mana open, shouldn't Battle Hymn go on the stack anyway?
And, Battle Hymn then disappears... it's not in the graveyard or the exile zone... just gone...

Also reg. this build, in constructed matches, my opponents doesn't play anything, they just put lands into play and discards when they have too many cards in hand.

Has anyone else experienced either of these two things?

- DeadSpeak

Both of these issues should be fixed. Please let us know if you still see the problem after the next snapshot build is available.

[DeadSpeak]

Hey everyone,

Using the forge-1.3.5-20130109.132128-4 build, I've been playing a Burn at the Stake deck, with Battle Hymn, and I've encountered this problem:

When I cast Battle Hymn, it doesn't go on the stack, it just resolves. Even if my opponent doesn't have any mana open, shouldn't Battle Hymn go on the stack anyway?
And, Battle Hymn then disappears... it's not in the graveyard or the exile zone... just gone...

Also reg. this build, in constructed matches, my opponents doesn't play anything, they just put lands into play and discards when they have too many cards in hand.

Has anyone else experienced either of these two things?

- DeadSpeak

Both of these issues should be fixed. Please let us know if you still see the problem after the next snapshot build is available.

Thanks Arsenal!

Look forward to the next build...

-DeadSpeak

[storms]

Divine Reckoning isent working it destroys all creatures on field

[swordshine]

:arrow: Divine Reckoning isent working it destroys all creatures on field

Fixed. Thanks storms.

[friarsol]

In Quest Mode, cards in your Sideboard aren't marked in the "Decks" column, leading to a scenario where you can accidentally sell certain cards in your SB and then be unable to start the next duel.

Edit: Actually its even worse, it looks like they do let you start the game, and you have a card in your sideboard that's not actually in your card pool anymore (which doesn't make any sense).

[Agetian]

In Quest Mode, cards in your Sideboard aren't marked in the "Decks" column, leading to a scenario where you can accidentally sell certain cards in your SB and then be unable to start the next duel.

Edit: Actually its even worse, it looks like they do let you start the game, and you have a card in your sideboard that's not actually in your card pool anymore (which doesn't make any sense).

I'd look into this ASAP but sadly, I have to be away from coding Forge for a while (probably until about the end of January or so, maybe a little more or less than that), due to a very intense schedule at my workplace, I'll see if I can manage to stick it into my schedule within a few days, but if not, can someone (especially maybe someone who is good with the Quest Mode code) please look into this?
EDIT: I corrected the part with the card not being marked as a card in deck if it's located in the sideboard (was an easy and quick fix) but sadly I don't have time to correct the other (bigger) issue at the moment... I quickly looked at the relevant code and I can see where the problem with the card not disappearing from the card pool is (the code in sellCard in QuestUtilCards.java on line 338 references only the Main part of the deck and does not detect where the card actually came from - from the main or from the sideboard; thus, selling the card from the sideboard is, in fact, impossible, and the card from the sideboard is never truly "sold" (as in "goes out of the card pool")), but I can't devise a strategy to fix that part quickly enough before I have to go to work Your help is welcome until I can find time to get back to this...

Also, here's a bug that I noticed today:
The opponent had in play an Initiate of Blood, and the flipped version (the 4/4 legendary). Also a Kiki-Jiki, Mirror Breaker, which he used to copy the Initiate of Blood (indeed, that was the only legal target). I think this should work, because the Initiate is not legendary when it's not flipped (and even if this weren't true, the legend rule would've kicked in when the 2nd Initiate was summoned, as the first was already flipped). What *actually* happened in Forge is that the Initiate, the flipped Initiate, and the copy all died (this is already wrong because that's not how the legend rule works even if it did apply here, which it doesn't). I can look in his graveyard now and see both Initiates of Blood. I advanced to the next step, and the log says the computer just activated the Initiate of Blood! It's almost like it doesn't realize all the initiates died.

- Agetian

[Max mtg]

EDIT: I quickly looked at the relevant code and I can see where the problem with the card not disappearing from the card pool is (the code in sellCard in QuestUtilCards.java on line 338 references only the Main part of the deck and does not detect where the card actually came from - from the main or from the sideboard; thus, selling the card from the sideboard is, in fact, impossible, and the card from the sideboard is never truly "sold" (as in "goes out of the card pool")), but I can't devise a strategy to fix that part quickly enough before I have to go to work Your help is welcome until I can find time to get back to this...

Seems easy enough, check if r19047 does it.
Generally the code is able to track loss of even several cards at a time.

[friarsol]

Why is quest mode marked as 60 card restriction now? It should be 40 as it's mostly a limited format.

Edit: Quest should be: 40 Main deck, 15 Sideboard.

[Agetian]

@ Max Mtg: Thanks for fixing the quest mode card selling from the sideboard!

A couple new things I've noticed:
1) I flipped a Voidmage Apprentice to counter a creature that the opponent was playing face down. The rules say that immediately after a face down creature leaves play, it must be turned face up. However, when I look into his graveyard all I see is a card named "Face Down".

2) Another timing bug: I casted a Shock during my M2 phase and it didn't resolve until my opponent's UP.

Btw, agree about the quest mode, it used to be (and most likely should be) 40 deck, 0 or 15 sideboard (at least that's what was decided upon after the previous discussion).

- Agetian

[Max mtg]

Well, quest mode then needs its own deck validation rules - here they come! (r19054)
You may adjust them in forge.deck.DeckFormat.QuestDeck enum member

[friarsol]

It appears Schemes can show up in Full Cardpool booster packs.

[Almeida]

hey guys Skullclamp is not working

[friarsol]

When my Quest Pet is destroyed I get this error. Looks like the Owner isn't being assigned somewhere:

forge.card.spellability.TargetSelection$2
java.lang.NullPointerException
at forge.GameAction.sacrificeDestroy(GameAction.java:1421)
at forge.GameAction.destroy(GameAction.java:1550)
at forge.GameAction.checkStateEffects(GameAction.java:1134)
at forge.game.zone.MagicStack.unfreezeStack(MagicStack.java:208)
at forge.game.zone.MagicStack.addAndUnfreeze(MagicStack.java:188)