quest-n-click
Health Gecti
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Community trust — 15 GitHub stars
Code Uyari
- fs module — File system access in .github/workflows/candidate.yml
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Mobile-first SCUMM-style point-and-click engine with authoring tools and an AI-friendly workflow

quest'n'click
Make a point-and-click adventure for the browser: write it as data, shape it in a visual Studio, check that it can
be finished, and ship it as a web game that installs on a phone and plays offline.
Formerly web-scumm. This project was called WebSCUMM, then web-scumm, in homage to SCUMM, the LucasArts engine
whose spirit it follows. It was renamed quest'n'click so its name would spark no needless debate. Links to the old
repository redirect here, and the old demo address,wanoo.github.io/web-scumm, redirects to the new one: the game
and the Studio now live at wanoo.github.io/quest-n-click. From 4.2.5 the packages and commands
are namedquest-n-click; the oldweb-scummnames kept working through 4.2.x and are gone in 4.3.0, wherenpx quest-n-click migraterenames a game's imports and commands
(upgrade notes). Saves, runs and sessions keep their formats and load as before.
| 🎮 Play | The Pantry Key, the sample game, on a phone in landscape or on a desktop |
| 🛠 Studio | Open the Studio in demo mode: edit the sample game, your edits stay in your browser |
| ⏱ Start | Your own game in its own folder, then a first room in fifteen minutes |

