Lenga Engine v0.9.0
Release date: 2026-08-06
Lenga v0.9.0 is the first tagged release of the engine repository. It ships
the production desktop workflow the engine has been converging on, and it
introduces an experimental command-line Web export path for early validation.
Highlights
Lenga v0.9.0 is strongest as a production-ready 2D engine with an
end-to-end desktop workflow:
- 2D scenes, sprites, animation, tilemaps, UI, audio, particles, and physics,
authored through the Scene/Game/Animator editor workflow. - PHP 8.5+ gameplay scripting through an embedded runtime and native
extension bridge. - Desktop build and export for Windows and macOS, directly from the editor.
- A substantially expanded particle system tracking Unity Shuriken module
parity, including per-module editor authoring. - A growing 3D workflow: project authoring, cameras, model and mesh
rendering, materials, lighting, skyboxes, rigidbodies, colliders, and
physics queries. 3D continues to harden towardv1.
Experimental: Web Export
Lenga v0.9.0 includes an experimental Web export path for early validation.
It can build and smoke-test real Lenga projects through the production
runtime and PHP-wasm path, but it is not yet the supported editor Export
workflow. Use it to test browser feasibility, asset packaging, scripting
compatibility, and runtime parity before v0.9.2 promotes the workflow into
the editor.
What the experimental path can do today:
- Build a Lenga project into a browser bundle (HTML, JavaScript, Wasm, and a
preloaded asset package) through the production engine runtime and an
Emscripten-built PHP embed. - Package project settings, PHP scripts, Composer metadata, build scenes, and
referenced assets through a manifest-aware staging step. - Preflight a project before compiling, serve the generated bundle locally,
and run automated browser smoke checks with machine-readable results. - Manage Web build profiles, scenes in build, and dependency manifests
through stable CLI tooling.
How to try it: see the Web export CLI tooling guide in
docs/setup/web-export-cli-tooling.md and the website manual page
"Try Experimental Web Export".
Boundaries in v0.9.0:
- Web export is command-line only. The editor Export window, editor-authored
asset graphs, and managed toolchain repair arrive with the production
feature inv0.9.2. - Best suited to 2D projects. 3D physics is not available in browser builds.
- The Web toolchain (Emscripten, Raylib Web, PHP-wasm embed) must be
provisioned through the documented setup scripts. - Experimental means experimental: contracts and output shapes may change
beforev0.9.2.
Known Limitations
- The 3D workflow is usable but still being hardened for
v1. - Web export is experimental, as described above.
- Linux desktop export is not yet part of the actively validated platform
set (Windows and macOS are).
Verification
This release passed the v0.9.0 closeout gates defined in
docs/planning/web-export-v0.9-release-plan.md: tooling lint and contract
validation against internal canary projects, a clean editor and runtime
build, and a clean release-candidate Web build and browser smoke run of the
internal 2D canary.
What's Next
v0.9.2 promotes Web export into a supported, editor-first feature: an
Export window, editor-authored asset dependency graphs, toolchain detection
and repair, deployment packaging, and supported documentation. The phased
plan lives in docs/planning/web-export-production-implementation-plan.md.