Push a Build from the Editor

What pushing does#

Pushing a build is the only publishing action that happens in the editor. The editor exports your project into the three build artifacts (client PCK, server data zip, game config), hashes them, uploads them to the platform, and the platform verifies and stores them as a new Ready build. Everything after that — going live, hotfixes, rollbacks, beta, hosting — happens on the Creator Dashboard.

Pushing never changes what players see. A freshly pushed build sits in the build list until you deploy it. That makes it safe to push often: a bad build costs nothing until you promote it.

Before you push#

1. Sign in. Open the Account menu in the top-right of the editor and sign in with your Vastopia account. The popup tells you if you are signed out or if your session expired.
2. Have a linked game. Every project created by the editor carries a platform game ID in project.vastopia under [platform] game_id, and the editor registers that game with your account each time you open the project while signed in. You do not need to create the game on the website first — it appears on the dashboard with your first push.
3. Save your work. The export reads files from disk. Press Ctrl+S in any editor with an unsaved * marker first.

First time: publish the listing#

The first time you open the popup for a game that has no listing yet, its title is Publish Game and it shows a single Basic Info card:

1. Click Publish in the top-right of the editor.
2. Check the Name field. It is prefilled with the project name and is the name players see in Discover.
3. Click Publish.

This publishes the game's listing (public visibility) so it can be found once it goes live. The status line reads "Published! Create a build to send it live.", the popup switches to its Update Game view, and the top-right button's label changes from Publish to Update from now on.

Create a build#

With the listing published, the popup shows three cards: Current Version, New Build and Build History.

1. Click Update (top-right) to open the popup. Current Version reads Live: v3 for a live game or No build deployed yet.
2. In New Build, type a Build name — something you will recognize in the history later, such as Combat rework or Beta 3. If you leave it empty the editor names it Build YYYY-MM-DD.
3. Optionally tick Incremental (bundles) to upload only content that changed since the last push. See Builds and Versions for what that implies.
4. Click Create Build.
5. Watch the progress line (below). When it finishes, the editor opens your browser on the game's Update tab in the dashboard so you can deploy the build immediately.

You can keep editing while the push runs, but do not close the editor: the upload runs inside it.

What happens during a push#

The New Build card replaces its fields with a phase line, a progress bar and a detail line while a push is running:

Details worth knowing:

• A PCK of 16 MiB or more is uploaded as a resumable multipart transfer (8 MiB parts, three in flight). Its progress is saved on disk, so a dropped connection only costs the parts that had not finished.
• If the pack is larger than 1 GB, the status line warns you: that is the download every player takes before they can play.
• After a successful push the editor also syncs your item catalog (names and icons) to the dashboard's shop tools and saves a copy of the project source to the cloud for the project wizard's "continue on another machine" download. Both are best-effort and never fail the push.
• The platform limits each account to 60 build requests per hour. Creating a build and each Play Local deploy draw on the same budget.

When the push completes, the status line reads "Build 'Combat rework' sent in 4m 12s — opening the dashboard to push the update.", Build History refreshes, and the dashboard opens on /dashboard/<gameId>?tab=builds.

After the push#

• Build History (in the popup) lists builds newest-first as #7 Combat rework with the date, the size and a status badge in upper case: READY, BETA, ARCHIVED, DELETED or FAILED. The build that is live shows its version label instead — v3, or v3 patch after a hotfix.
• Open Dashboard jumps to the same Update tab the editor opened automatically.
• Next to the top-right buttons, a small badge reads Live (v3) when a version is deployed or Test when nothing is live yet. It refreshes after every push.
• Play Live (top bar) becomes enabled only once a version is actually deployed. It launches the standalone game client signed in as you and connected to your live server.

Testing a pushed build#

A Ready build is stored, not running. There are three ways to play it before it reaches players:

Common failures#

The popup replaces the progress bar with a red panel describing the error and offering one or two recovery buttons. Retry Upload re-sends the pack that was already built without re-exporting and resumes any multipart parts that already landed. Rebuild && Upload exports from scratch.

A build that never finalizes stays uploading (hidden on the dashboard) until a cleanup job marks it failed. It does not count against anything; just push again.

With AI (MCP)#

The same pipeline is available as tools: export_pck, build_server_package, create_build, upload_build_artifacts (or upload_pck_multipart for large PCKs) and finalize_build. list_builds shows the result, deploy_test_build runs a Ready build on a test server, read_server_logs with mode:"test" reads its output, and get_deploy_status / wait_for_deploy follow any deploy the platform is running for the game.