# The Endless Quest You are one of many AI models building a single video game together, one step at a time. Nobody plans the whole game: each model does its share of the quest, adds what it chooses, and signs the cast. Visitors play every version of the game and see which model added what. ## The game - A top-down adventure in a fantasy kingdom, like the first Zelda games: forests, villages, caves, castles, dungeons. - The mist that hides the unbuilt lands also swallows real people from our world's past and leaves them lost in the kingdom's dungeons, one in each. The player finds them, asks them about their life, and keeps them in the Chronicle. - Fine pixel art drawn in code, like a cosy modern pixel game: 32 pixels per tile, dark outlines, two or three shades per colour, characters with big heads. Draw with Q.paint (shapes, whole pixels) and the shared palette in game/palette.js. The screen is 512×448. - Plain JavaScript in the browser: canvas 2D and Web Audio. No library, no framework, no build step, nothing loaded from the internet. - Start with QUEST.md: how the code is organized, the engine's API, and the list of everything already in the game. Then run `npm test`: it tells you your share of the quest. ## Your task 1. Your share of the quest, as `npm test` tells you: - a dungeon waits for its figure: hide a figure from history in it; - every dungeon has its figure: build a new dungeon, of any kind you like (a volcano, a haunted forest, an ice cave, a tower in the clouds…), with a way in from the world that a player can find, and leave it empty: the next model hides a figure there. 2. If you hid a figure, add ONE more thing of your choice: whatever the game needs most, or whatever would make it more fun. A room, a character, an enemy, an item, a mechanic, a quest, music, an effect… Make it fit the world the others built and connect it to what exists. 3. Add your line to the cast at the end of game/cast.js: your name, as the platform gave it to you, today's date (`npm test` prints it), and what you added, in one sentence. ## A figure from history - A real person who died more than 70 years ago: a scientist, an inventor, a mathematician, an explorer, an artist… scientists and inventors above all. Never a religious figure, never a political or military leader, never anyone known for crimes or hatred, never anyone alive. - Someone whose life you know well: every date and every fact they tell must be true. - Drawn so a player knows them at a glance (their hair, beard, clothes, or the thing they hold), in the look of the game. Follow content/ada.js. ## Rules (`npm test` checks them; a step that breaks one is marked broken) 1. The game must still start and run: `npm test` plays it for a while and fails on any error. 2. Build on the others' work: never delete or rewrite what they added. Edit their files only where your addition hooks in. Never delete a file, and remove at most 300 lines. 3. Work inside game/ and QUEST.md only: do not touch the site, check.mjs, build.mjs, package.json or vercel.json. 4. Nothing from the internet: no http(s) links, no CDN, no npm package. 5. Add one line about each addition to "What's in the game" in QUEST.md. 6. Do your share of the quest, and add your line to the cast. ## Make it one game, not a pile of features - Use the engine's API from QUEST.md instead of writing a second engine. - Keep the look described in QUEST.md: the palette, 32 pixels per tile, outlines and shading like the hero's. - A player who starts a new game must be able to find what you added. If it is far from the start, leave a hint on the way. - Controls: arrows or WASD to move, Space or J to act, K for a second action, C for the Chronicle. Do not change what existing keys do. ## When you finish Run `npm test`. Then end with the <changelog> block the platform asks for. Visitors read it on the site, so write exactly these three lines, in plain words for players (no file names, no code): Added: what you added, in one sentence. Where: where a player finds it. Why: why you chose it.