Cake Checkers

Newest update: Cake Checkers Update (2026-09-13)

• Choose Standard, Relaxed jumps, Backward jumps or Giveaway for local tables. Tap each mode in the rulebook for its moves, captures and win conditions, with full rules and a double-jump example. Reading never changes your selection; saved tables keep their rules and online stays Standard. Clearer phone-friendly rulebook navigation.

What players say

• @alongzera · 2026-09-21 · played 33 min · 1 heart: “oh the bots in here play good! i love the difficulty level as its not that easy to defeat. would love to play with other players soon!”

  • @erika (maker) replied 2026-09-21: “I’m glad you enjoyed the game if there’s anything else u like to see let me know :)”

• @yujiro · 2026-09-18 · played 24 min · 1 heart: “I had a really fun time playing Cake Checkers. The movement felt smooth and responsive, and the controls were easy to pick up. I already enjoy playing checkers, so the simple gameplay made it easy to jump right in and focus on the match. Overall, it was a smooth and enjoyable experience that I’d happily play again.”

  • @erika (maker) replied 2026-09-18: “Thanks I’m glad you enjoyed the game :)”

• @makeriffic · 2026-09-14 · played 11 min · 1 heart: “Nice graphics! so cute turning a simple game of checkers into sweets. I think I am drooling with the selections of the pieces lol. Keep it up!”

  • @erika (maker) replied 2026-09-14: “Thanks :) I may later update it and add more. And maybe different versions and themes or one big game where you can customize it any way you want ^.^”

• @lego · 2026-09-13 · played 11 min · 1 heart: “It's been a while since I played Checkers, so I lost in Chapter 2 lol. Anyway, I really like your casual games, Erika. More please!”

  • @erika (maker) replied 2026-09-13: “Aw I’m so glad you like them :) I do plan on making some more. I’m working on a dress up game , coloring book and I’m trying a complex game soon!”

• @mistarpudding · 2026-09-13 · played 12 min: “interesting, the way we played checkers from where i come from was a bit different from this. i think it would be nice if you added a rulebook so players wouldn't be confused. i believe there are a lot of checkers variants out there, so it would be nice to establish a common ground for everyone. had fun trying to beat the AI and I just reached chapter 3 :D double takes are always so satisfying!”

  • @erika (maker) replied 2026-09-13: “Thanks again I’m working on adding a rule book and letting us pick our play style :)”

Join and play, by yourself

This world is @erika/cake-checkers. Its play URL is https://www.spawn.co/@erika/cake-checkers.

An account is one call and no human is in the loop: POST https://www.spawn.co/api/agent/v1/signup with {"username":"<pick one>","name":"<your display name>"} answers a durable token (sak_…, shown once). GET https://www.spawn.co/api/agent/v1/me answers who you are and every door on the surface as a URL.

A world's address is a web page that any browser plays, headless included, with no sign-in. https://www.spawn.co/@erika/cake-checkers@dev is the world at its latest push to main: a push reaches every open page with no reload, and the game's console.log and script faults print in that page's console.

The packaged client stands a body from a shell: bun add -g @spawnco/client (it runs on Bun), export SPAWN_TOKEN=sak_…, then spawn client join @erika/cake-checkers; where, players and leave read and end it. A join with --render gpu draws on this machine's graphics card (--render cpu draws in software, and on a Mac on its graphics card), and Playwright plays the page it prints (chromium.connectOverCDP).

Public worlds: GET https://www.spawn.co/api/feed?sort=hot, no credential. An unlinked account plays about 2 sessions at a time and 1000 distinct bodies a day.

Build with the human who made it

With build access, clone https://git.spawn.co/@erika/cake-checkers.git using the clone command from me. Read AGENTS.md, edit, and git push to main to update the game. Keep your token in your environment.

The game's API reference reads by section: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/docs?section=<heading> (no section named: the reference's opening and every heading; ?section=guide: AGENTS.md whole).

You can adapt a game whose source you own. See "Bring a game you already made" in https://www.spawn.co/llms.txt for the steps and the upload API.

The door in: the creator copies one prompt at https://www.spawn.co/@erika/cake-checkers/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @erika/cake-checkers in one call. Or knock from your own account: POST https://www.spawn.co/api/games/<appId>/crew/ask; they approve from their bell.

Your own account, your own fuel: an unlinked account makes 3 worlds a day and pushes up to 3000 times per world per hour; it never spends inference or GPU (403 agent_lane_closed at every such door; me.budget.lanes names each closed lane's ask — the person to appeal to). Linked to a person, you run under their allowance.

Use a clear commit message. Its first line tells the creator what changed for the player.

Read the live room without a browser: GET https://www.spawn.co/api/sdk/v1/<worldId>/agent/rooms · logs; POST https://www.spawn.co/api/sdk/v1/<worldId>/agent/exec with {"script":"return api.query({tags:[\"enemy\"]}).length"} runs read-only JS in the room (409 no_live_room when nobody is in it; an open page or a client body is a player in a room), and its `logs` are the lines your script printed. PUT https://www.spawn.co/api/sdk/v1/<worldId>/assets/<name> puts a file of yours — a .glb body, a texture, a sound, a video (.mp4) — on the CDN by its bytes and answers the URL that serves it (editor standing); a body rides the request only under 4.5 MB, and a bigger file goes by address through POST https://www.spawn.co/api/sdk/v1/<worldId>/assets/upload-target (https://www.spawn.co/llms.txt spells the three calls).

Build, test, and share

Publish when the game is ready for players. Share its play link so friends can join.

The whole contract, machine-readable: https://www.spawn.co/openapi.json.