Publish and update games on itch.io by creating a project page and uploading builds with butler, its command-line tool. Organize platform-specific channels, assign version numbers, preview changes, and upload only changed files during updates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Publish and update a game on itch.io: create the project page and upload builds with the butler CLI (butler push) to named channels. Use for itch.io publishing, butler push, channel naming for Windows/macOS/Linux/HTML5, versioning uploads, or shipping a jam or release build to itch.io.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Get a build onto an itch.io page and keep it updated. The page is created in the browser; all
uploads go through butler, itch.io's command-line tool, with one command you'll use
forever: butler push. butler diffs against the previous build and uploads only what
changed. Deep CI/CD and flag detail lives in references/butler-ci.md.
butler push, choosing channel names, versioning uploads, or
shipping a jam/demo/release build to itch.io.butler push, butler login, channels, .itch.toml, "publish on itch",
"upload to itch".When not to use: publishing on Steam (use steam-publish); jam scope/planning (use
game-jam — this skill is only the upload mechanics); building the game itself (engine
skills).
itch.io/game/new — butler pushes only to a page that
already exists. Set the Kind of project: keep Downloadable for native builds, or
choose HTML for a browser-playable game (this is required for web builds — see
Pitfalls). Set pricing and keep visibility at Draft (or Restricted for testers) until
the page is finished: the first public publish puts it on Most Recent once, and it
cannot go back to the top later.itchio.itch.io/butler, add it to PATH,
then butler login (opens a browser to authorize). Verify with butler version. For
CI, use BUTLER_API_KEY instead — see the reference. (The itch desktop app also has a
graphical push screen that uses its own bundled butler, if the user prefers no CLI.).zip of that folder), not an installer and not a
pre-compressed archive of archives (hurts patching; see Pitfalls).butler push <dir> <user>/<game>:<channel>. <user>/<game> is
the lowercase page address (finji.itch.io/overland → finji/overland). The channel name
determines the platform tag (see Patterns). The first push uploads everything; later
pushes to the same channel upload only the diff.--userversion 1.2.0 or
--userversion-file build.txt so you control the version string players and the update
API see.butler status <user>/<game>
to see channels/builds and butler push-preview to see what a push would change before
sending it.butler push# butler push <directory-or-zip> <user>/<game>:<channel>
butler push ./build/windows leafy/my-game:windows
butler push ./build/mac leafy/my-game:osx
butler push ./build/linux leafy/my-game:linux
butler push ./web leafy/my-game:html # browser build (also set page Kind = HTML)
Substring in channel name -> auto-applied tag:
win / windows -> Windows linux -> Linux
mac / osx -> macOS android -> Android
Multiple platforms in one channel are allowed: e.g. a Java jar:
butler push ./jar leafy/my-game:win-linux-mac
Convention: lowercase words separated by dashes (windows-beta, osx-demo, soundtrack).
Tags are only the INITIAL guess — fix them anytime on the Edit game page (then Save).
There is no tag for CPU architecture: name the channel (windows-arm64) if you ship several.
butler version # print version; confirms install + PATH
butler login # authorize this machine (opens browser)
# Set an explicit version string instead of itch's auto-incrementing integer:
butler push ./build leafy/my-game:windows --userversion 1.2.0
butler push ./build leafy/my-game:windows --userversion-file build_number.txt
butler status leafy/my-game # list channels + latest builds/versions
butler push-preview ./build leafy/my-game:windows # NEW/MODIFIED/DELETED/SAME, uploads nothing
# Hide a brand-new channel from the page until you're ready (NEW channels only):
butler push ./build leafy/my-game:windows-beta --hidden
# Exclude files from the upload without copying the folder (--ignore is repeatable):
butler push ./build leafy/my-game:windows --ignore '*.pdb' --ignore '*.dSYM'
# Preview exactly what would be sent, without sending it:
butler push ./build leafy/my-game:windows --dry-run
.exe/.msi)
defeats patching and the itch app's auto-update, and may need admin rights players don't
have. Push the extracted, runnable folder instead..zip. butler auto-unzips it and pushes the contents
(to avoid a "zip in a zip"). Pass --no-auto-unzip only if you truly want the zip uploaded
as one opaque file.index.html at its root and
must stay within itch.io's limits: at most 1,000 files, 500 MB extracted, 200 MB per file,
240 characters per path. The CDN is case-sensitive, serves the game from a subfolder (so
paths starting with / break — use relative paths), returns 403 for folder URLs, and only
allows HTTPS requests to other domains. HTML5 pages take payment only as donations; sell a
web game by making the page Downloadable.invalid target (bad user) / (bad game). The target must match the page address
exactly — subdomain for the user, URL slug for the game, all lowercase — and the page must
exist already..app loses its structure. Push the .app folder itself (or the folder that
contains it); butler keeps the bundle as the top-level directory and marks Mac/Linux
executables as executable by default.--hidden on an existing channel errors. It only applies when the push creates a new
channel. Unhide later from Edit game.windows and win-final are different channels and
create separate downloads. Decide your channel names up front and reuse them.BUTLER_API_KEY printed in a public log is compromised — revoke
it immediately on the API keys page. See the reference for safe CI usage.BUTLER_API_KEY, automated install via broth, the
full flag list, and the update-check API, read references/butler-ci.md.itch.io/docs/butler (installing, login, pushing);
itch.io creator docs — itch.io/docs/creators/html5 (web build limits) and
itch.io/docs/creators/quality-guidelines (tagging, AI disclosure, delisting rules).steam-publish — the same game on Steam via SteamPipe (often shipped alongside itch.io).game-jam — most jams are hosted on itch.io; this skill handles the upload step.prototype-fast — share an early prototype on a Draft/restricted itch page for playtesting.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Implement reusable decision systems for game characters using behavior trees, which organize conditional actions, and Utility AI, which scores available choices. Build either approach or combine them to control patrols, combat, targeting, and needs-based behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design game audio with grouped volume controls, music that responds to gameplay, and varied sound effects. Plan how music lowers during dialogue and how events follow the beat, using principles that can be adapted to different game engines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and debug Rust games in Bevy using ECS, a way to separate game data from behavior. Organize apps and plugins, query entities, control execution order, and fix conflicting data access or frame-dependent movement.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and tune game cameras for smooth 2D following and 3D viewing. Covers motion smoothing, look-ahead, level boundaries, wall avoidance, and framing multiple targets, with techniques that apply across engines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design the core rules of a card game, including decks, hands, discards, drawing, shuffling, turns, and resource costs. Represent card effects as data and define their resolution order so card movement and gameplay outcomes follow explicit rules.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and prepare consistent game artwork, from sprites and backgrounds to UI icons and 3D briefs. Organize asset requirements, generate or source related visuals, standardize files, and check their appearance and technical fit inside the game.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.