Collectible Card Game Headquarters

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 include a gameplay report zip file. You can create a gameplay report by opening the options menu (press Esc during a duel) and selecting the "Gameplay Report" menu item.

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)

Enchanted Evening + Opalescence does not works if Opalescence was the first card to enter the battlefield. I don't remember if this issue is an old, already reported issue or not, so here I am, just to be sure

jerichopumpkin wrote:Enchanted Evening + Opalescence does not works if Opalescence was the first card to enter the battlefield. I don't remember if this issue is an old, already reported issue or not, so here I am, just to be sure

I think this may be due to Layer Dependencies - where timestamp should be ignored if two effects affect the same layer, or the effect of one would change the effect of another. Already a complicated area.

I don't think that Magarena can identify dependencies.

Comprehensive Rules wrote:613.7. Within a layer or sublayer, determining which order effects are applied in is sometimes done
using a dependency system. If a dependency exists, it will override the timestamp system.

613.7a An effect is said to “depend on” another if (a) it’s applied in the same layer (and, if
applicable, sublayer) as the other effect (see rules 613.1 and 613.3); (b) applying the other
would change the text or the existence of the first effect, what it applies to, or what it does to
any of the things it applies to; and (c) neither effect is from a characteristic-defining ability or
both effects are from characteristic-defining abilities. Otherwise, the effect is considered to be
independent of the other effect.

613.7b An effect dependent on one or more other effects waits to apply until just after all of those
effects have been applied. If multiple dependent effects would apply simultaneously in this way,
they’re applied in timestamp order relative to each other. If several dependent effects form a
dependency loop, then this rule is ignored and the effects in the dependency loop are applied in
timestamp order.

613.7c After each effect is applied, the order of remaining effects is reevaluated and may change if
an effect that has not yet been applied becomes dependent on or independent of one or more
other effects that have not yet been applied.

Don't worry if that reads like nonsense!

Stensia Masquerade puts the +1/+1 counter on itself

jerichopumpkin wrote:Stensia Masquerade puts the +1/+1 counter on itself

Pushed a fix, now uses the groovy code from Rakish Heir

have this crash twice already since ver 1.72
maybe have something related by the cards i'm playing. crash.log file is attached.

I have 2 decks that occasionally crash. I was going to collate the crash reports but I started trying to make new cards so I have a lot of crashes from that .
On firemind legacy reanimator and legacy enchantress. Its about 1 game in 50 maybe.

Crash report, maybe it was because I played 2 cards with madness at the same time

jerichopumpkin wrote:Crash report, maybe it was because I played 2 cards with madness at the same time

Thanks for the crash.log, it looks like a UI issue for triggers from cards. Were you trying to mouse over the card name on the stack/log when the crash occurred? Tracking this as https://github.com/magarena/magarena/issues/760

hong yie wrote:have this crash twice already since ver 1.72
maybe have something related by the cards i'm playing. crash.log file is attached.

Thanks for the report. Tracking this as https://github.com/magarena/magarena/issues/761

Does this occur for the first game or after a few games?

Please attach you general.cfg file it can be found in the Magarena folder.

melvin wrote:

jerichopumpkin wrote:Crash report, maybe it was because I played 2 cards with madness at the same time

Thanks for the crash.log, it looks like a UI issue for triggers from cards. Were you trying to mouse over the card name on the stack/log when the crash occurred? Tracking this as https://github.com/magarena/magarena/issues/760

I'm sure that I didn't try to do it, but it could be that it happened by chance, as I was about to cast Fiery Temper on the creature then changed my mind

EDIT: also I can confirm that it's not because of the double madness trigger, as I did it yesterday and everything was ok (with the same 2 cards, by the way)

melvin wrote:

hong yie wrote:have this crash twice already since ver 1.72
maybe have something related by the cards i'm playing. crash.log file is attached.

Thanks for the report. Tracking this as https://github.com/magarena/magarena/issues/761

Does this occur for the first game or after a few games?

Please attach you general.cfg file it can be found in the Magarena folder.

it happen right at my first game after i updated to ver 1.72.
when i read a problem could be triggered by UI, i think that's very possible.

I had a madness crash too but I cldn't reproduce it. I cast Asylum Visitor in combat with madness, but a second time doing exactly the same was fine will post more if I see it again.



I had a thought it might have been looking for the transformed picture or something the first time and been fine since ?

While I was trying to make Kalitas I possibly found a bug with Anafenza, The Foremost. Which is that the creatures shd not die and then be exiled for example Hangarback Walker shd not come back as thopters if Anafenza is in play which at the minute it does with my Kalitas which is a direct copy.

Eye of Ugin reduces the cost of its own activation.