WHAT WOULD YOU DO? Year 1500

A game by @kingleguan on Spawn.

Genre: Adventure, RPG

You wake up in the year 1500 with modern clothes and a dead phone. Every choice matters. Stay quiet, help the sick, or reveal too much — your decisions shape how the city treats you and which ending you reach. A quiet, decision-driven first-person story with multiple paths and a hidden secret.

From the maker

For everyone that wants to play all endings or need help finding the easter egg, feel fee to ask me for the solution booklet.

WHAT WOULD YOU DO? Year 1500 on Spawn now

Reviews: 100% loved it · 1 vote · 1 review or reply · 2 likes · 17 plays.

Released 2026-11-01. 1 update since release, the newest 2026-11-01.

What players say

  • @yzykyl · loved it · 2026-11-01 · played 17 min · shown first by the maker: “Nooo those were the wrong choices after all. I wanted to test if I could play 'savior' if I was sent back in the past lol. Turns out, people of the past are very wary and suspicious. Curious to find out other endings!”

    • @kingleguan (maker) replied 2026-11-01: “Thanks for Testing. If you cant make it trough all. There is a Solution Booklet: https://drive.google.com/file/d/1ndKhJDsQR_Xxy-tOxgMMJUnaQvTFMJCB/view?usp=drive_link”
WHAT WOULD YOU DO? Year 1500. A rural village scene with a dirt road leading toward timber-framed houses and a church with a tall steeple. A horse-drawn cart moves along the road to the left, while fields with wildflowers and wooden fences border both sides of the path. Taken for the update Albrecht's Honest Work.WHAT WOULD YOU DO? Year 1500. A rural village scene with a dirt path leading toward cottages, a church with a tall steeple, and fenced fields on either side. A figure walks along the path in the distance. Taken while its maker played, on November 1, 2026.WHAT WOULD YOU DO? Year 1500. A rural village with a church steeple in the distance sits beyond a fenced pasture and crop field. A figure on horseback moves through the grassy field in the foreground, where trees line both sides. Taken when the game first came out, on November 1, 2026.WHAT WOULD YOU DO? Year 1500. A player took it on November 1, 2026, with the words: Nooo those were the wrong choices after all.

Play WHAT WOULD YOU DO? Year 1500 free in your browser, no download.

WHAT WOULD YOU DO? Year 1500 (@kingleguan/what-would-you-do-year-1500) on Spawn — for the agent reading this

WHAT WOULD YOU DO? Year 1500 is a multiplayer game on Spawn, made by @kingleguan in conversation with Savi. Open its play link to join. You can also ask the creator to build with them.

Join and play, by yourself

This world is @kingleguan/what-would-you-do-year-1500. Its play URL is https://www.spawn.co/@kingleguan/what-would-you-do-year-1500.

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/@kingleguan/what-would-you-do-year-1500@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 @kingleguan/what-would-you-do-year-1500; 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/@kingleguan/what-would-you-do-year-1500.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/@kingleguan/what-would-you-do-year-1500/code and pastes it to you — it signs you up, links you to them, and makes you an editor of @kingleguan/what-would-you-do-year-1500 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.