Hi @willowBySword,

Thank you for sharing your crash file. We have identified that this bug is caused by the card “16073b” The Grand Collection (Main Scheme).

The issue occurs when you cannot exhaust your hero but attempt to spend 2 resources, which leads to a game crash. This bug arose due to an update in the resource payment logic, and unfortunately, we did not test this card thoroughly.

We will work on fixing this bug and will implement additional protective code to ensure that similar issues do not cause the game to crash in the future.

Thank you for your understanding, and we appreciate your help in improving the game.

Hi @makstfate,

Thank you for sharing your crash file.

We have reviewed it and found that the bug is caused by the card “45075a.” The issue occurs when a ‘pursuit’ counter is placed on it by the obligation card “45080.” It seems that the game is unable to correctly identify the player in this situation.

We will address this issue in the next version.

Thank you for your report!

Hi @willowBySword,

Thank you for sharing your crash file.

We have reviewed it, and the issue is caused by the fact that the owner of the card “16136” is not a player; its owner is the scenario. Currently, we only check for players’ cards in this context.

We will address this issue in the next version.

Thank you again for your report!

Thank you for sharing your crash file. We have reviewed it and found that the crash occurred because the villain was not in play at that moment. Due to player deck shuffling, the engine attempted to find the villain’s corresponding encounter deck but encountered a null value.

We have fixed this bug in our development version.

Thank you for your patience, and please let us know if you encounter any further issues!

Hi @makstfate,

Thank you for sharing your crash file. We have identified the bug caused by cards “40204” and “49037.”

Here’s a brief overview of the issue:

1. When you play card “49037”, it interacts with hero “37001a”, which has the “X-MEN” trait. As a result, card “49037” gives the hero the traits [“X-FACTOR,” “X-FORCE,” “X-MEN”].
2. Immediately after your hero gains these traits, it triggers the effect of card “40240”, causing it to also gain the same three traits.

This interaction is what leads to the crash.

We will address this issue in the next version.

Additionally, we discovered another bug: card “49037” should only work for characters. We will update this card in the next version as well.

Thank you for your understanding and for helping us improve the game!

Hi @makstfate,

Thank you for sharing your crash report. We have identified that this bug is caused by card “23017,” and we will address it in the next version.

In the current version (0.5.8.74), please avoid using this card to prevent further issues.

Thank you again for helping us improve the game!

Hi @makstfate,

Thank you for sharing your crash report for version 0.5.8.103. I appreciate your help in identifying the issue.

The bug occurs when a player flips their identity after it has been treated as blank due to card “45088”. We are aware of this and will be addressing it in the next version.

Thanks for your patience, and we’ll keep you updated on the fix! If you have any more feedback or questions, feel free to reach out.

Hi @phiology,

Thanks for your message and for trying to help identify the issue! I noticed that the file in the link you provided has been deleted.

I understand your console died, but the game should have generated a crash.json file in the game root folder. If you could locate that file and upload it, that would be really helpful. Alternatively, you can upload one of the save files named save_x.json if it contains the operation that caused the crash.

If you’re unable to upload those files, could you please provide details about how the crash occurred?

Thanks again for your support in improving the game!

Hi @phiology,

Thank you for sharing your save file for version 0.5.8.103. We have identified that this bug is caused by the card “07042.” In your situation, you have two upgrades in play, and this card is designed to discard only one, which leads to a mismatch in the target number.

Additionally, this card is intended to discard a Support card, but we mistakenly labeled it as an Upgrade in the script.

Thank you again for your help! We will fix this issue in the next version.

Hi @8uttmunch,

Thank you for sharing your crash report.

The crash is caused by cards “06019” and “46014.” After you attack an enemy with the upgrade “46014,” using “06019”’s ability to deal 2 damage to the same enemy and defeat them will result in a game crash.

We apologize for the inconvenience and appreciate your patience as we work to resolve these issues.

Hi @8uttmunch,

Thank you for sharing your crash report.

We noticed that you were playing “03033” while your hero became the defender due to the card “27014,” which has a ‘defense’ label.

It seems you intended to use “03033”’s ability to gain +3 DEF. However, the rulebook states:

Playing a defense-labeled ability is not a basic defense and does not cause a hero to reduce the amount of damage dealt by that hero’s DEF.

This means that while your hero can gain the DEF, it will not affect the damage reduction as intended.

As a result, we implemented an assertion to prevent this situation, which caused the game to crash. We will remove this assertion in the next version to prevent this issue from occurring again.

Thank you for your understanding, and we appreciate your feedback!

Hi @8uttmunch,

Thank you for sharing your crash report.

The game crashed due to the following sequence of events:

When your hero defends against an attack using a basic power, the game creates and broadcasts a message: when your hero defends against an attack. You played card “38016” in response to that message, which is perfectly fine.

