Skip to main content

Arcadible Studio

Arcadible Studio is where you see your games once they're on Arcadible: their plays and likes, their builds and releases, and what their store pages are made of. You log in with your Arcadible account.

A drawing of Studio: a rail with Games, Builds, and Settings, and a game's Builds tab listing its releases Games Builds Settings Star Drift star-drift · public Overview Builds Repository Store 0.1.4 Production Published 0.1.4-beta.2 Staging Published 0.1.4-beta.1 Staging Failed 0.1.3 Production Published manifest_invalid

Studio shows what your project made. It doesn't edit games: a game is created by its first deploy, and its store page changes when you deploy. So there are no forms to keep in step with your repository.

Studio has three pages: Games, Builds, and Settings.

Games​

Games lists every game on your account, public and unlisted, with its Visibility, Plays, and when it was last Updated. While one of your games is public and your own profile is unlisted, a note above them says players can't find you or your other games from it, with Make it public, which opens your profile's settings.

A game with no production release shows Not released in place of its visibility, and is named and pictured by its newest build, since the game's own title and icon come from its first production release.

New game shows the commands that create one with the CLI. A game appears in the list once its first build is published.

A game​

Open a game for its header, with View in store for its store page and Play for its play page, and four tabs. For a game not released yet, the header shows Not released, and Play opens its newest prerelease.

Overview​

  • Next steps, until the game is released and public: Release it to production, which links Releases; Make it public, which links Going Public; and Release from GitHub (optional), which opens the Repository tab. Each step that's left shows what does it, such as arc deploy or visibility = "public", and done steps are checked. The list goes once the first two are done.
  • Plays, counted from production builds, and Likes.
  • In production: the version players get, with its channel and when it was deployed.
  • Latest staging build: the newest prerelease.
  • Delete game. See Managing a Game.

Each version links to its build, and Play opens it.

Builds​

Above the builds, a line for each release on its way, with its status (Pending or Processing) and version, and one line, Releases to fix: N, for the failures since the game's last published release. Show why opens the newest five, with See all under Failed when there are more. Each failure shows its version and channel, where it came from (arc deploy or GitHub), what happened, its Reason, and How to fix, which links to its reason's entry.

Below them, every build of the game, newest first.

Store​

The store page as players see it, rendered by the store's own page from a build's values. Choose Production or Staging, each with its version: the newest build in that channel, and disabled without one.

  • Production is what players see.
  • Staging is what they'll see once that version is released to production. Before a game's first production release, the tab opens on Staging, and says that until then players see only "Not released yet".

Play with the version, such as Play 1.2.0, opens that build. The preview's screenshots and description images open full screen.

Below the preview:

  • Details: that build's title, short title, tagline, bio, visibility, genres, controls, and orientation, and the game's handle.
  • Artwork and gallery: the artwork, and every gallery file by its file name, each opening full screen.

With no builds, the tab shows No builds yet. It's read-only: to change the store page, edit your project and deploy a release version. Your Store Page links to Your Store Page.

Repository​

The GitHub repository the game releases from, with Disconnect repository. With none, it lists the repositories your GitHub installations can access, so you can Connect one; with no installation yet, Go to Integrations opens Settings to install the app. A repository without the release workflow shows No release workflow. See Deploying from GitHub.

Not published yet​

A game whose first release failed doesn't exist yet, so its link shows Not published yet with the failed releases. Fix the cause and deploy again.

Builds​

Builds lists the builds of all your games, with tabs for All, Production, Staging, and Failed. Failed keeps every release that failed, with its reason. Above the builds are the same lines as on a game's Builds tab, for all your games: one for each release on its way, and Releases to fix: N.

Open a build for its Game, Version, Channel, Size, when it was Deployed, its Origin (a link to its files, outside the play page), and its Manifest: the arcadible.json it was deployed with. Play this build opens its version link.

Settings​

  • Integrations: the Arcadible GitHub App. Install GitHub App installs it on a GitHub account or organization, and Connect an existing installation connects one installed earlier. Each installation has Manage on GitHub and Disconnect. Disconnecting stops releases from its repositories; the app stays installed on GitHub. Uninstalling the app on GitHub disconnects its games' repositories too: after installing it again, connect each one again on its game's Repository tab. See Set it up.
  • Profile opens your settings on arcadible.com, which Studio shares: your name, handle, profile picture, background, poster, tagline, bio, and homepage, shown on your developer page, and whether your profile is public.

Studio's words and the docs'​

Studio names some things differently from these docs:

StudioThe docs
Builds (the page)Builds, and the releases still on their way or failed
arc deployA direct deploy
GitHubA git deploy
In productionThe latest build in the production channel
Latest staging buildThe latest build in the staging channel
StoreThe store page

See How Arcadible Works for each term.