Major Bug Report

[mtgrares]

This is inteneded to be a list of major bugs in MTG Forge. Bugs that make the program crash or major implementation issues like Shadow creatures blocking non-Shadow. My focus is primarily on the "big bugs".

Bugs that cause MTG Forge to crash:
1. attacking on your first turn with a creature with haste, like Raging Goblin
2. currently Shadow creatures can block non-Shadow (although this can easily be fixed).

[Huggybaby]

Hey mtgrares, welcome to the forum!

My hasty goblins deck is one of my favorites. I hope you fix the haste bug soon.

[GandoTheBard]

MTG Forge Still doesnt save drafts correctly, nor does it save over a filename if you give it one already being used. Nor does it warn you of this.

[mtgrares]

MTG Forge Still doesnt save drafts correctly, nor does it save over a filename if you give it one already being used. Nor does it warn you of this.

I don't have this problem. I've tried a few drafts and they all work for me. Reading and writing files (IO) tends to be hard/buggy. The problem when reading and writing files is that there are so many errors conditions. In version 2 I plan to save each deck in a separate file, which should minimize the problems.

If other people have this problem, post it.

[GandoTheBard]

Not sure how the computer managed this but I was playing my vise deck vs my sliver deck and noticed at the end of the first turn the computer had drawn 15 cards. It played 4 (land mox mox sliver and discarded 4. I assume this is a Vise related bug.

Same game later on I cast Ancestral on him on my turn to bring his hand total to 10, then he draws 7 more cards on his turn. Screenie attached.

[Mr.Chaos]

I encountered the carddrawing bug with Black Vise as well.
It even carried over from 1 game to the next. Meaning that on turn 1 of the 2nd game of a best of 3, the ai would draw several cards instead of just 1, even if there was no Black Vise or Howling Mine on the table.
This bug only affects the ai side of the game, it never let me draw more than 1 card.

[mtgrares]

Thanks for telling me about Black Vise, hopefully I can fix it.

[GandoTheBard]

I seem to have discovered a way to permanently freeze the game without freezing the client. It is the 2nd main phase and I am clicking ok and the button goes blue then grey and nothing happens. I look at the Taskmanager, Runforge.exe is using no cpu. 10 minutes later it is still not doing anything...I happen to have a hand where nothing is castable so cant even cast anything to check to see if the game is still operational, but I can select various cards and look at their pics. Which means the game is still functional just not going forward for some reason. I figured this is a bug that is probably hard to repeat but I might as well report it anyway. As a follow up I conceded the match because that functionality still worked and now the forge client wont allow the match to continue (button goes blue then grey again).

[jpb]

Looks like a problem when the recursion in nextPhase was removed. Someone would need to attach a debugger and run into the problem to figure it out. If you can come up with a scenario to reproduce this issue I can try to debug it.

[GandoTheBard]

The AI cheat bug where it draws a zillion cards is not confined to the black vise deck. I just played several games with against my mono black pain drain deck where it drew +6 cards during the draw step (or whenever it chooses to) Sometimes it drew extra cards (without a card telling it to) after the combat phase.

This bug is a real game killer imho. Any opponent can win given enough cards in hand, and a smoothed land draw. The two cheats together is quite deadly.

[Mr.Chaos]

Actually, not sure if this qualifies as a major bug, but it sure reduces the AI's options.
What is it: when the AI has a creature in play with a temperary ability, like Roofstalker Wight, then during the AI's first main phase, it will activate this ability over and over again until it runs out of mana.
I have seen this happen with many other cards like it.
So the AI will add flying or haste to the same creature until it runs out of mana. Preventing the AI from playing spells due to no more mana available.

Why the AI does this? No idea. First time it was funny, now it is annoying me.

[Incantus]

Actually, not sure if this qualifies as a major bug, but it sure reduces the AI's options.
What is it: when the AI has a creature in play with a temperary ability, like Roofstalker Wight, then during the AI's first main phase, it will activate this ability over and over again until it runs out of mana.
I have seen this happen with many other cards like it.
So the AI will add flying or haste to the same creature until it runs out of mana. Preventing the AI from playing spells due to no more mana available.

Why the AI does this? No idea. First time it was funny, now it is annoying me.

This is why the AI needs a true minimax search

[DennisBergkamp]

The same happens with Flowstone Hellion, the AI just plays its ability until it dies.

EDIT: I think checks in the canPlayAI() methods associated with abilities like these would fix this, where false would be returned if Roofstalker Wight already has flying, or if Flowstone Hellion has a toughness lower than 2. Or, I don't know, maybe it's more complicated than that...

[jpb]

It is that simple. Please implement that.

[GandoTheBard]

The screwed up computer draws 4-6 cards a turn bug seems related to how many games one plays before killing the client (thus resetting all globals.) I do not quite understand how it manages the cheat but it seems like it starts after 4-5 matches have been played. The deck it plays or against is apparently irrelevant.