CLI reference

ase games

Work with the Game Registry.

ase games list

Your studio's games.

Requires: a sign-in (ase login), in any studio role.

Changes: nothing; it only reads.

ase games list [OPTIONS]

Argument	Description
`--json`	Print JSON.

Examples

ase games list
ase games list --json

ase games check

Check a game repo's own brain/ as its release will publish it.

Requires: a sign-in (ase login) or, in CI, a release credential.

Changes: nothing; it only reads.

ase games check [OPTIONS]

Argument	Description
`--project <PROJECT>`	The game repo checkout whose brain/ to check. Default `.`.
`--game <GAME>`	The game's id, which names it in what's wrong; the checkout's folder name by default.

Examples

ase games check

ase games adopt

Put a game whose repo already exists on ASE Brain, run in that repo: its row in your studio, its own brain/ published, then Brain's files synced. Safe to run again.

Requires: a sign-in (ase login) with the studio permission manage_games (Owner and Admin). git, and a brain/game.toml that passes ase games check. A repo whose organization belongs to another studio is refused.

Potentially destructive. Adds the game to your studio in dev, publishes its brain/game.toml and brain/events.toml as its live config, which ASE Brain's services read at once, then runs ase sync, which overwrites Brain's files in the checkout. With --dry-run it changes nothing. It commits nothing, so git restores the checkout; publishing the previous files again restores the config.

ase games adopt [OPTIONS]

Argument	Description
`--project <PROJECT>`	The game's repo checkout. Default `.`.
`--game <GAME>`	The game's id; by default the repo's name.
`--repo <REPO>`	The repo's path on its Git host (`my-org/neon`); by default the origin remote's.
`--dry-run`	Show what would change, changing nothing.

Examples

ase games adopt --dry-run
ase games adopt --game neon-drift --repo my-org/neon-drift

ase games show

A game's config from both halves, each value with where it lives, and the version live now.

Requires: a sign-in (ase login) or, in CI, a release credential.

Changes: nothing; it only reads.

ase games show [OPTIONS] <ID>

Argument	Description
`<ID>`	The game's id.
`--project <PROJECT>`	A checkout of the game's repo, for its own half. Default `.`.

Examples

ase games show neon-drift

ase games promote

Move a game from dev to live: from then on its tables only grow, and store targets take its releases.

Requires: a sign-in (ase login) with the studio permission manage_games (Owner and Admin).

Potentially destructive. Makes the game live: its tables only grow from then on, store targets take its releases, and it can no longer be deleted. It can't be undone: a live game never goes back to dev.

ase games promote [OPTIONS] <ID>

Argument	Description
`<ID>`	The game's id.

Examples

ase games promote neon-drift

ase games rename

Give a game a new display name; its ID stays. Studio owners and admins only.

Requires: a sign-in (ase login) with the studio permission manage_games (Owner and Admin).

Potentially destructive. Changes the name everyone in the studio sees for the game; its id and data stay. Rename it back to undo it.

ase games rename [OPTIONS] <ID> <NAME>

Argument	Description
`<ID>`	The game's id.
`<NAME>`	The new display name.

Examples

ase games rename neon-drift "Neon Drift Deluxe"

ase games delete

Delete a dev game: every service stops serving it now, and all its data is purged after 7 days unless it is restored. Studio owners and admins only.

Requires: a sign-in (ase login) with the studio permission manage_games (Owner and Admin). A dev game: a live game can't be deleted.

Potentially destructive. Every service stops serving the game at once. After 7 days its data, config versions and secrets are purged, and its id can never be used again. ase games restore brings it back within the 7 days; after the purge nothing can.

ase games delete [OPTIONS] <ID>

Argument	Description
`<ID>`	The game's id.
`--yes`	Don't ask to type the ID first.

Examples

ase games delete neon-drift

ase games restore

Bring back a deleted game before its purge.

Requires: a sign-in (ase login) with the studio permission manage_games (Owner and Admin). Room in the studio's plan for another game.

Changes: Brings a deleted game back as it was, before its purge, and services serve it again.

ase games restore [OPTIONS] <ID>

Argument	Description
`<ID>`	The game's id.

Examples

ase games restore neon-drift