Skip to main content

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

Ah, that's unfortunate! Does it give you the option to view crash information that you could share? Or does it just hang indefinately on the title screen logo?

It hangs on the logo screen, and then the crash screen directs me to this URL, which doesn't have a lot of info haha

https://help.play.date/e0/

Looks like the game managed to trigger "something truly unexpected" then😅

So far I've only seen "regular" game crashes that give a QR code with a stack trace, which can be send to the developer to find the underlying bug. But in this case honestly have no clue what could've caused this or how to figure that out...

If there's anyone reading this who played the game and also has a revA Playdate, could you please leave a comment or send a message on whether you had the same problem?

Same here on revB. Both versions, catalogue and itch crash on my device. 😢

Does it also crash right after the logo screen?

Right. It crashes while trying to load. 

I asked around with some other developers and it seems there is a likely explanation for it related to loading too many resources up front and exceeding a time limit. The reason why this only occurs on some Playdates might be because they somehow load files slower than usual (maybe having almost full storage makes a difference?).

Anyway, the underlying problem should be easily fixable by changing the way stuff is loaded. I'll will implement that and upload a new version. I'll let you and James Gameboy know when that's ready. Hopefully it'll fix the problem!

Thank You so much! I hope, it'll work.  ..and yes, right guessing: my storage is notoriously full. 😅

The issue should hopefully be resolved in the latest version (1.02) that I just uploaded to Itch. Please let me know if you still encounter the problem with this version.

It works! (And that aside, it's a really fun game.) Thank you so much, really appreciate this! 

@James Gameboy: the issue should hopefully be fixed now in version 1.02

Got it loaded! Thanks!