ODDBOUT

English | 한국어

Create a fighter with AI. Bring your character into the arena.

ODDBOUT is a fighting game where you play with a character you create. This repository contains the open-source tools for making that character. Work with an AI assistant to turn a description or reference image into artwork, animations, and a fighter package for the game. The tools and docs also use the name AI Fighter.

Play ODDBOUT · Manage your fighters · Site guide · Creation guide · Report a problem

Gameplay preview

Existing ODDBOUT gameplay. The subscription-based character creation workflow is still experimental; this clip does not show a complete creation run.

Watch the 10-second clip · Play ODDBOUT · Questions and feedback

Related MCP server: repo-verifier

What you can make

• Start with a short idea, reference images, or both.

• Review the artwork and animations with your assistant. Ask to change what you do not like while keeping the versions you have chosen.

• Build a package with all 11 required motions, check the files, and register it with your account.

• Play with your registered fighter directly or let the common AI controller take over.

The kit includes sprite-gen, creation workflows, validation tools, and an MCP server for connecting your assistant to the game. The game engine is maintained separately.

In this kit, "sprite-gen" means the sprite-gen engine and CLI pinned at vendor/sprite-gen, which comes from sprite-gen-agent, our fork of Alex Kim's sprite-gen. Commands, paths and the Python package keep the name sprite-gen.

Ways to make a fighter

Every way registers the fighter to your own Google account, up to three fighters per account. The first two need nothing installed; the third installs the generator from this repository on your PC; the last runs this whole kit. The site guide walks through each.

Register from Dots without a PC

For creation in a saved Dots VM, use the Dots VM entry point. The intended flow is one repository URL plus your creation request, using your own Grok subscription. The environment preparer runs the install recipe once; Dots then runs node dots.mjs --install once and node dots.mjs to resume the same pinned workspace. The source and preview-delivery checks remain distinct from login. This 0.5.5 candidate still requires actual saved-VM creation acceptance; unit tests or a parent-container run do not certify it.

Connect the hosted ODDBOUT MCP, sign in with Google, then select @ODDBOUT in your Dots conversation. The ODDBOUT plugin 0.6.0 or later already carries this connection; without the plugin, add it in ChatGPT Plugins as a custom MCP server (adding both shows ODDBOUT twice). Grok and Claude connect the same server from their connector settings, and My agents shows and disconnects every connection. The cloud connector handles account checks, file transfer and registration; no local MCP installation, API key or callback copying is needed. See cloud connection instructions for each host's endpoint and first-time setup. When the hosted generation tools are available, ODDBOUT can make the fighter on its worker at your request. Save the verified account ID, request key and job ID; after a timeout or disconnect, follow hosted job recovery to look up the same job by its ID or original key and refresh preview URLs without resubmitting. A connection or a returned URL does not prove that an image was displayed and reviewed. Creation in your own workspace still uses your selected generation account. The setup below is for running the creation kit in a workspace; it is not required to authenticate the cloud connector.

Create with the local kit

Use the ODDBOUT plugin for creation, review and registration from a PC or a supported Dots workspace. The same connected ODDBOUT account registers the result in either environment. A second AI Fighter Creator plugin is no longer required. See the unified plugin and migration guide.

Send the repository URL to your assistant in the prepared workspace. Add an idea or a reference image. For example:

Make a cat boxer in blue armor for ODDBOUT using this kit. Show me the concept first so we can get the appearance right. Then show me movement, attacks, and reactions in groups for feedback. When I choose the final result, validate it, register it with my account, and check that I can use it in the game.

Your assistant handles setup, generation, packaging, and file checks. You choose how the character looks and moves. Local creation can begin before you sign in to ODDBOUT.

What you need

Using the local kit takes setup and several rounds of review. Time, usage limits, and costs depend on your provider and how many changes you make. You choose the provider with your assistant. Switching providers or using a paid API needs your agreement. A browser-only chat needs a connected execution environment for the full workflow.

Make and review, one group at a time

Your assistant shows you actual previews and waits for your feedback after each group. It revises the affected assets and keeps your other selections. You can also ask it to handle later groups on its own. Alongside file checks, the assistant reviews character consistency, movement, foot contact, and timing. You review the results before moving on.

See the full creation workflow for generation, revision, and packaging.

Set up the kit yourself

