Inside Limn Engine: How a 360-Level Raycast FPS Runs in a Single HTML File
Inside Limn Engine: How a 360-Level Raycast FPS Runs in a Single HTML File When I set out to build NULLPOINT , a retro-style browser FPS with 12 seasons and 360 procedurally generated levels, I had one strict rule: no build tools, no npm, and no complex bundlers. Everything had to run from a single HTML file. To pull this off, I used Limn Engine ( epic.js ). If you look at Limn, you won't find a…
Limn Engine, a minimalist HTML5 Canvas wrapper, was used by the author to build a first-person shooter (FPS) game called NULLPOINT with 360 procedurally generated levels. The engine operates on a single HTML file, adhering to the author's strict rule of no build tools, no npm, and no complex bundlers. Limn handles the essential components of the game, such as the display, camera, submit loop, input capture, and basic physics, allowing the developer to focus on creating the game mechanics.
The engine's performance is boosted by a "fake" offscreen canvas, which caches static elements like tilemaps, backgrounds, and UI frames. This cached canvas is then drawn onto the visible canvas using the drawImage method, resulting in a high frame rate even on low-end hardware. The game's core architecture consists of a Display controller and a Component base class for game objects, but NULLPOINT ignores most of Limn's API, treating it as a high-performance bootstrapper.
NULLPOINT customizes the raycasting engine and writes its own raycasting math from scratch, drawing vertical slices for walls and enemies using the raw display.context (2D Context API) instead of Limn's built-in systems. The game is powered by Web Audio API for sound effects and music, eliminating the need for external .mp3 files. Overall, Limn provides the necessary canvas, camera, and loop functionality, allowing developers to build complex games in a single HTML file with minimal overhead.
Rewritten by urgent.news; may contain errors — check the original.
Source: dev.to