Make your fighter.

Three ways to make a fighter

Whichever way you choose, the fighter is registered to your own Google account, up to three fighters per account. Pick the way that fits how much you want to do yourself.

To choose every concept and motion yourself with the local creator toolkit, follow the guide from Make it yourself below.

Make it yourself: quick start

You make the creative choices. Your assistant runs the local tools, prepares the files, and shows the results. You do not need to write a character manifest by hand.

1. Open a new conversation in Dot, Codex, or another assistant that can access local files and run tools on your computer.
2. Paste the prompt below. Replace the cat boxer with your own idea and attach a reference image if you have one.
3. Review the fighter’s front before making animations. A browser-only chat without local tool access cannot run these tools; if it hands you the finished files, check and upload them on the site.

Read https://github.com/jeonghwanko/oddbout-starter/blob/codex/game-context/START-HERE.md
I want to make a fighter for ODDBOUT: a small cat boxer with red gloves and an oversized blue hoodie.
Use the current game requirements and the bundled creation workflow. Check which image and animation tools I can use with my own accounts.
Show me the full-body front first. Keep the red gloves and oversized hoodie. After I approve the look, show movement, attacks, and reactions in separate review groups.
Let me review the final files before registration.

The sample describes a new fighter; it is not a request to generate anything until you send it to your assistant. No ODDBOUT sign-in is needed for local concept work.

What you need

• A computer with local tool access. Keep the project in a folder your assistant can read and write.
• Git, Node.js 22.12 or later, and Python 3.11 or later. Your assistant can check the installed versions before setup.
• Your own image and animation access. Tool installation does not include a generation subscription or unlimited usage.
• An idea, reference images, or both. Use references you created or have permission to use, and say what each image is for.

Choose a generation route

Tell your assistant what you can currently access. Image and animation access are checked separately. These are starting recommendations; your explicit choice takes priority.

Agree on what to do if a tool is unavailable or reaches its limit. The assistant should not silently change providers or move to a paid API. There is no fixed completion time: generation, revisions, and reviews vary.

Set up the tools

For the guided route, ask your assistant to set up the linked starter kit. If you prefer to run the setup yourself, use these commands in a terminal. They install the pinned tools in this checkout.

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

Use the main branch. A GitHub ZIP omits the submodule contents. sprite:setup fetches the pinned sprite-gen revision and creates its own Python environment. sprite:status checks installation, not subscription or sign-in status.

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

npm run plugin:build
codex plugin marketplace add <path printed by the builder>
codex plugin add oddbout@ai-fighter-local

Confirm readiness

npm run creation:context
npm run sprite -- workflow --kind sprite

Your assistant reads the current game context and get_fighter_spec sections overview, creation, and guide. It reads the schema when packaging. A workflow result of needs-input (exit code 2) means an account or route choice is still needed. Start generation only when that stage is ready.

Create the look

Describe the parts that make your fighter recognizable: silhouette, face, outfit, colors, equipment, and attitude. A short paragraph is enough to begin. A name and biography can come later.

• Identity reference: keep this face, body, or costume.
• Outfit reference: use this clothing, these colors, or this equipment.
• Style reference: the feel you are after. The colouring itself is always ODDBOUT’s: flat cel colours with one soft shadow step.
• Pose reference: borrow the stance or motion, not the whole character.

The front becomes the fighter’s picture on the site and its face in matches. The motions are drawn from the side view, which faces right in an orthographic view with a 16° camera elevation. The toolkit handles the shared scale.

Make it move

Once you choose the look, review movements in groups. Each group is prepared and shown together. An approval advances the work; a request such as “good, but change the hands” asks for a revision first.

If you want the assistant to handle later groups without review stops, say exactly which ones. You can still request a targeted change. Silence does not approve an unfinished group.

Review & package

File validation and visual review answer different questions. A valid file can still contain sliding feet, duplicated poses, or the wrong face. Watch the actual final animation before registering.

npm run fighter:pack -- path/to/plan.json
npm run validate -- output/my-fighter/fighter.json

output/my-fighter/
  fighter.json
  assets/
    idle.webp
    walk.webp
    run.webp
    ...

Register your fighter

1. Connect your ODDBOUT account. The ODDBOUT plugin, or an agent connected in My agents, signs you in with your own Google account. Use the same account as on the creator page. The workspace needs no separate sign-in.
2. Ask to register the approved package. The assistant validates the manifest and actual files, then uploads them with prepare_fighter_registration, upload_fighter_asset and submit_fighter_registration.
3. Wait for the server result. A queued upload is not a completed registration. The assistant checks the submission with get_fighter_submission until it returns a final result.
4. Confirm the fighter in your account. Completion includes registered, a fighterId, and its current availability. No invitation or manual pre-approval is required. A file-validated fighter starts Not entered: you can practise with it in the arena, and it stays out of other people's cups, ranked duels and public lists.
5. Send the front. The assistant uploads the chosen front and its faces as the fighter’s profile set (submit_profile_set). The home page shows the fighter once an operator approves the set.
6. Check every motion and enter. On your fighter's page, open All motions: play each motion, slow it down or step through it. Then press Enter ODDBOUT; other people can now play against your fighter in cups and ranked duels. If the site asks for the front first, ask your agent to send the profile set. A new package returns the fighter to Not entered until you enter it again.

Make it with another tool

Any tool can make a fighter as long as the package follows the spec: fighter.json and its still, transparent WebP sprite sheets under assets/. Check it here first: nothing is sent and no account is needed.

1. Follow the spec. Start from the example fighter.json; the full spec ↗ explains every field.
2. Check it here. Drop the ZIP or the folder below. Each problem names its motion and cell; copy the list for the agent or tool that made the package.
3. Upload it. On My fighters: New fighter → Other ways → Upload a finished package. After the server check, review the motions and enter the fighter.

Required motions

Optional motions

All images

One image

Images

Longest side

One motion

Sign in and upload it →

Revise & resume

Name the motion or image you want to change, what should change, and what should stay. Keep approved versions; do not regenerate the entire fighter for a small edit.

“Resume the cat boxer. Keep the approved face, outfit, and run. Only shorten the combo recovery. Show the revised combo before repackaging.”

The assistant keeps a local work note with selected file paths, versions, feedback, and the next review group. For a new conversation, point it to the same project folder and that note. A body or costume change may affect several animations; review the affected groups again. Metadata-only edits need fresh file validation, not another review of unchanged art.

Some changes need no conversation. Open the fighter on My fighters: four buttons open an editor. Profile changes the name, introduction and match lines; Animation downloads the current package and uploads a fixed one; Combat sets how the fighter fights; World holds its story and relations. Profile and combat changes keep the fighter entered. A new package returns it to Not entered until you check its motions again. On All motions, Ask for a fix copies a request to paste to the agent that made it.

Troubleshooting

Technical reference

The table below explains the current 11-motion set. The live game context and schema remain the source of truth. Your assistant refreshes them at the start, on resume, before each new group, and before packaging. If requirements change, preserve the existing work and review the differences.

The appearance baseline uses a 400 px body height; this is not the same as sheet-cell height. The optional clips skill, entrance, and victory can be added to the 11. Assets use one shared coordinate and scale reference. Artwork defines the look and motion; HP, damage, executable code, and gameplay rules are not creator-supplied character fields.

• Starter document with game context ↗
• Full creation workflow and packaging ↗
• Manifest and animation contract ↗
• Gait review guide ↗
• Registration and availability ↗

The toolkit’s repository, commands, and file contract still use the name “ai-fighter”. They are the creation tools linked from ODDBOUT. Guide reviewed: 3 November 2026.