Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I was really hyped about playing it, but the file says it is damaged. I tried following your instructions, but it didn't worked.

(1 edit)

Sorry to hear that... As far as I know, you are the first person "my" method doesn't work for.
Are you sure you have done everything correctly? :/

I'm still trying to fix that issue, but in the meantime I want to find a way to make you play!

Yes I've tried everything. I can wait until you find a solution, don't worry

May I ask which OS you are using?

MacOS Big Sur

(+1)

Ok, apparently Big Sur made everything a little bit more complicated... Still, you should be able to run the executable following the instructions provided with the video.
You can try this and let me know (since I'm still using Mojave, so I cannot test it myself!):

Yeah I tried those and it's still not working. :/ 

So, you are someone else having the same issue on Big Sur?!
Darn it, I really need to work something out... These new operating systems are creating more and more problems. :/

Maybe I should make it playable in browser, if I just understand how.

Yeah, dev problems am I right? 

I am afraid so! :D

Hi, yarsavenger! Hope you read this.
I think I've solved the problem, finally (fingers crossed). It was an issue with code signing.
If you:
- download the executable (version 1.1.6);
- move the file into the Application folder as requested;
- open it by clicking with the right mouse button (or Control + click);
- confirm "Open"...
...it should work, even on the latest OS!

I'm sorry it took me so long, but code signing on Apple is really very complicated.
Let me know if it works! :)

Hi, I also tried the solution but it didn't work. Do you have any idea what might be triggering this error?

It's not an actual error, rather the way MacOS deals with downloaded executable. It's a problem that has always existed, but that before was easier to solve.
In the last few days, I tried to bypass it building a browser version of my game: it turns out that HTML5 works in very unpredictable ways, triggering quite a lot of unexpected behaviors.

I swear I won't give up! :)