Lenga Engine Sample Games

This repository contains editable Lenga projects that show how engine features fit together in real games. Open a project in the Lenga Editor, inspect its scenes and components, and use the PHP scripts as practical starting points for your own work.

These are source projects rather than prebuilt game downloads. They evolve independently of the engine repository and may target features on Lenga's current development branch.

Projects

Project	Mode	What it demonstrates
Blasters	2D	A compact space-shooter project with input, animation, projectiles, and gameplay behaviours.
HelloWorld	2D and 3D	A feature sandbox for camera behaviours, 2D joints, 3D models, and simple scripted objects.
Platformer	2D	A larger platformer project with tile-based levels, animation controllers, combat, menus, audio mixing, and gameplay state.
Pong	2D	Physics-driven paddle gameplay, configurable input, runtime spawning, UI, and scene transitions.
RollerWorld	3D	A roll-a-ball game using 3D physics, follow cameras, lighting, materials, shaders, audio, UI, and collectibles.
Super Blastoid	3D	A minimal 3D project for experimenting with scene setup and native components.

Requirements

• A compatible version of the Lenga Editor
• PHP 8.5 or newer
• Composer 2

Each project declares the public lenga/engine PHP scripting API as a Composer dependency. Composer downloads the compatible API automatically; you do not need the Lenga engine source tree or a particular folder layout.

ENGINE_VERSION is the repository-wide source of truth. After each Lenga Engine release, automation updates every sample manifest and lock file to that exact version so all projects remain reproducible and compatible with the corresponding editor/runtime release.

Open A Sample

1. Clone or download this repository.
2. Choose the project you want to explore.
3. Run composer install inside that project's directory to install the PHP scripting API and generate its autoloader.
4. Start the Lenga Editor and open that project directory from the Project Hub.
5. Open the project's configured entry scene and press Play.

For example:

cd RollerWorld
composer install

Composer dependencies, exported builds, runtime saves, IDE settings, and local editor layout files are intentionally not committed. Lenga's ProjectSettings/.asset-imports.json files are committed because they are portable asset dependency metadata used by editor and export workflows.

Project Structure

Every sample follows the same basic Lenga project layout:

ProjectName/
|-- Assets/             # Scenes, scripts, prefabs, media, and authored assets
|-- ProjectSettings/    # Lenga project, import, physics, and editor settings
|-- bootstrap.php       # PHP runtime bootstrap
|-- composer.json       # PHP dependencies and PSR-4 namespace mapping
`-- composer.lock       # Reproducible dependency versions

The most useful learning path is to start with a scene in Assets/Scenes, select its GameObjects in the Hierarchy, and then trace attached behaviours into Assets/Scripts.

Contributing

Bug fixes and focused examples are welcome. Before submitting a change, read CONTRIBUTING.md and verify that the affected project opens, its PHP files lint successfully, and its entry scene runs in the editor.

Continuous integration installs the public scripting API and validates Composer metadata, PHP syntax, project JSON, configured scene paths, PSR-4 autoloading, release-version alignment, and repository hygiene for every sample. Maintainers can review the release automation contract when preparing or recovering a coordinated release.

Licensing

Lenga-authored source code and project configuration in this repository are available under the MIT License. Media, fonts, models, and other third-party assets may have separate terms; see THIRD_PARTY_NOTICES.md and any license files stored beside those assets before reusing them in another project.