Bug reports for Magarena 1.66

[melvin]

To help us in addressing bugs, the best way is to create an issue on the issue tracker. This lets us keep track each report separately and ensures it doesn't get lost.
https://github.com/magarena/magarena/issues (requires github account)

For game play bugs, please report in as much details as possible, especially the list of permanents on the field, any continuous effects in place etc. If possible, do attached the <install folder>/Magarena/logs/game.log file to the report.

Less preferred is to post your report in this thread. (requires forum account)

You can report anonymously via gitreports, note that name/email if provided will be listed on the issue tracker.
https://gitreports.com/issue/magarena/magarena (no sign-up required, name/email optional)

[kannikkiy]

When AI plays a moprh creature spell you can see the face of this creature card in stack popup image as well as its name in action window (see attached files). Perhaps, it's not a bug, but feature?

[Lodici]

Thanks tracking as issue #455 and issue #454.

[sponeta]

Another bug with Colfenor's Urn: it seems to check base toughness, not current toughness. I attacked and killed opponent's Belligerent Hatchling, which at the time had 2 -1/-1 counters on it, so its toughness was 2, yet the AI was able to exile it with Colfenor's Urn.

[ShawnieBoy]

Another bug with Colfenor's Urn: it seems to check base toughness, not current toughness. I attacked and killed opponent's Belligerent Hatchling, which at the time had 2 -1/-1 counters on it, so its toughness was 2, yet the AI was able to exile it with Colfenor's Urn.

Thanks, tracking as Issue #462

[sponeta]

Is this a bug or just weird rules?

I attacked with Deathgazer, AI blocked with Pit Raptor. After blockers were declared, I used Distorting Lens on Pit Raptor to turn it blue to make Deathgazer's ability affect it, but it didn't get destroyed after combat. I guess the blocker was black when blockers were assigned so Deathgazer's ability fired but failed. But should Deathgazer actually make the color check at the end of the declare blockers phase instead of the start?

Deathgazer's ability does work otherwise. Just to check, I went back with undo and used Distorting Lens before attacking. The AI was kind enough to block with Pit Raptor anyway, and it got destroyed correctly.

[ShawnieBoy]

Is this a bug or just weird rules?

I attacked with Deathgazer, AI blocked with Pit Raptor. After blockers were declared, I used Distorting Lens on Pit Raptor to turn it blue to make Deathgazer's ability affect it, but it didn't get destroyed after combat. I guess the blocker was black when blockers were assigned so Deathgazer's ability fired but failed. But should Deathgazer actually make the color check at the end of the declare blockers phase instead of the start?

Deathgazer's ability does work otherwise. Just to check, I went back with undo and used Distorting Lens before attacking. The AI was kind enough to block with Pit Raptor anyway, and it got destroyed correctly.

This is just the rules, "when blocks or is blocked by a non-black creature" triggers as soon as it blocks/is blocked by a non-black creature (during the declare blockers phase, fast effects can only be applied afterwards, once it has triggered it's too late). It only resolves at the end of combat, it doesn't check again.

Declare Attackers
Fast Effects
Declare Blockers <- Triggers here
Fast Effects <- Too late to effect the triggers

[sponeta]

That's dumb but logical. Thanks for clearing it up!

[muaddib]

Game crashed, screenshot and logs attached.

[Lodici]

Game crashed, screenshot and logs attached.

Thanks this has already been raised as issue 456.

It is caused when you move the mouse cursor over "Ajani's Pridemate" in the prompt (see below). The only workaround for 1.66 is to try and avoid moving the mouse over any blue text in the user prompt. Sorry for the inconvenience.

[sponeta]

Storm Entity seems to count itself, even though it says "each other spell".

[ShawnieBoy]

Storm Entity seems to count itself, even though it says "each other spell".

This is already being tracked as Issue 321

Unfortunately there's no simple way of removing itself from the casting check (ie. Number of spells -1) as it can also enter the battlefield without being cast and throw the numbers off again.

[sponeta]

Ooh that's a good point. Good to know!

[jerichopumpkin]

AI casted Avoid Fate without a target and it staid in play like an enchantment

[melvin]

AI casted Avoid Fate without a target and it staid in play like an enchantment

Thanks for the report! The card was wrongly coded to use a ETB trigger instead of a spell effect. Fixed for 1.67 (Oct) release.