Start
Node 22.12 or newer and Python 3 with Pillow (npm run assets prepares the art with them), on Windows, macOS or
Linux. The engine installs from a release's archive (npm publishing comes
in a later release):
T=https://github.com/wanoo/quest-n-click/releases/download/v4.5.1/quest-n-click-4.5.1.tgz
npx --package=$T quest-n-click create my-game "My Game" --engine=$T
cd my-game && npm install
npm run assets && npm run dev # play it; then npm run verify, npm run build
npm run build writes dist/, a static site any host serves. ffmpeg serves the sound pipeline and is optional;npx quest-n-click doctor says what is missing. Package reference is the whole guide;
Your first game walks the first room.
Before 4.2.5 the archive and the command were named web-scumm; 4.2.5 also shipped them under that name, and 4.3.0
no longer does: a game made before moves with npx quest-n-click migrate (upgrade notes).
Build a game
The content is data. Rooms, props with states, characters, items, rules, conversations, hints, scripts and
events are plain TypeScript objects, with no code in them, so every tool can read, check and play them:
export const garden: RoomDef = {
id: 'garden', name: 'The garden', decor: 'garden',
props: { tank: { name: 'water tank', states: { full: 'tank_full', empty: 'tank_empty' } } },
exits: { back_door: { name: 'back door', to: 'house', entry: 'garden' } },
on: [
{ verb: 'use', a: 'pipe', b: 'tank', if: '!tank_drained',
do: [{ minigame: 'pipes' }, { lose: 'pipe' }, { set: 'tank_drained' }, { prop: ['tank', 'empty'] }] },
],
hints: [{ until: 'tank_drained', lines: ['Use the pipe on the water tank.'] }],
};
A rule is a verb, a target, a condition and a list of commands. What a game needs beyond them, a custom command, is
TypeScript of its own: trusted code, named in the game and hashed with it (content principles,
how the engine works). Famous mechanics of the genre are written this way in Classic mechanics.
The Studio is the real engine with an editor on top: rooms with their placements, the storyboard panel by panel,
every sprite sheet and where it is used, the checks after every save, a play tab that explains a rule and replays a
session, and notes shared with an AI assistant (the Studio).
![]() Rooms: the real engine, a placement editor on top, every line editable in place | ![]() Check: the validator and the solver, run again after every save |
Art, sound and languages. A prompt for every sprite sheet, object and backdrop in one style, sheets cut into
sprites (Images); chip-tune music arranged from a MIDI and sound effects from one palette
(Music); every line translatable, a missing translation found before release.
Prove and ship it
- Validated: broken references, unreachable rooms and untranslated lines are found before anyone plays.
- Solved: the solver runs the real engine (no second model of the content).
npm run verifyasks for a
witness, a path to an ending;npx quest-n-click solve --proveexplores every reachable state and fails on a softlock or a truncated search. These
are two different promises, and the release asks for the second (Benchmarks says what the proof can
and cannot do). - Replayed: a session is the unit of reproduction; saves load across versions, one frozen save per release from
3.0.0 on. - Shipped: a PWA that installs and plays offline after the first visit, with what a phone has to download held by
a budget and every file accounted for with its licence. - Accessible as far as a machine can tell: axe-core on every screen, keyboard and touch play in CI. That is not a
WCAG conformance claim: screen-reader and real-device passes are a person's to make (Field passes).
![]() Conversations with topics, choices and a transcript | ![]() The puzzle graph: what each item and flag leads to, the critical path, the solver's heat |
Further
- Several playable characters, a world map, minigames playable by touch or keyboard, cutscenes and phone calls,
autosave and save slots. - Remix: worlds generated from a seed, each one validated and solved before it ships (Remix).
- Speedrun: runs recorded, sealed and verified by a replay; leaderboards on the Bridge.
- Reality: a game reacts to a fact from the world (an email answered, a terminal command, a badge) through a
signed signal from a Bridge, without its content touching the network (the Reality Bridge,
running it).
![]() A minigame, played by touch or with the keyboard | ![]() The world map, the characters where they are |
What is stable
Each surface is promised only as far as its proofs go (Stability and support, GO / NO-GO 4.2):
| Stable | Limited | Experimental |
|---|---|---|
| the content format and its tools; the desktop Chromium PWA; the Reality Bridge on SQLite | the DOM player on phones and screen readers (untried by a person); the Safari PWA; Firefox (the PWA only); speedrun and Remix; voices; the four package archives (until a person installs them) | the Canvas painter; the Bridge on Postgres (distributed); the four connectors |
What only people and real devices can check is listed, not claimed: Field passes, and each release's
notes say which passes were made.
How it is made
src/engine/ core (the DSL, the engine), tools (validate, solve, lint, i18n…), dom (the player), minigames, reality
games/demo/ the sample game: rooms, layouts, art, audio, locales, storyboard
games/_template/ copied by npm run new-game
tools/ the commands, the Studio, the MCP server, the art and audio pipelines, the Vite plugins
bridge/ the Reality Bridge (the package quest-n-click-bridge)
connectors/ the connectors of the world outside (the package quest-n-click-connectors)
wiki/ the documentation (en, fr), published as the wiki; docs/dev: the work log, the decisions, the passes
The engine, the solver and the replay share one code path; Architecture and a half-hour
code tour explain how it fits together.
Made with an AI assistant, reviewed by people. The content is declarative, so an assistant reads and writes it
like any other file (AGENTS.md holds the rules); every operation is a command and an MCP tool
(MCP setup); after each change it can validate, solve, replay and take a screenshot, so it sees its own
mistakes before a person does. Every result stays reviewable, in the Studio and in Git.
CONTRIBUTING says how to change it.
In numbers
Measured on this commit of main by the automated gates (npm run quality:baseline writes these figures):
mutation testing; the reference game proved in 288 states; the player's
first visit 136 KB of JavaScript, gzipped. Each release is built from the
commit its candidate tested. The candidate makes the four package archives, the Bridge's image, the SBOMs, the runs and
the baseline, and the release publishes those very files; the release makes only the built game, its assets manifest,
the proved Remix catalogues, the reference speedrun and the sums, from the same commit. Every file is published with
its SHA-256 sum and a provenance attestation (the list).
Documentation
The documentation is the wiki, every page in English and in French, written in wiki/ in this
repository and checked there (npm run wiki -- check: links, anchors, both languages in step, the references against
the code): Your first game, working with an AI from
the first idea to the release, every command in npm scripts, what changed in the
CHANGELOG, moving to a new version in Upgrade, and where it comes from in the
Roadmap. An assistant reads the same pages through the MCP server (search_docs, read_doc);
the old docs/ pages are transition pages, each section linked to its new place and to its 4.4.0 text.
Current release: v4.5.1 (Wiki): the maintainer's audit of the
wiki fixed (links whose label is code, the first tutorial, saves, the support window, search), a game's own spans
(spans.json) and leak-audit allowances (audit-allow.json), and site.json's url for an absolute og:image
(Horacio). Over 4.5.0 "Wiki": the documentation
becomes a bilingual wiki, 210 pages in English and in French, published from each release's own archive; an assistant
searches it with search_docs and list_docs and reads a section by id with read_doc, and the engine's package
carries it (docs-bundle/) so read_doc works in a created project; doctor runs in a created project. Over 4.4.0
"Author's Desk": a playable
example of choosing the hero in two languages (games/heroes), the Studio's hero × language matrix, before/after
captures in the semantic diff, a faster hosted preview, a hotspot that acts on a single tap and a map pin with several
places (Horacio, LostInBrittany), the phone's column on a short landscape screen. Over 4.3.1: a translation's own text
switches get their voices by value through the whole chain, and npm run solve is said to find one winning path
(--prove proves every hero). Over 4.3.0 "Hero Choice": the player
chooses the hero at New Game (portraits in a choice, a name per variant, text switches so the others' words follow the
hero), a key per verb and a proportional pixel font for the interface, most of it from an outside contributor, Horacio
(LostInBrittany); the former web-scumm names are gone (npx quest-n-click migrate). Over 4.2.5, the project's new
name; 4.2.4's changes for authors (an exit gone
through on a single tap, actorGap, the sprite sheets' background, face: 'hero' fixed) and 4.2.3 "Coordination",
the Studio online for a team, experimental (what runs where): previews per revision, health, personal undo, published builds, backup and restore, and since 4.2.3 a scenario map, anchored
comments, a diff by name, AI agents through a remote MCP, Git push and import, the hosted Assets tab; over 4.2.0 "Stable
World". 4.2.0 restored strict SemVer after the 4.1.x incubation line: a minor adds, a major removes; the public API
follows it (Stability and support). 4.2.0 shipped before the people's passes: of the surfaces above, only the
Stable column is promised; the passes are made on a 4.2.x, which promotes what they prove
(GO / NO-GO 4.2, D38).
Licences
Code: MIT. Sample artwork, sound effects and theme: CC BY 4.0 (attribution "Wano"); the theme is Tchaikovsky's Swan
Lake (public domain), written out and arranged for the project. Fonts: SIL OFL. See CREDITS.md.
quest'n'click (formerly web-scumm) is an independent project. "SCUMM-style" names a kind of game; the project is not affiliated with, endorsed
by or derived from LucasArts, Lucasfilm, Disney or the ScummVM project, and ships none of their code, data or art.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi





