Hey,
So last night I was digging into JVRMudClient (game) from OrchardKit, trying to finally get it running on my M2 MacBook Air, macOS Ventura 13.4. I wasn’t doing anything crazy — just wanted to connect to a server, check out the interface, and maybe poke at some custom scripts. Turns out, even seemingly simple installs on macOS can become a tiny adventure.
First thing I did: download the build, drag it to Applications, double-click. Classic bounce in the Dock… and nothing. No error, no “app is damaged,” just a disappearing icon. My first thought was Gatekeeper, since this is an unsigned, direct-download game. Standard fix: right-click → Open → Open. Apple explains the behavior in detail here: https://support.apple.com/en-us/HT202491
It launched — briefly. I saw the main window flash for a second, then the game quit. Not ideal.
Attempt #1: Reinstall
I deleted the app, cleared caches in ~/Library/Caches and ~/Library/Application Support, and grabbed a fresh copy. Same behavior. Silent exit. At this point, I started looking at architecture issues and permissions.
Check the binary:
file /Applications/JVRMudClient.app/Contents/MacOS/*
x86_64 only. On M2, that means Rosetta 2. Normally macOS prompts automatically, but it didn’t here. Installed manually:
softwareupdate --install-rosetta
Relaunch. Better, but still froze on load.
Attempt #2: Quarantine Attribute
Downloaded apps often carry com.apple.quarantine. Even if Gatekeeper allows them, macOS may still restrict execution paths. Checked Terminal:
xattr -l /Applications/JVRMudClient.app
Sure enough, it was quarantined. Removed it:
xattr -d com.apple.quarantine /Applications/JVRMudClient.app
Relaunch. Now the window stayed open longer, but the game still failed when trying to access save directories and configuration files. Console.app showed denied permissions entries — the TCC system was silently blocking file access.
What Fixed It
Went to System Settings → Privacy & Security → Full Disk Access and added the launcher. Also toggled access for Documents and Desktop folders, since the game reads/writes there. After this, it finally stayed open, loaded the interface fully, and connected to a test server.
Performance is smooth on the M2; CPU usage is minimal, latency negligible. Controller input works via Bluetooth with no extra config, and saving scripts or preferences persists across relaunches.
I found this page useful while confirming macOS quirks around similar apps: https://sznurkowo.com/game/93561-jvrmudclient.html. It helped me understand why the game was dying silently on first attempts.
Lessons Learned
If I were doing this again from scratch:
- Check architecture immediately (
filein Terminal). - Install Rosetta for Intel-only binaries on Apple Silicon.
- Remove quarantine before first launch.
- Pre-authorize Full Disk Access and folder permissions.
Honestly, knowing that sequence upfront would have saved at least 20–30 minutes of trial and error. But now that it’s running, the client behaves perfectly, with real-time updates, stable saves, and smooth input.
For context, games distributed through the Mac App Store (https://apps.apple.com/) usually handle these permissions automatically, but outside builds like this one require a bit of manual prep. Apple’s notarization docs are handy for understanding the security layers at play: https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
Anyway, just wanted to share — for any OrchardKit titles, once you account for architecture, quarantine flags, and privacy permissions, they tend to run without surprises. The difference between “silent crash” and “working game” is just a few quick Terminal commands and toggles in System Settings.