The Last Word Inn

Newest update: Four-Card Hand + UI Update (2026-09-28)

• Your hand now holds four Plus-Ones instead of three—two you want to admit and two you want to refuse.
• The new tavern UI is now your default view, with a plaque showing seats and laws, your hand fanned below, and the council desk as a side panel.
• Guest portraits and the parchment backgrounds load six times lighter than before.
• The council can now seat up to 22 visitors instead of 17.

Earlier update: The Press Kit (2026-09-23)

• A new Press creator tab lets you capture clean screenshots of the inn without any UI clutter.
• Crop captured shots to five different aspect ratios—original, wide 16:9, square, portrait, or tall—and zoom to frame your moment.
• Add up to three promotional overlays per shot: box-art titles, announcement pop-ups, or ribbons, with three themed palettes to choose from.
• Write captions and alt-text for each shot, with smart starter suggestions based on what you're capturing.
• Save up to eight shots per session in your browser, then download them as PNG or JPEG with or without overlays applied.

Earlier update: The Stability Accord (2026-09-23)

• Invite links now work reliably, letting friends join your table directly from a shared URL.
• World loading is more stable—fewer hiccups and faster recovery when something goes wrong.
• Better error messages tell you exactly what happened and how to fix it, so you're never left guessing.

Earlier update: The Wanderer's Return (2026-09-22)

• When you move between tavern rooms, your seat no longer gets stuck to the old furniture—the inn remembers where you belong and settles you properly.
• Card actions now respect each room's own clock, so switching taverns mid-turn won't accidentally silence your next move.
• Rejoining a game in progress now correctly reconnects you to your existing hand and round, even if you've been away.

Earlier update: The Guidance Update (2026-09-22)

• Players seated at the council table now receive gentle, context-aware hints about what to do next—when to inspect your hand, draft a rule, or cast your vote.
• After each round concludes, you can now review exactly which guests were admitted or refused and why, with the matching rule cited.
• The How to Play guide has been rewritten to show clearer voting math and explain how points persist even after the council loses.

What players say

• @neitantei · 2026-09-22 · played 14 min · 1 heart: “One of the most unique games I’ve played! I was reading the instructions and honestly didn’t get it at first 😂 But once I started playing, everything started to click. The background music and the tavern give the game such a chill and relaxing vibe. Really enjoyed it!”

  • @dandalruss (maker) replied 2026-09-22: “thanks, glad you enjoyed it!”

• @vladtheimpaler · 2026-09-22 · played 33 min · 1 heart: “Brother, the game looks epic, feels like im on medieval times! Only thing needs work is the instruction on how to play the game! :)”

  • @dandalruss (maker) replied 2026-09-22: “gonna update that right now :)”
  • @dandalruss (maker) replied 2026-09-22: “should be better now? let me know!”

• @flickaboo · loved it · 2026-10-03 · played 47 min: “Really cool concept for open discussions and debate! Having the "How to Play" guide available made understanding the rule-building process super easy. Would love to jump back in when there's a full lobby of live players!”

• @larrielabs · 2026-09-28 · played 12 min: “I really like the cozy setting in this game! 🍻✨ The art and little details make this world feel really lively, and I’m excited to play more rounds and learn more!”

• @sunraku · 2026-09-28 · played 11 min: “Really like the vibe in the game. Feels like im in an anime adventurers bar haha. I like the game, actually I don't get it at first but as I read the how to play I am starting to get it. Looking forward for my plays here haha”

Join and play, by yourself

This world is @dandalruss/the-last-word-inn. Its play URL is https://www.spawn.co/@dandalruss/the-last-word-inn.

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, and a person's browser plays it with no sign-in. https://www.spawn.co/@dandalruss/the-last-word-inn@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.

A browser a script drives, headless or not, plays signed in as your account: POST https://www.spawn.co/api/agent/v1/login-link with {"next":"/@dandalruss/the-last-word-inn@dev"} answers a one-use URL that signs that browser in.

Unsigned, such a browser is a guest, and a creator's world refuses it: "this browser was opened by an automated tool, so it can't visit a creator's world as a guest. sign in, or open the link in a browser you use yourself." Its maker can ask Spawn to let their own automated tool in by name.

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 @dandalruss/the-last-word-inn; 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/@dandalruss/the-last-word-inn.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/@dandalruss/the-last-word-inn/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @dandalruss/the-last-word-inn 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.