game commands list a seller’s Partner Center games, look one up by Store ID, XBOX title ID,
or name, create a game, and check on its creation job.
Each command acts on one seller, from --seller-id or your saved seller; see
Context. If you belong to several sellers, see
this known issue: these commands can
use another seller.
Commands
Arguments
Options
game get needs at least one of title-id, --store-id, or --keyword. The positional value is
always an XBOX title ID; when it looks like a Store ID, the error suggests the same command with
--store-id:
Listing and lookup
game list returns the seller’s whole catalog, and game get with --keyword searches all of
it. A large catalog can take a few minutes to read, and the command shows its
progress on stderr. There’s no paging option; page the output with
less or more. If a request fails, the command prints no partial results, and writes the
correlation ID to stderr. Each request times out after two minutes; to change it, set
XboxPartner:TimeoutSeconds (see Configuration).
Output
JSON output is onegames array. Each game has these fields:
game create and game job get write the creation job. Its game field, with the same fields,
appears once the game exists.
Table output
list and get accept --output table, with one row per XBOX title ID and these columns:
TITLE ID, STORE IDS, PRODUCT NAME, MSA APP ID, and PACKAGE FAMILY NAME. A title’s
Store IDs and other values share its row, and long values are truncated. create and job get
refuse --output table.
Details view
--details prints one block per title ID, with every game under it and all of its identifiers,
including the SCID and development sandbox, without truncating. Missing values show as -. With
--details or --output table, the result count and duration go to stderr.
Creating a game
game create asks before it creates the game; without a terminal, it needs --confirm. The CLI
can’t delete a game. If you belong to several sellers, check
the known issue first: the game can be
created in another seller.
The command sends the request once, waits up to two minutes for the creation job, and writes the
job to stdout. The job ID, correlation ID, and commands to check on the job go to stderr. If the
wait ends first, the job keeps running: check it with game job get, and don’t create the game
again.
If the request fails, stderr says whether a game might have been created:
- No game was created when the request wasn’t sent, or the service refused it, such as with a
400for a sandbox the game can’t use. Fix the problem and run the command again. - The outcome is unknown after a server error, a timeout, or a lost connection. Check
game listwith the command printed on stderr before you try again.
Checking a creation job
job get only reads, so you can run it as often as you like. A job that succeeded can still
report problems in its errors field.
Exit codes
Don’t decide whether to run
create again from its exit code. If stderr says no game was
created, fix the error and run it again; otherwise check with the game job get or game list
command it printed.
End-to-end example
Save a seller once, then create a game, which uses it:game create printed on stderr:
