Credits and asset provenance

This page exists so that the answer to “where did that come from?” is never a guess. Everything published on this domain is original work unless it is listed below as something else, and at the time of writing nothing is listed as something else.

Artwork

There are almost no image files on this site. Game graphics are drawn at runtime in code — canvas paths, gradients and procedural texture — rather than loaded from sprite sheets. The felt look in Feltling, for instance, is a generated fibre tile composited over shapes whose outlines are deliberately wobbled; there is no painted artwork behind it at all. The handful of vector files that do exist (jumper.svg, cactus.svg, coin.svg) were drawn for this site.

An earlier version of this site did use three downloaded sprite packs from itch.io, in four games. Because their licences could not be confirmed as permitting commercial use, those files were removed from the repository and the games that used them were redrawn in code. No third-party artwork is served from this domain today.

Thumbnails and share images

Every thumbnail on the front page is a real screenshot of the game running, captured automatically by a headless browser rather than composed by hand — which means it cannot show something the game does not actually do. The 1200×630 share cards are generated from those same screenshots. If you are writing about one of these games, both are free to use.

Sound

All audio is synthesised in the browser with the Web Audio API at the moment it plays. There are no sound files. A knock on felt, for example, is a burst of white noise shaped by an amplitude envelope and pushed through a low-pass filter whose cutoff falls as the seal’s coat thickens. No samples, recorded or purchased, are used anywhere on this site.

Typefaces

Headings and interface text use Fredoka and Outfit, and nine of the older games load a display face such as Audiowide or Orbitron. All are open-licence typefaces served from Google Fonts, which means your browser fetches them from Google’s servers rather than from this domain — the one category of third-party request on this site besides analytics and advertising, and it is described on the privacy page. Body text falls back to your own system typeface while they load. The newest game uses the system rounded face and loads nothing.

Code and tooling

• The games — vanilla JavaScript and HTML5 Canvas. No engine, no framework, no runtime dependencies. Each game is one self-contained HTML file.
• The site — a Node build script that generates static HTML. No CMS.
• Testing — Node's built-in test runner, plus Playwright driving headless Chromium for the gameplay gates and screenshot capture.
• Images — sharp, for resizing captures into WebP thumbnails and PNG share cards.
• Hosting — GitHub Pages, deployed by GitHub Actions on every push, with the build gates running in CI so a failing game cannot reach the live site.
• AI assistance — coding assistants are used to draft and refactor code, which is then reviewed, tested and accepted or discarded by a person. Design decisions and the text on this site are human work. This is stated plainly on the about page as well.

Reusing anything here

The games are not open source and are not free to redistribute, but they are available for licensing — see the contact page. Screenshots and share images may be used in coverage of the game they show, with a link back.