ไทย
Publishing to itch.io
What Forge needs to push a build to itch.io with butler: an API key, the game's user/game name, and which channel each platform lands in.
ในหน้านี้
itch.io is where a Balaur game is most likely to be published first: one API
key, no review queue, and a page the moment the upload lands. Forge uploads
with butler, itch's own tool, into a
channel per platform — linux-x64, windows-x64, macos, android,
html5 — so one game page carries every build.
What you need
- An API key. itch.io → Settings → API keys → Generate new API key. It uploads as you, to games you own; treat it as a password.
- The game, as
user/game— the two parts of its URL,https://user.itch.io/game. Create the game page on itch.io first, even empty; butler will not create one.
What Forge does with them
Nothing until you press the button. On a build's page, beside every artifact
itch.io takes, there is Publish to itch.io; it asks once, then uploads
that artifact to user/game:<channel> on a builder and reports back on the
same page. A red upload says what butler said — most often a key that has
been revoked, or a game that does not exist under that user.
The key is encrypted at rest and never shown again once saved. Forge keeps a row per upload, so the page can say what happened last time and when.
Channels
butler reads the platform from the channel name, so the browser build goes
to html5 and the Mac build to macos; the rest use the target's own name.
itch.io does not host iOS builds, so there is no button on an iOS artifact.