Games, namespaces & visibility

Every game in the registry has an address, like gabriel/arena, that rooms use to find it. This page explains how addresses are made, why they can't change, and who can see a game.

Namespaces and addresses

Games live under your namespace, claimed once in the Creator Portal when you create your first game. A game's slug names it within the namespace, and together they form its address, for example gabriel/arena.

Namespaces and slugs follow the same grammar: 3–32 characters, lowercase letters, digits and -, starting with a letter, ending with a letter or digit, and without --. Some namespaces are reserved, such as disko, admin, api and test.

Both are permanent: they can't be changed and are never reused, even after the account is deleted. That's deliberate. Rooms load games by address, so if an address could change or be taken over by someone else, a room could end up running a game nobody intended. Your namespace is independent of your player username.

Visibility

Visibility decides who can load a game. It works at two levels: the game as a whole, and each release.

A game's visibility is chosen when you create it and can't be changed:

• A public game accepts public, unlisted and private releases.

• A private game accepts only private releases.

For anyone else, a private release looks exactly like one that doesn't exist, so nobody can even learn that it's there.

Display metadata

The display name, description, icon and About are set in the Creator Portal, not part of any release; changing them needs no publish. The Registry shows them on the game's page: the About is formatted text (Markdown) where you explain the game, its rules and how to host it. Icons are square PNG, JPEG or WebP images of 64–1024 px, at most 256 KiB and not animated. Metadata such as EXIF is stripped on upload.

Quotas