However, because “38016” has the ‘defense’ label, it creates and broadcasts a new message: when your hero defends against an attack by triggering an ability labeled as a 'defense'. We refer to this as a non-basic defense.

When you then played card “48018” for the second message, it triggered a rule that prevents you from updating your DEF for a non-basic defense message, similar to the previous error. This is why the game crashed.

To avoid this crash in the current version (0.5.8.147), please follow these steps:

1. Declare your hero as a defender.
2. Play “38016”.
3. Click “End Event” to apply the +2 DEF from “38016” to your hero.
4. Play “48018”.
5. Click “End Event” to apply the +2 DEF from “48018” to your hero.
6. Play other cards, e.g., “03033”.
7. Click “End Event” to allow the other card to update the DEF for your hero.

We apologize for this inconvenience and will address this issue in the next version.

Thank you for your understanding!

Hi @8uttmunch,

Thank you for sharing your crash file.

The crash occurred because you played card “03033” without using your hero’s basic DEF power. In the current version (0.5.8.147), please avoid updating DEF during a non-basic defense message to prevent this issue.

We will address this in the next version.

Thank you for your understanding!

Hi @phiology,

Thank you for sharing your crash file.

We noticed that you attempted to place a Confused status card on a Side Scheme, which is not allowed, and this is why the game crashed.

In your case, you played “15004,” which discarded three cards: “11029,” “01186,” and “11024.” The game first processed “11029,” which has three boost icons. As a result, you should choose to place a status card on a character instead of a scheme.

We will address this issue and ensure that selecting a scheme is not permitted in the next version.

Additionally, we noticed that you selected the challenge “Need for Speed” for this scenario. In this challenge, you can only win the game by attacking the Speed Demon minion three times in one turn with the Quicksilver hero. While you can play as “Scarlet Witch”, the challenge is designed for “Quicksilver”.

Thank you for your understanding!

Hi @makstfate,

Thank you for sharing the crash file with us.

We have reviewed the report and identified that the bug is caused by card “27070.” For the current version (v0.5.8.147), please disregard any errors related to this card. We are actively working on a fix and will address this issue in the next version.

If you have any further questions or need assistance, feel free to reach out.

Hi @8uttmunch,

Thank you for sharing your crash file.

We have identified that the bug occurs when you attempt to update your hero’s DEF power by playing “48018” while the hero is not performing a basic defense. In the current version (v0.5.8.147), please avoid updating DEF during a non-basic defense message to prevent this issue.

We are actively working on a fix and will address this in the next version.

If you have any further questions or need assistance, please feel free to reach out.

Hi @makstfate,

Thank you for sharing your crash report. The issue you encountered is caused by card “49002.” In the current version (v0.5.8.147), please avoid putting this card into play. If you already have this card in play, please refrain from flipping your hero to Alter-Ego form.

To continue your game, you can go to step 138 in your saved data.

We appreciate your patience, and we will address this issue in the next version.

Hi @8uttmunch,

Thank you for sharing your crash file.

We have reviewed it and identified a crash occurring at step 39. This crash happens when you attempt to play card “09015” in response to a non-basic defense event broadcast by playing card “03033.”

To avoid this crash, please follow these steps:

1. Declare your hero as a defender.
2. Play card “03033.”
3. Click “End Event” to apply the effects of “03033.”
4. Play card “09015.”

In the current version (v0.5.8.147), please avoid updating your hero’s DEF during non-basic defense events.

We appreciate your understanding, and we will address this issue in the next version.

Hi @Adrian79Ko,

Thank you for sharing the crash file. The issue is caused by card “27070,” and I’m pleased to inform you that we have fixed it in our development version.

If you have any further questions or need additional assistance, please feel free to reach out.

Hi @makstfate,

Thank you for sharing your crash file. The bug is caused by card “32049.”

In the current version (v0.5.8.147), this card can incorrectly activate using itself as a target. We will address this issue in the next version.

Thank you for your understanding!

Hi @makstfate

Thank you for sharing your crash file. This bug is cause by card “49037”, we will address this in the next version.

Hi @Skiptron,

Thank you for sharing your crash file.

The crash is caused by card “40013.” In the current version, it will crash when you attempt to put a player-side scheme into play.

We will address this issue in the next version.

Thank you for your understanding!

Hi @MichaelDSalzman,

Thank you for sharing your crash file.

This crash occurs because of card “48002.” When there are no legal targets to which a “Bamf!” can be attached, and you still search for a “Bamf!” using this card’s effect, the newly searched “Bamf!” will be stacked in the processing area, which causes the game to crash.

We will address this issue in the next version.

Thank you for your understanding!

Hi @makstfate,

Thank you for sharing your crash file for game version 0.5.8.166. We have identified that the crash is caused by card “40006.” We will address this issue in the next version.