Bug Reports (snapshot builds)

[fmartel]

in r31736 each time I click to recast my commander (from the Zone, not being killed) It cost me 2C more each time. Now, my commander is costing 14C+normal cost

in -r31755 it adds 4C more !!!

[Agetian]

r31755: Evoke appears not to work. I cast Shriekmaw with Evoke and it did not get sacrificed as it entered the battlefield.

- Agetian

[Hanmac]

like i thought, Evoke was totally my fault ... i tested it with the only creature i forget to convert :/

now back again to my MayPlay project ... i need to finish it before next release

[fmartel]

-r31757 I still have the problem where If I try to re-cast my commander the cost goes up each time I check it. (died once, but try to cast it a second time, not enough mana, check again 2C mana has been added)

[Hanmac]

@fmartel: its only normal that you still have the problem when between
r31736 and r31757 it hasn't been fixed yet.

there is the svn changelog:
SVN changelog

i will take a look at it: from my current watching the parameters with Amount does look like they should.

hm while i am there, i might rewrite it a bit about the "May be played" stuff

Edit: Commander RaiseCost should be fixed now, i also updated the MayPlay stuff.

[stormcat]

:r31760
In Commander Game
I controlled Mikaeus, the Unhallowed and Triskelion.
When Triskelion with a undying dies, triggered double.

[Hanmac]

@stormcat: i tried to reproduce it, but i didn't get your result yet.
can you try it again and maybe dump the game state or give a step-by-step how you get that with two triggers?

[Agetian]

r31760: For some reason, when trying to cast a commander from Command Zone (any commander, tried with three different ones), I am presented with a list of two options to cast the commander, both of them the same. Clicking either one works. This is minor but I think this should not happen...

- Agetian

[Hanmac]

Agentian: that is a problem with the MayPlay stuff,
for some reason the original SA does gets a true for checkZoneRestrictions

see this post in another thread:
viewtopic.php?f=52&t=3760&p=199568#p199567

i didn't had the time yet to check this out,
i will probably when i converted more stuff from "May be played" into "MayPlay"

[stormcat]

@Hanmac
Not doing anything special.
please refer to the attachment.

[Agetian]

I think I may have found a bigger problem with recasting the Commander from the command zone, at least kind of. I'm playing a lot of Commander and Planeswalker mode on mobile Forge in Planar Conquest mode, so this has become rather obvious with updating to the latest snapshot build (SVN r31760, in particular):

The AI can recast the commander and the planeswalker without the raised cost, e.g. it always casts Kiora, the Crashing Wave in planeswalker mode for 4 mana, which gives the AI quite a bit of unfair advantage especially as the game goes on. The same happens with commanders (tested with quite a few), the AI can always recast the commander for its original mana cost. This used not to happen recently... not sure if it's a part of the same MayPlay issue as mentioned before or a separate thing.

- Agetian

[Hanmac]

Agetian: i added a fix in checkZoneRestrictions, so mayPlay only for nonBasicSpells.

now the BasicSA should be blocked for the mayPlay stuff (until i rewrite it more)

i am not 100% sure if that does block it for the AI.
(or the AI does find a way to cheat)

[Agetian]

Agetian: i added a fix in checkZoneRestrictions, so mayPlay only for nonBasicSpells.

now the BasicSA should be blocked for the mayPlay stuff (until i rewrite it more)

i am not 100% sure if that does block it for the AI.
(or the AI does find a way to cheat)

Unfortunately, the AI still somehow finds a way around it, it seems... and still recasts the commander for its original mana cost no matter what

- Agetian

[Hanmac]

Agetian: i think i found it, there was an adjust missing in:
ComputerUtilMana.calculateManaCost

so the AI got away without raising ManaCost, now it should be fixed.

[Agetian]

Agetian: i think i found it, there was an adjust missing in:
ComputerUtilMana.calculateManaCost

so the AI got away without raising ManaCost, now it should be fixed.

Ah, nice! Thanks! I'll give it a test soon!

- Agetian