Collectible Card Game Headquarters

Describe the Bug:

I don't know the card causing this error and crash during opponent's main phase, but the message indicates something about the graveyard and card drawing. I thought I'd put it up here in case you guys can glean anything from it.

The dump.dmp:

Code: Select all

Assertion failed
functions/deck.c:1511
graveyard_ptr_mutable[player][position] == iid_draw_a_card
0: 0x0253E188
1: 0x0253E2E9
2: 0x024F451F
3: 0x021532F5
4: 0x02488B1D
5: 0x0254E415
6: 0x0252B97D
7: 0x0252B9DF
8: 0x024E6935
9: 0x024EAA97
10: 0x0254E415
11: 0x0252B97D
12: 0x0252C0A6
13: 0x004344B2
14: 0x00475D78
15: 0x00436D07
16: 0x00436A80
17: 0x0252C9F9
18: 0x00475CBF
19: 0x0252BC06
20: 0x0252C297
21: 0x004371B4
22: 0x0043D326
23: 0x00439A10
24: 0x0047902C
25: 0x004946E9
26: 0x77A56359
27: 0x77BA7B74
28: 0x77BA7B44



The board looked like this:




Savegame attached, version 8-2020 a62926f - gauntlet. Thank you!

A word of explanation without looking into it further: failed assertions are errors that shouldn't occur in theory but occur surprisingly often in practice.
Assertions (via the function assert or in our case the macro ASSERT) check whether a certain condition holds and if not create the type of error you got. The is typically a sanity check, for example a parameter like card_id should not be negative (the most famous dump we have). But of course there are others. It is a smart way to have things blow up in a controlled way. You could go on with the wrong parameter, but something would break for sure and typically in a less expressive and readable way. This way we know what went wrong and where to look, which brings us one, maybe two steps ahead of the typical situation where you either know what breaks but not where to look or worse, you know that something breaks but not what and where.

AI doesn't want to crash it again in 10 times loading your savegame no crash or error whatsoever. It is also one of the very few games I remember especially with so few cards involved that AI makes such a variety of different plays each time savegame is loaded. If I remember correctly AI made 7 different plays out of 10 tried.
Probably this is a Scrapheap Scrounger (it is in AI's hand) issue as we do have a bug report about it or
a combination of two cards in AI's hand. Indulgent Aristocrat sacrifice ability vs Scrapheap Scrounger reanimate ability and how AI tries to combine those.