For a Dots VM, start with Dots bootstrap, doctor and resume and the saved-environment Start instructions. The offline entry point is node scripts/dots-workspace.mjs doctor --workspace <absolute-workspace>; installation is explicit with bootstrap --install. A Git URL alone does not authorize generation. Start from main (below) and record its actual commit. The Dots workflow reports unsupported image-output contracts as blocked; it does not read protected Codex sessions or claim that login/installation proves image generation or parent delivery.

Use the main branch, which contains the public service configuration. For a new installation:

git clone --branch main --single-branch https://github.com/jeonghwanko/oddbout-starter.git
cd oddbout-starter
npm ci --ignore-scripts
npm run sprite:setup
npm run sprite:status

Installed before 2026-10-29 from codex/creator-hosting? That branch is frozen, and the kit's readiness check now stops a checkout on it as the wrong branch. Commit or set aside any local changes, then move the checkout to main (a plain git checkout main fails in a single-branch clone):

git remote set-branches origin main
git fetch origin
git switch -C main origin/main
npm ci --ignore-scripts
npm run sprite:setup

Setup downloads the pinned sprite-gen source into this checkout and installs it in a dedicated Python environment. Use Git clone; the GitHub source ZIP does not contain the submodule files. The status command checks installation, not generation access or quota.

Setup also fetches the outside tools sprite-gen needs, without sudo: img2webp with -exact (libwebp 1.6.0, SHA-256 pinned, placed in the kit's environment when your system has none or an older one such as Ubuntu 24.04's 1.3.x) and RIFE for smooth walk and run loops (sprite-gen rife install, about 430 MB download). Install ffmpeg yourself first: sudo apt install ffmpeg (Ubuntu/Debian), brew install ffmpeg (macOS) or winget install --id Gyan.FFmpeg -e (Windows). Setup and sprite:status list each tool as ok, missing or broken with the command that fixes it. A Linux machine without a GPU also needs sudo apt install libvulkan1 mesa-vulkan-drivers for RIFE; without RIFE, loops are cut as filmed with a warning. Keep an in-progress character workspace in place and avoid pulling repository updates during creation.

To connect the tools, follow the local Codex plugin guide: npm run plugin:build, then the printed codex plugin marketplace add … and codex plugin add oddbout@ai-fighter-local. The older manual MCP connection (node scripts/print-install.mjs) remains for compatibility. Other local hosts can connect mcp/stdio.mjs with AI_FIGHTER_ROOT set to the checkout.

The unified plugin guide covers the portable source package. A local plugin installation does not mean the plugin is installed in Dots or listed in a public directory.

Register and play

When you choose the final result and ask to register it, your assistant checks the package and registers it through your connected ODDBOUT account: the ODDBOUT plugin, or an agent connected on My agents, signed in with your Google account. You do not need to set up a backend or get service API keys. Older local tools without that connection sign in with npm run login.

The server checks your uploaded files and registers your fighter in production: you can watch it and practise in the arena. Your assistant checks the result to confirm the registration. The queue can take time to process. To let other people play against your fighter in cups and ranked duels, open All motions on its page, check each of the 11 required motions and press Enter ODDBOUT.

Open the creator page with the same Google account to see your fighter; its My agents tab manages your connected agents and your PC. See registration, limits, and profile edits for details. Keep login links, callback URLs, and session files private.

Help and contributions

If setup, generation, sign-in, registration, or gameplay fails, open an issue with the failing step, expected and actual behavior, error message, and tool version or commit. Exclude credentials and private files. For generation or upload timeouts, check existing requests and outputs before retrying.

Bug reports, clearer setup instructions, and reproducible examples are welcome. Read AGENTS.md before using an assistant to change this repository. Pull requests target main and merge only after the test workflow passes; npm test runs the same suite locally, including the strict type check of api/, worker/, mcp/ and scripts/.

Local development checks, after installing dependencies:

npm run spec:check
npm test
npm run validate -- examples/sparring-bot/fighter.json
npm run mcp:smoke

npm run test:fast skips the slow image-packing, proxy and Python-engine suites (npm run test:heavy runs only those); run the full npm test before a release.

The sparring-bot example is a geometric test fixture. These checks do not generate or register a character. Running matches on a self-hosted service requires the separate production game engine bundle.

License

The creator kit is MIT-licensed. The bundled sprite-gen submodule is sprite-gen-agent, our fork of Alex Kim's sprite-gen, with its own Apache-2.0 LICENSE and NOTICE. Generation providers have their own account and usage terms.