Point-and-click adventure game framework for Go, built on top of Ebitengine.
Ruby gem for telnet BBS servers: a board declared in a few lines, a windowed face for modern terminals and a PETSCII face for the Commodore 64 on one port, doors, gateways, AI characters, accounts and badges for a whole network.
Turn any Rails app into a retro game catalog: push a game, the CI builds it, the catalog publishes it, and every store client can install it.
Since WarpEngine 1.0: what the admin does, as a JSON API under /api/admin/v1, with a live OpenAPI 3.1 document and an MCP server.
The reusable Batocera store engine: any WarpEngine-based site can ship its catalog to a retro box with a config file and a three-line installer.
The WarpEngine Client app: the catalog as a grid of cards, the store engine built in, and a settings dialog for the stores on the machine.
The RetroArch store engine: any WarpEngine catalog becomes .lpl playlists with box art, on desktop, Android, the Steam Deck or a handheld.
The VS Code extension for WarpEngine games: a new game from the host's template, metadata checked against the host, play in the web runtime, connect, release and the catalog, without leaving the editor.
The shared core of our store engines: one file that knows the WarpEngine catalog, so an engine only has to know its host platform.
WarpEngine Catalog Protocol: the endpoints a WarpEngine server offers to catalog readers, each with its response shape.