Skip to main content

arc unstable game delete

Delete the game.

arc unstable game delete is under arc unstable, whose commands may change in any release of the CLI. It was arc delete until 1.0.37, and it moves to arc game delete once the arc game commands are settled.

Usage​

arc unstable game delete

Delete the game

Options:
-h, --help Show help [boolean]
-v, --version Show version number [boolean]
-j, --json Format output as JSON [boolean] [default: false]
-q, --quiet Output only errors [boolean] [default: false]
-C, --cwd Set the working directory [string] [default: "."]
--yes Don't ask first [boolean]

Description​

Deletes the project's game from Arcadible: the game with the project's id. It takes no handle or id on the command line, so it only ever deletes the game of the project it runs in, or the one -C names.

Deleting a game is permanent. The game and all of its builds are removed from Arcadible at once, and it can't be undone.

Only the game's owner can delete it, so it needs you to be logged in. What deleting does to the game's handle, its repository, and its id is in Delete a game; Studio's Delete game does the same.

At a terminal, it asks before deleting, naming the game by its title, else its handle or id, and anything but yes leaves the game as it is (Left as it is.):

? Delete Star Drift? The game and all of its builds are deleted right away. This can't be undone. (y/N)

Anywhere else (a script, CI, an agent, a pipe, or with --json), there's no one to ask, so it's refused unless --yes says it's meant, before anything is read or sent:

$ arc unstable game delete
Delete aborted.
This can't be undone, so say it's meant:

arc unstable game delete --yes

Code: argument_invalid
https://developer.arcadible.com/references/errors#argument_invalid

--yes is only ever an option on the command line: arc.config.toml can't set it.

After that refusal, and before it asks, it checks, in order: that the project has an id (game_id_missing), and that you're logged in (not_logged_in). Once it's answered yes, a game that was never deployed, was deleted already, or belongs to another account is refused as game_unavailable.

It leaves your project's files as they are, and says so:

$ arc unstable game delete --yes
Deleted Star Drift.

Your files are unchanged: arcadible.toml keeps the deleted game's ID.
To deploy it as a new game, delete the `id` line and run `arc init`.

Output​

It prints the game it deleted, and what's left in the project. With --json, the deleted game's id:

{ "game": "757c395c-11e1-419b-943a-6366882443f7" }

With --quiet without --json, it prints nothing.

CodeWhen
0The game was deleted, or you answered no and it was left as it is
1It wasn't deleted: --yes was needed, you're not logged in, the game isn't yours or isn't there, or the project has no id or can't be read
130You cancelled the question with Ctrl+C, and it was left as it is