LDOE Mod — License Keys

Issue a new key

Updates (over the air)

Push a new menu and changed model files to every licensed phone, no reinstall. Phones check on each game start, download in the background and use the update from the next start. Build first with make-protected.cmd (it encrypts the menu and registers its key), then press Publish menu. A game update or a loader change still needs a new APK.

Approved build hashes

Optional. When this list is empty, every release build is accepted (no lockout on first deploy). Once you add at least one hash, /api/validate rejects any build whose hash isn't in this list, even with a valid key. Run node build-release.js to get a build's hash, then paste it here.

Devices seen

Every physical device that has ever opened the app, even one that never entered a key — the Activity column tells apart a bare first-launch ping, someone guessing/probing keys, and a device that's actually used a real key. Banning a device here blocks it outright, independent of any key: even a brand-new, otherwise-valid key won't work on a banned device.

Active & issued keys

A key locks to the first device that successfully activates it (by Android ID) — that's what stops someone forwarding a working key to a friend. If the real owner gets a new phone, use Unbind so the key can lock to the new device on next activation.