Page 1 of 1

[fixed/closed]Aeon Chronicler - can't be added

PostPosted: 20 Aug 2016, 05:38
by BAgate
Describe the Bug:
When you add Aeon Chronicler to your hand (tried both debug and via Death Wish) you get the following dump:

bad parameters
in_play(0, -1)
0: 0x024680A4
1: 0x0241E87B
2: 0x022A7D24
3: 0x02475FB5
4: 0x024297ED
5: 0x0242D547
6: 0x0241E5B7
7: 0x0047965B
8: 0x021A6498
9: 0x021A64E1
10: 0x021A7F1F
11: 0x02475FB5
12: 0x024297ED
13: 0x02429837
14: 0x02429EDE
15: 0x004368C6
16: 0x02427BB3
17: 0x0043BFAA
18: 0x004399BD
19: 0x0047902C
20: 0x004946E9
21: 0x779D38F4
22: 0x77C05DE3
23: 0x77C05DAE
24: 0x00000000


Which card did behave improperly ?
Aeon Chronicler

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2016/08/07: Eldritch Moon, duel

What exactly should be the correct behavior/interaction ?
no dump

Are any other cards possibly affected by this bug ?
-

Re: Aeon Chronicler - can't be added

PostPosted: 20 Aug 2016, 07:06
by Korath
It's because it calls in_play() before checking event - which I very carefully made it not do the last time I changed it. This is normally just a poor practice and performance sink (not to mention wrong for this card, and most like it - the power/toughness setting ability works in all zones), but it crashes cards with characteristic-defining abilities for power or toughness (i.e. */*, */whatever, or whatever/*) because the card parameter will be -1. Running git blame to find the change that resulted in the weird-looking check would have turned up commit 9a50dd55, which has a very thorough explanation why it'd be a bad idea to just remove it.

There shouldn't be any difference between adding a card to your hand with the debug menu or with Death Wish anymore, by the way, except that Death Wish is more clicks and costs you life.

Re: [confirmed]Aeon Chronicler - can't be added

PostPosted: 25 Aug 2016, 09:27
by Korath
Tempting as it is to just leave this, reverted back to the working version in d324a51.