Card Bug Report

[emkay]

Is it right that Pyrohemia deals x damage for x tapped mountains? Should't it be just only 1 possibile damage?

[emkay]

Version: MTG Forge 10-18
Doublecard: ID 1650/1442
Does the Deckbuilder CardID change after new cards are added or is it static like an true ID?
The following Card IDs got no pic in Deckbuilder:

950
985
995
1010
1014
1029
1045
1072
1101
1151
1165
1181
1224
1232
1235
1261
1265
1298
1343
1346
1420
1432
1454
1455
1472
1488
1496
1531
1534
1555
1576
1610
1613
1639
1644
1673
1692
1731
1734
1756
1781
1811
1813
1814
1815
1825
1872
1876
1879
1883
1884
1893

is this usefull in any way?

[GandoTheBard]

Version: MTG Forge 10-18
Doublecard: ID 1650/1442
Does the Deckbuilder CardID change after new cards are added or is it static like an true ID?
The following Card IDs got no pic in Deckbuilder:

950
985
995
1010
1014
1029
1045
1072
1101
1151
1165
1181
1224
1232
1235
1261
1265
1298
1343
1346
1420
1432
1454
1455
1472
1488
1496
1531
1534
1555
1576
1610
1613
1639
1644
1673
1692
1731
1734
1756
1781
1811
1813
1814
1815
1825
1872
1876
1879
1883
1884
1893

is this usefull in any way?

I don't think it is...those are likely null cards.

Is it right that Pyrohemia deals x damage for x tapped mountains? Should't it be just only 1 possibile damage?

In the case of this client I think it is ok that it chunks damage as opposed to stacking it but in theory it should stack it so that order of triggers resolves correctly. But MTG Forge is anything if not a rules breaker.

[jpb]

But MTG Forge is anything if not a rules breaker

HA! That should be the motto of MTG Forge.

[Bog Wraith]

In case this hasn't been posted anywhere else, just wanted to mention that Flowstone Giant also suffers from premature death when the AI always pumps it with two red mana when attacking.

[mtgrares]

Does the Deckbuilder CardID change after new cards are added or is it static like an true ID?

The card ID's are created each time a new card object is created. In the deck builder if you click on the same time multiple times, a new card object is created each time and will have different card IDs. The card ID is only useful during the game play if you have multiple creatures of the same name in play. Like if you have two Birds of Paradise in play and you need to know which one that computer is targeting with Shock.

The card name is more useful than the card ID, so it is more helpful if you list the card names for the pictures that MTG Forge doesn't have.

[Chris H.]

During a game with the computer playing a generated deck the computer played a Black Vise on its first turn.

Apparently, during my next draw phase, my hand doubled in size + 1. I remember having 13 cards in my hand at that time. I was stunned! And the Black Vise did a substantial amount of damage to me.

On my third draw phase, my hand doubled in size + 1 once again.

None the less, at this rate, I quickly lost the game.

This happened with the 11-05-forge updated version.

[GandoTheBard]

During a game with the computer playing a generated deck the computer played a Black Vise on its first turn.

Apparently, during my next draw phase, my hand doubled in size + 1. I remember having 13 cards in my hand at that time. I was stunned! And the Black Vise did a substantial amount of damage to me.

On my third draw phase, my hand doubled in size + 1 once again.

None the less, at this rate, I quickly lost the game.

This happened with the 11-05-forge updated version.

Yeah its a known bug. Someone mentioned it has to do with how things are arranged during the draw step instead of the upkeep step with regards to upkeep costs etc. Just one of many difficulties with the client sadly. Don't look for it to be fixed in this lifetime.

[Chris H.]

Yeah its a known bug. Someone mentioned it has to do with how things are arranged during the draw step instead of the upkeep step with regards to upkeep costs etc.

I play tested the Black Vise and Helldozer deck again and discovered that the Black Vise bug does not effect the computer. I waited for a game with a black vise in my opening hand. I played the Black Vise on my first turn and the computer took only 3 points of damage on subsequent turns.

I also wanted to take this chance to mention that I noticed that the Lay Waste card in the cards.txt file has the wrong casting value:

Lay Waste
2 R
Sorcery
Destroy target land.

I corrected this mistake in the cards.txt file and play tested the deck and the Lay Waste card now asks for the correct mana. The corrected cards.txt file can be found below:

[GandoTheBard]

I corrected this mistake in the cards.txt file and play tested the deck and the Lay Waste card now asks for the correct mana. The corrected cards.txt file can be found below:

Thanks for catching that...I totally don't remember seeing that but then I never play with the card. There is no real need for a new cards.txt as anyone can edit it and make the change from 2 to 3. But thanks for posting it.

[nixrage]

There is a bug i encountered when i'm playing the version 1 mtg forge,

the Defense of the Heart
when the AI sacrifices this card, The AI won't pick 2 cards but the deck, i will select instead!!
can u fix this bug on the release of version 2!!
plz!!

NixRage

[mtgrares]

I

s it right that Pyrohemia deals x damage for x tapped mountains? Should't it be just only 1 possibile damage?

Yes, that is why Pyrohemia is so powerful.

I also wanted to take this chance to mention that I noticed that the Lay Waste card in the cards.txt file has the wrong casting value:

Lay Waste
2 R
Sorcery
Destroy target land.

This was done in order to make Lay Waste more powerful for limited decks. People find this confusing since I changed the mana cost on purpose. It doesn't really matter either way and having the correct mana cost saves some confusion.

[mtgrares]

Black Vise is heavily buggy. You, the player, sometimes draw extra cards because Black Vise messes things up.