Skip to main content

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

Jessica

6
Posts
1
Topics
40
Followers
17
Following
A member registered Nov 10, 2014 · View creator page →

Creator of

Recent community posts

Hmm, maybe the bundle identifier is a red herring, but the code signing is definitely the bigger issue.

I would say your options are either to sign it, or remove the code signature entirely, leaving you with a Mac app which users will need to bypass security checks (i.e. right click and choose open, then say yes to the prompt) to run.

Hi there, the macOS version doesn't currently work, due to a combination of modifying a signed copy of DOSBox Staging, which has code signing/notarization, and removing/commenting the bundle identifier from the Info.plist.

You'll need to set an actual bundle identifier (I edited mine to `com.kokoscript.wordhopper`) and either remove the code signing as it stands, or sign it yourself with a developer certificate to make this work.

Once I'd edited Info.plist to reinstate a bundle identifier, I made it run on my local machine, with:

# remove any extended attributes and resource forks
xattr -cr ~/Downloads/WordHopper.app && \
codesign --force --deep -s - ~/Downloads/WordHopper.app

Note that this is NOT SUFFICIENT FOR DISTRIBUTION, the resulting app is signed to work on the local machine only.

Absolutely incredible visual design, love it!

I played the demo and enjoyed it, but the smooth overworld/dungeon movement made it uncomfortable, even with the vignette option; is there any option in the full version for something like the player teleporting around to different perspectives but moving the character independently?

(Funnily enough the best workaround I found was shifting the world to be above me so the lack of back face visibility meant the world was mostly not visible aside from major objects 😅)

Just managed to glitch my way through the corner of the fence intersecting the garbage truck on Downtown. Wasn't recording or I'd send you a gif. Approached from grinding the rail with the valve on it. I'm guessing that's not the intended way to get back there 😅

I tried to write mine in Swift too, and ScreenSaverEngine refused to run it. Displayed a lovely flickery message instead.