[confirmed]AI crash Staff of Domination?+Vedalken Shackles?

by **Aswan jaguar** » 28 Feb 2015, 18:57

Describe the Bug:
AI had this crash which seems to be some kind of AI thinking how use the available mana and combine Staff of Domination activations and also use Vedalken Shackles.If I remove either no crash happens.
NOTE: I have seen a lot of times some crashes (like this one) with difficult for AI cards like Staff of Domination which can have so many different plays to happen if upkeep,draw steps on AI's turn are passed quickly and not happening at all or less frequent the same crashes if you pass those steps leaving 1-2 seconds before passing to next step.This with the full AI time thinking and not with the pre-set to faster AI in config.txt in case it matters.Has anyone else experienced this?Does this happen to you with this case and savegame I provide?

Which card did behave improperly ?
Staff of Domination? Vedalken Shackles?

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2014/12/20: Commanding 2014 Urzas,duel

What exactly should be the correct behavior/interaction ?

Are any other cards possibly affected by this bug ?
-

by **BAgate** » 01 Mar 2015, 03:19

I confirmed off of your screenshot, but when I tried your savegame I played 20+ turns with no crash. So it isn't anything simple.

by **Aswan jaguar** » 01 Mar 2015, 07:02

Don't play a lot of turns just this AI turn but more times.Also if you have a stop in draw phase remove it and remember to click fast to go from upkeep (put a stop) to main phase or if it doesn't crash then quickly to 2nd main phase.
As I told use all time AI thinking (54505) if you don't already do in config.txt as it is pre-set to lower number.
If with these settings you don't have crash then it probably means my old pc and limited memory can't handle the computations as fast sometimes and that leads to crashes.Which could be the case as I report by far the most crashes.

by **BAgate** » 01 Mar 2015, 07:30

The AI think time did it. With preset number it never crashed in dozens of tries, but with think time set to max as you said it crashed every time.