Skip to content
CLI manual

thrungames upload

Upload a build from a folder or a .zip file

MCP tool: upload_build

Zip a folder (or take a .zip), check it against the upload limits, and upload it as a new version of your game. Resolution order, first match wins: path the argument, THRUNGAMES_PATH, "root" in game.json, then "." game.json the working folder's, else the source folder's, else the zip's files every file in the folder except .git, node_modules and dotfiles, narrowed by "include" and "exclude" in game.json (a .zip is uploaded as it is) version --version, THRUNGAMES_VERSION, "version" in game.json, then git describe --tags --always in the source folder size --width/--height, then game.json, then the current version's (an Immersive game with none gets 960x600) submit --submit, or THRUNGAMES_SUBMIT=true (or 1) game with an upload token (tgu_...) the token's game; otherwise --game, THRUNGAMES_GAME, then "name" in game.json Without --submit the version stays a draft you can preview and submit later with "thrungames versions submit".

Usage

thrungames upload [path] [flags]

Examples

shell
thrungames upload ./build --game space-dodger --version 1.2.0
thrungames upload game.zip --game space-dodger --submit

Flags

Flags of thrungames upload
FlagTypeDefaultDescription
--gamestringgame slug or id (env THRUNGAMES_GAME; default: name in game.json)
--heightintdisplay height in pixels (default: game.json, then the current version's)
--submitboolsend the new version to review (env THRUNGAMES_SUBMIT)
--versionstringversion name (env THRUNGAMES_VERSION; default: game.json, then git describe)
--widthintdisplay width in pixels (default: game.json, then the current version's)

Every command also accepts the global flags.