Registering a game

Developers → REGISTER A GAME. Three things:

• The id: 3 to 12 of A–Z, 0–9, _ — TETRIBLOX, SNAKE. It is the game's name on the wire (HELLO 1 SNAKE …), its page's address (/snake), and it is yours for ever once approved; a removed game frees it.
• The name: what people read — up to 60 characters. It can be changed later on the game's Store page under your organisation.
• The modes: the boards the game has, one word each, space apart — MARATHON CHALLENGE SPRINT:seconds ULTRA. A mode ranks by score, descending (ties: fewer seconds, then earlier) unless it is tagged :seconds, when it ranks by time, ascending (ties: higher score, then earlier). A daily is not a mode you register (chapter 4). The modes can be changed after registration under the game's Awards section; a SCORE for a mode the game has not got is answered NO SUCH MODE, which is what a mode spelled one way in the game and another on the page looks like.

Choose beta (the default — you and the testers you name, nobody else) or public once approved.

The key

The page shows the program key once: 32 hex digits, 16 bytes. It is K in every MAC the game sends (chapter 3), and the seed of the daily is derived from it. Bake it into the build — Tetriblox's make release TBLX_LIVE_KEY=<32 hex> does exactly that — and never write it anywhere a player can read. There is no page that shows it again; a lost key is a new key, which is rpm game add with a fresh one on the box, and the service's admins will do that on request.

Then

The game exists and is waiting to be approved. Until then the key is issued but the game is refused at HELLO with the reason — ERR 403, not silence. Its page is up: your organisation → Games → the game has the Store page, Builds, Awards, Testers and Visibility. Wire it (chapter 3), declare its awards (chapter 4), write its page (chapter 5); approval comes from the service's admins, the organisation first and then the game.

← Signing up The wire →