Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Crash Report Submission - Please Share Your Dump Files Here

A topic by irefrixs created 79 days ago Views: 328 Replies: 24
Viewing posts 1 to 13
Developer (1 edit)

Welcome to the official crash report submission thread for Marvel Champions: Digital Edition!

To help us improve the game and fix any issues, we kindly ask you to share your crash dump files here. This post is dedicated solely to collecting crash reports, so please refrain from posting any other comments or discussions.

How to Submit Your Crash Report:

  1. In the game, click the Report button to automatically upload your crash dump file to ufile server.
  2. Once the upload is complete, you will receive a URL link.
  3. Copy and paste that URL link in this thread as your submission.

Thank you for your help in making Marvel Champions: Digital Edition better! Your feedback is invaluable to us.

Please remember: This thread is for crash report URLs only. Any other comments will be removed to keep the focus on resolving issues.

Developer

https://ufile.io/znlnjz9u

https://ufile.io/2jukwpa4

Developer

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.

https://ufile.io/k97kvbau

Developer

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!

https://ufile.io/cpa82hfv

收藏家1,无法将反派的牌返回他的牌库

Developer

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!

https://ufile.io/n3kr5jsx

Developer (1 edit)

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!

https://ufile.io/mrcyq8nd

Developer

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!

https://ufile.io/1fpw40fl

Developer (1 edit)

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!

https://ufile.io/s3gqsz69
天啟4騎士 歡歡 跳錯誤訊息

Developer

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.

https://file.io/GaqVxDRjGObF

In the game, I could not find the report button because my console died with the game so I hopefully uploaded what will be helpful to identify the problem (if not already imported)

Occured in Thor vs Wrecking Crew in Standard diffilculty - no replay is present because the webserver died.

Thanks for your effort to improve the game!

Developer (1 edit)

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, I reuploaded the files (crash.json as well as a dump of the console for easier error traceback) here:


https://easyupload.io/m/eh9dm9

Developer (1 edit)

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.

https://ufile.io/dcp07u2g

Developer(+1)

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.

https://ufile.io/2pug6hm2

Developer(+1)

Hi @8uttmunch,

Thank you for sharing your crash report.

The crash appears to be caused by card “35018.” When you use this card to defeat an Ultron facedown minion (whose original type isn’t an enemy), the minion reverts to its original type after being defeated. This transition leads to a crash because card “35018” attempts to interact with it as if it were still a minion.

We appreciate your help in identifying this issue, and we will work on a fix.

Thank you!