OasisWManual 한국어
Section 10. Publishing and troubleshooting How-to Pending 4

Publish your game

Publishing puts your game at a URL that other people can open in a browser. You publish manually; this is not a job for the AI. This page covers everything from your first publish to opening the URL. To fix a game you already published and publish it again, see Republish and the primary build.

Before you start

  • Play the game from start to finish with ▶ Launch and fix everything that needs fixing. Publishing uploads the project exactly as it is at that moment.
  • If the editor tab has been open for a long time, reload it once. In our tests, publishing from a long-open tab failed after 0 seconds, and succeeded after reloading (1 run). See "Troubleshooting" below for details.

Publish

  1. In the left toolbar, click Publish / Download. The BUILDS window opens. If you have never published, it shows "You have not created any builds."
  2. Click Publish at the top right. The screen changes to PUBLISH NEW BUILD.
  3. Fill in BUILD DETAILS.
    FieldContents
    TitlePre-filled with the project name. Becomes the browser tab title of the public page
    Image boxClick it to upload a cover image. 720 × 720 pixels
    DescriptionPre-filled with the project description
    VersionEmpty. Entering something like 1.0.0 makes builds easier to tell apart later
    Release NotesDescribe what you changed this time. The build publishes even if you leave it empty
  4. Leave BUILD SETTINGS and SCENES as they are the first time. By default, script concatenation (Concatenate Scripts) and minification (Minify Scripts) are on, and all scenes in the project are selected. Engine Version was Current (2.23.1).
  5. Click the blue Publish button at the bottom. You return to the BUILDS window, and a new row appears in Build history.
  6. When the icon at the left of the row changes from an empty circle to a green check, the build is done. In our tests this took 9 to 90 seconds (3 successful runs). If it fails, a red ✕ appears.

The first successful build automatically becomes the PRIMARY (primary build), and its public URL appears in the Primary build field at the top of the window.

Open the public URL

Click the URL in the Primary build field, or click the open-in-new-window icon on the right, and the game opens in a new tab. Click the copy icon next to the URL to copy it.

The URL looks like this:

https://play.oasisw.ai/p/<project ID>/

This URL always opens the project's primary build (PRIMARY). If you change the primary build, the same URL opens the new build. The shortcut icon on each row of Build history links to https://play.oasisw.ai/b/<build ID>/, which opens only that build. The Play button on the project overview screen also opens the same public URL (checked on 2026-10-29).

The tab shows only the game, without the editor, and the tab title is the project name. After publishing, play the game from start to finish at this URL yourself. Whether something that worked in ▶ Launch also works at the public URL needs to be checked separately (see the caution above).

Who can see it

Who can open the game URL is set by Private Project in the project settings. Tests on 2026-10-29 (1 run each) showed the following:

Private ProjectWhen someone who is not signed in opens a /p/ or /b/ URL
On (the initial value for new projects)They get 403 with the message This project is private. Sign in as a project member and open it from the editor. The game files (config.json, scripts) could not be downloaded either. The game opens in a browser signed in as a project member
OffThe game opens

So to show your game to other people, turn off Private Project after publishing. Click the scene name in the top bar → Project settings and click the toggle. A confirmation dialog, Are you sure you want to make your project Public, appears, and the setting changes only when you click Yes. The same dialog appears when you turn it back on. ⋯ → Make public on the dashboard card appears to be the same setting. Pending Verify that it is the same setting as Make public on the dashboard

What you can do from a build row

Click … on the right of a row in Build history to open this menu:

MenuWhat it does
Set Primary BuildConnects this build to the public URL. It changes immediately, with no confirmation dialog. Grayed out if the build is already primary. See Republish and the primary build
ViewOpens BUILD DETAILS. Shows the status, creation time, duration, creator, and the error message if the build failed
DeleteDeletes the build. Pending Test whether deleting the primary build takes down the public URL

You can filter the list with Type, Format, Status, Branch, and Actor above the rows.

Troubleshooting

SymptomWhat to do
A red ✕ appears right after you click Publish, and View shows Failed to fetch dynamically imported moduleReload the editor tab and publish again. This failure happens when the site is updated after you opened the tab; in our tests, publishing succeeded right after reloading (1 run). The failed row stays in the list but does not affect the public URL
The game shows at the public URL, but the ball or character doesn't moveThis is a defect in the published version of games that use physics (see the caution above). For now, you can only confirm correct behavior with ▶ Launch
Other people get 403 and This project is private.Private Project is on. Turn it off as described in Who can see it above
In a game with two or more scenes, the public URL doesn't move on to the next sceneIn a build published on 2026-10-29 with two scenes (physics-1029, physics-1029 2), both scenes were included under the name physics-1029, and only one remained in the running game's scene list (1 run). Code that changes scenes by name (changeScene('physics-1029 2')) doesn't work in the published version. Pending Retest after the operations team's fix
You fixed the game and published again, but the game at the public URL hasn't changedFrom the second publish on, the primary build doesn't change automatically. See Republish and the primary build

Next steps

Source publish-help/publish.html