NEOLearn

Engine guide

A guide to the NEO engine in Rust: setting up, the ECS, apps and time, assets, scenes, rendering in 2D and 3D, UI, input, audio, animation, tools and examples.

Updated October 20, 2026

On this page

This guide explains the NEO engine for people who write Rust: how a NEO app is put together, and how to use each part of the engine, from entities and systems to rendering, UI, input, audio and animation. Read it in order the first time, or jump to the part you need.

If you only make games in the Studio and script them, you don't need this guide; start with Scripting. The engine is what your game's Rust code in crates/ is written against, and what scripts reach through the parts your Rust code exposes.

Getting started#

PageWhat it covers
Set up the engineThe Rust toolchain, system packages and faster compiles.
Your first appAn app with a window, a camera, a shape and a system that moves it.
Project layoutWhere a NEO game's crates, content and settings live.
Cargo featuresThe neo crate's features, and which are on in NEO's builds.
PlatformsDesktop, web and mobile: what runs where.
PerformanceBuild settings and habits that keep a game fast.

The parts of the engine#

PartWhat it covers
ECSEntities, components, systems, queries, resources, commands, messages, observers, hooks, relationships, schedules, states and plugins.
App and coreThe app and its runners, time and the fixed timestep, transforms, math, async tasks and windows.
AssetsLoading and using assets, hot reload, custom assets and loaders, processing, asset sources and glTF.
Scenes and reflectionRuntime type information, the type registry, serialization and scenes.
3D renderingCameras, meshes, materials, shaders, lights, shadows, the environment, post-processing and anti-aliasing.
2DSprites, sprite sheets, 2D shapes and meshes, text in the world and 2D cameras.
UINodes, flexbox and grid layout, text, images, interaction, focus, widgets and scrolling.
InputKeyboard, mouse, gamepads, touch and picking.
AudioPlaying sounds and music, and spatial audio.
AnimationClips, animation graphs, glTF animation, morph targets and tweening, and NEO's character animation.
Debugging and toolsLogging, diagnostics, gizmos, profiling, dev tools and the remote protocol.
ExamplesMore than 400 runnable examples, by category.

How NEO's own crates fit in#

The engine core gives you the building blocks: the ECS, rendering, assets, UI, input, audio and animation. NEO's own crates build games on top of it, and this guide links to their pages where they take over:

CrateWhat it addsPage
neo_pluginPlugins described in Cargo.toml, switched on in neo.toml, game features that switch on and off while running.Plugins and neo.toml
neo_gameplay_kit, neo_character, neo_input_kit, neo_audio_kitA ready-made character, input actions and touch controls, and game audio.Gameplay kit
neo_camera_director, neo_gameplay_cameraA camera director with blends and modifiers.Camera
neo_scriptJavaScript and Python scripts inside the running game.Rust code and scripts
neo_deviceThe platform layer: content, saves, GPU set-up and web start-up.Web builds

Next steps#