Page 5 of 441

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 12:30
by Almost_Clever
GandoTheBard wrote:--Empty the Warrens -- this gives a random number of Goblin Tokens instead of using Storm to replicate it properly.
This one kind of bothered me, since computers typically just don't like doing random things. Figured out the pattern (it isn't random but it isn't correct, either). In addition to counting the spells previously played this turn, Empty the Warrens counts (incorrectly):

    -- Lands played and put into play (Playing and cracking a Terramorphic Expanse adds two to the Storm count.)
    -- Permanents put into play through any sort of effect other than summon spells (Raise the Alarm, for example, adds three to the Storm count, one for the spell and two more for each soldier token. Activating The Hive to put a wasp token into play will add one to the Storm count. Casting Pyrohemia adds two to the Storm count, once for the spell, once for the enchantment in play.)
    -- Activated abilities, such as pumping a Pyre Charger, or pinging with a Prodigal Pyromancer. Note, stacking abilities reduces the Storm count (if you pump the Pyre Charger three separate times, it adds three to the Storm count. If you pump three times without waiting for each pump to resolve first and ping with a Tim, that only adds one to the Storm count.)
The last one the hardest one to figure out ;^), because it seemed inconsistent from turn to turn. BTW, I typically wouldn't recommend using Pyrohemia with Prodigal Pyromancer, Pyre Charger, and Empty the Warrens unless you want to clear your side out because you've really slooooowed down your computer :wink: .

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 16:10
by Chris H.
This message originally started in another thread.

Now that we have First Strike we may want to consider changing the code for Valor.

If we do we may want to add an enchantment which will give the ability of vigilence to our creatures.

If the code for Valor is corrected now that we have first strike, the old code for Valor could with some modification be re-used for Oathsworn Giant.


Oathsworn Giant
4WW
Creature - Giant Soldier
3/4
Vigilance Other creatures you control get +0/+2 and have vigilance.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 17:03
by Rob Cashwalker
Oathsworn Giant is more like a glorious anthem effect, not the Valor effect. But I agree, we've only scratched the surface of cards that deal with First Strike and Doublestrike, Lifelink and such....

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 17:52
by Chris H.
I meant to add more data about the Valor card. Rares had a good description of the problem in a message thread pertaining to errors and design limitations. I was hoping to do a copy and paste of his description, but I could not find his message. #-o

In cards.txt we have this description for Valor:

Valor
3 W
Creature Incarnation
As long as Valor is in your graveyard, creatures you control have vigilance.
2/2
Vigilance


It would appear that when Valor was added it was decided that first strike would require additional coding. I'm guessing that Valor was given Vigilance instead. In essence, a design decision.

I'm not the one doing the coding and can not honestly state that it would be easy at this time to correct the Valor card and to code a different card to give a similar effect. That is, to have a card which gives vigilance to all of your creatures.

I was play testing a deck with Valor, Marble Titan and Puppeteer. I decided to stop work on this deck with the new first strike code.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 18:06
by DennisBergkamp
I already updated Valor to have First Strike, I will also add Oathsworn Giant.

Empty the Warrens

PostPosted: 23 Jan 2009, 18:47
by mtgrares
About Empty the Warrens, I "simulated" storm by counting the number of permanents that went into the graveyard this turn, at first this seemed like a reasonable solution, but permanents may go into the graveyard for other reasons, like a creature being destroyed.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 21:00
by Almost_Clever
Chris H. wrote:If we do we may want to add an enchantment which will give the ability of vigilence to our creatures.
Try Serra's Blessing.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 21:36
by DennisBergkamp
I will add Serra's Blessing too....

By the way, one interesting "bug" I've seen is when all I have is a Wall of Ice and the computer has a bunch of beefy creatures (Kavu Climber, Gnarled Mass, Barbary Apes) and also a Gaea's Anthem. He still won't attack for a few turns, until he has like 5 or 6 of them.

EDIT: another bug: Jedit Ojanen of Efrava can block an additional creature.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 22:47
by GandoTheBard
I've updated the bugs list a little. Please let me know when the next release comes out which bugs Should be fixed and please testers...confirm so I can grey out what is no longer relevant.

Re: Current Known Bugs list

PostPosted: 23 Jan 2009, 23:32
by DennisBergkamp
Gando, will do. I fixed about 15+ of the bugs from the list (although a lot of those are just fixes in cards.txt). I will post all fixes when I'll post the new version.

By the way, Jedit Ojanen and Jedit Ojanen of Efrava are two different cards. The reason the latter can block an additional creature, is because when he blocks, his ability gets put on the stack. The current combat implementation does not like this, and after clicking OK right after his ability resolves, I am able to block an additional creature. Interesting though, when I block 2 3/3 creatures with him, he still won't die. So I wonder if the second creature's combat damage gets lost someway, or if the AI hasn't been programmed to assign this combat damage properly (I don't think there are any "can block an additional creature" cards in mtgforge).

Re: Current Known Bugs list

PostPosted: 24 Jan 2009, 01:04
by GandoTheBard
Pardon my Typo lol...Ill fix it asap.

Re: Current Known Bugs list

PostPosted: 24 Jan 2009, 01:52
by Chris H.
DennisBergkamp wrote:I will add Serra's Blessing too....
Thank you.

With your recent additions of Verduran Enchantress and Enchantress's Presence I realized that you may have an interest in adding a few enchantments to power these cards. :D

Re: Current Known Bugs list

PostPosted: 24 Jan 2009, 02:51
by Almost_Clever
Computer blocks non-flying attackers with Cloudseeder-generated Cloud Spirit tokens.
Metallic Sliver a 3/3 creature with Sliver Legion in play as only other sliver (Sliver Legion is correctly 8/8 creature. The power/toughness boost should be {number of slivers in play - 1}, but that might cause problems if the Sliver Legion leaves play.
Draft decks include cards the computer won't play (Exclude, for example) or can't play (Goblin Deathraiders in a UB deck). I suspect the deck-building routine just counted the Goblin Deathraiders as a black card. I notice when I'm building a draft deck, the count of cards by color do not properly count gold cards.

Re: Current Known Bugs list

PostPosted: 24 Jan 2009, 03:44
by DennisBergkamp
Thank you.

With your recent additions of Verduran Enchantress and Enchantress's Presence I realized that you may have an interest in adding a few enchantments to power these cards. :D
Yes, I should make a few enchantments: Fastbond, (Exploration), Words of Wind, Wild Growth, Fertile Ground... those combo really well with the enchantresses.
I've been thinking about it, but unfortunately these are quite tricky currently in MTGForge :(
Maybe I'll try a few easier ones first.

Re: Current Known Bugs list

PostPosted: 24 Jan 2009, 12:00
by Almost_Clever
The AI does not seem to understand when the human player controls Intrepid Hero (AI plays fatties when human control active Intrepid Hero. AI will pump creatures to power 4 or more when human controls active Intrepid Hero. AI will destroy Soul Warden rather than Intrepid Hero when the AI is playing all big creatures.)

Probably more of a "feature" (due to how the computer draws land/non-land) rather than a bug, but the computer played Treefolk Harbinger with an empty hand, searching for a forest to put on top of the library, but then played a Darkling Stalker next turn (clearly not drawing the Forest).

I've run into a bug with creatures illegally blocking, but I cannot reliably repeat the problems with test decks (unlike the Cloud Sprite tokens blocking non-flyers, above). The problems I've seen the most are the computer blocking with creatures that cannot block (Hulking Goblin, Yellow Scarves Troops, etc.).