Choose the path that fits where you are: start making games, learn the Lenga workflow, go deeper, or contribute.
Start Here
If you are new to Lenga, read these pages in order before branching into subsystem guides.
Choose a Path
These paths map to the audiences we write for: brand-new creators, experienced developers new to Lenga, advanced Lenga users, and contributors.
New to game development
Begin with the editor, scenes, GameObjects, Transforms, Components, and Behaviours before moving into task guides.
Already know how to make games
Map familiar engine concepts onto Lenga without skipping the names Lenga uses in the editor.
Already use Lenga
Dive into gameplay communication, tweening, UI layout, and shipping workflows once the core model is already familiar.
Contribute to Lenga
Refresh the editor and object model first, then open the public GitHub organization to follow the code and project work.
Explore by topic
Choose a topic area to find guides that belong together. Start with the highlighted pages, then open subtopics when you need a deeper pass.
5 guides
Install Lenga, open the editor, and create or load your first project.
4 guides
Understand the editor workspace, views, panels, and day-to-day authoring flow.
4 guides
Understand scenes as authored spaces and manage scene files.
7 guides
Learn the scene object model: GameObjects, active state, tags, layers, primitives, parents, children, and prefabs.
4 guides
Place objects by working with position, rotation, scale, local space, world space, grids, and snapping.
5 guides
Attach and tune capabilities on GameObjects, from renderers and physics components to Behaviours.
9 guides
Write Behaviours, expose fields, respond to lifecycle methods, and coordinate gameplay.
4 guides
Use time-based interpolation to animate movement, scale, rotation, UI feedback, and authored presentation.
1 guide
Import textures, audio, models, and configure project asset settings.
1 guide
Use 2D image assets, sprite renderers, sprite sheets, and sprite-based workflows.
5 guides
Understand UIElements, canvases, RectTransforms, layout, text, images, and buttons.
15 guides
Understand rigidbodies, colliders, collision callbacks, queries, joints, effectors, and kinematic movement.
2 guides
Create sprite animation, animation controllers, and model animation workflows.
1 guide
Add sound sources and connect audio to gameplay.
3 guides
Light scenes, use shadows, skyboxes, and configure rendering setup.
2 guides
Create materials and shaders for custom surface rendering.
1 guide
Add particle effects and polish moments with visual feedback.
1 guide
Author levels with tilemaps, layout tools, and editor workflows after the core object model is clear.
4 guides
Export, publish, secure, and ship playable builds.
Search
Already know what you need? Search by feature, task, or keyword.
78 matching guides
Lenga starts with one simple step: install the editor so you can create and open projects locally.
When you launch Lenga, the editor opens to the `Project Hub`.
Use the `Project Hub` when you want to start a new game in Lenga.
Every Lenga project has a clear folder layout.
Use this workflow when the project already exists on disk and you want to bring it into the editor.
The Lenga Editor is the main workspace for building a game.
Lenga's editor keeps the parts you reach for most in view at the same time: your scene, your selected object, your assets, and the console feedback that tells you what just changed.
A lot of editor work in Lenga comes down to three panels working together:
Lenga gives you two important visual surfaces while you work:
A Scene is one authored space in your game.
Once a project is open, scenes become the main units of authored world and UI content that you move between.
Use scene backdrops when you want to establish the look of a scene before you start filling it with foreground detail.
Scene backdrops let you shape the visual mood of a scene without building decorative geometry just to fill the background.
A `GameObject` is one named thing in a scene.
A GameObject is the scene object Lenga stores, selects, edits, and exposes to your code.
You do not need final art before you start building a scene.
Every GameObject can be active or inactive.
Tags and layers help Lenga answer different questions about a GameObject.
Scenes become easier to work with when related objects live together in a clear hierarchy.
A prefab is a reusable GameObject setup saved as an asset.
A `Transform` stores where a GameObject is.
Once a scene is open, the next job is usually the same: place content where it belongs.
Use the Scene grid and snap controls when you want object placement to land on predictable increments.
Use this workflow when you want a 3D object or camera to rotate cleanly in code, especially when the object has a parent or when you want to combine several rotations together.
A component is one capability attached to a GameObject.
Components are how a GameObject gains capabilities.
Scene-attached gameplay code often coordinates other components on the same GameObject.
The Inspector is where component data becomes easy to tune.
A Behaviour is a scene-attached component class for gameplay logic.
A `Behaviour` is a PHP class attached to a GameObject as a component.
Lenga reads serialized PHP properties and turns them into Inspector controls.
Gameplay events let one part of your game react to something that happened somewhere else.
Use `EventBus` when you want systems to react to gameplay without holding references to the object that dispatched the event.
Use a `Signal` when one object wants to expose a callback surface on itself and listeners already know which exact owner they care about.
Lenga gives you three valid communication patterns.
`WaitForSeconds` is the cleanest way to express short timed sequences in Lenga when the code should read as a sequence instead of a state machine.
Lenga supports engine-wide pause.
`Preferences` is Lenga's built-in API for small local settings.
Tweens are short scripted motions that move a value smoothly from one state to another.
Use transform tweens when you want a GameObject to move, rotate, or scale smoothly without writing timer code by hand.
Tweens describe motion. Coroutines describe order.
Most tweens can be fire-and-forget. Some need to be controlled.
This guide covers the asset import workflow in the Lenga editor.
A sprite is a 2D image used as game artwork.
A `UIElement` is one piece of interface inside a Canvas.
Every UI element in Lenga uses a `Rect Transform`.
This guide walks through building a small UI hierarchy under a `Canvas` and placing elements where you want them in the editor.
Buttons can carry their own font and their own images for each interaction state.
SDF fonts help UI text stay crisp when it is scaled, outlined, or drawn at several sizes.
A Rigidbody is a physics body attached to a GameObject.
A Collider is the shape the physics system uses for contact.
Collision callbacks are how gameplay learns that two things actually touched this frame.
The 2D collision matrix lets you decide which layers are even allowed to collide before gameplay code runs.
Use an effector when the collider should enforce a gameplay rule beyond a normal solid collision.
`PlatformEffector2D` is for one-way platform behavior.
Treat each joint as a different kind of rigidbody relationship.
Use this workflow any time two 2D rigidbodies need a physical relationship.
`DistanceJoint2D` keeps two bodies at a distance relationship.
`FixedJoint2D` locks two bodies together as if they were rigidly attached.
`HingeJoint2D` rotates around a pivot.
`SliderJoint2D` constrains movement to one axis.
Contact queries answer a different question from casts and callbacks.
Physics queries let gameplay ask the world a question right now.
Lenga's 3D collision workflow is built around **colliders, queries, and `CharacterController`**.
Lenga's 2D animation workflow is built to handle the common character loop without forcing you into a heavyweight graph tool before you need one.
Lenga's 3D animation workflow is focused on **imported model animation playback**.
Use an `AudioSource` when a GameObject should play a sound.
2D lighting in Lenga is scene-based. You enable it for the scene, then add light and occluder objects to shape the result.
Lenga supports a practical lighting workflow for 3D scenes:
Lenga supports scene-level skyboxes for 3D projects.
Lenga uses first-class `Shader` assets for custom 3D surface rendering.
Lenga has a `Material` asset workflow for 3D rendering.
A particle system is a component that repeatedly creates many small visual particles.
Lenga's tileset tool lets you take one sprite sheet, slice it into reusable tiles, and start painting a level without leaving the editor.
Use this guide when you want to stage a build of your game for the machine and operating system you are developing on.
Use this guide when you want to take a Lenga export and hand it to another person or another machine in a repeatable way.
Use this guide when you want to take a Lenga export and hand it to another person or another machine in a repeatable way.
Use this guide when you want to understand what changes between a normal development run and a packaged player build.
No guides match your search.