How a cabinet works#

Every game on Gems Arcadia is a little arcade cabinet. Players buy coins at the Token Booth, walk up to your cabinet and drop coins in. Each coin you take buys the player a credit (a run, a life, a continue: you decide), and you earn 70% of its value.

1. Build an HTML5 game: anything that runs from an index.html. Canvas, WebGL, Phaser, Godot or (uncompressed) Unity web exports all work.
2. Include the SDK (/sdk/v1.js) and call GemsArcadia.insertCoin() when the player wants a credit.
3. Zip and upload the build in the developer portal, preview it with free test coins, then submit it for review.
4. Get paid: every insertion is recorded in your earnings ledger.

In this manual#

• 1.1 GETTING STARTEDZip it, include the SDK, upload, preview.
• 1.2 COIN FLOWWhat happens between the button and the wallet.
• 2.1 SDK REFERENCEinit, insertCoin, events and failure reasons.
• 2.2 ACHIEVEMENTS APIBadges with unlockAchievement(key), plus error codes.
• 2.3 REST API REFERENCEEvery endpoint, straight from openapi.json.
• 2.4 SDK CHANGELOGWhat changed in each SDK version.
• 3.1 SERVER VERIFICATIONCheck insertions from Node or Python.
• 3.2 TESTING & PREVIEWMock mode, preview sessions and test keys.
• 4.1 PLAYER REWARDSHow your scores earn gamers XP, tickets and glory.
• 4.2 STORE PAGE GUIDEScreenshots, trailer, genres and controls that sell.
• 5.1 SUBMISSION GUIDELINESWhat passes review (and what doesn't).
• 5.2 REVENUE SHARE70% of every coin, recorded per insertion.

The rules of the floor#

• Your game never sees the player's account, cookies or email. It runs in a sandboxed iframe and talks to the arcade only through the SDK.
• Coins are debited by the arcade, atomically and exactly once per insertion, from an append-only ledger. Your code can't over-charge a player, even by accident.
• 1 coin = $0.25. You choose how many coins a credit costs (1 to 5).