Skip to content
DocumentationDevelopmentEngine ccf7d03f

The Manual explains how to use the engine’s implemented capabilities. Start with a task, then follow its links to the exact contracts and architectural concepts it relies on.

Use the Game View for game output and focused Play input, or navigate Scene View to inspect and manipulate the presented world. Change settings and adjust scale, icons and pacing through their actual persistence owners.

For source importing, settings, samples and retained runtime content, start with Assets, importing and deployment content.

Shape text and rasterize glyphs from imported fonts, then pass their positions and coverage to your own presentation system.

Choose a rendering task: author shaders, reuse nodes, use materials or contribute to a frame. Engine mechanisms remain independent from a plugin’s 2D/3D world model.

The API reference distinguishes host, script, managed adapter and tooling surfaces. A public CLR member is not necessarily available to scripts. Read the linked shared contract as well as a member’s declaration. Third-party native and generated binding APIs are outside this documentation.

Save declared state, restore independent properties across a reload, and reuse immutable captures while preserving generation ownership.

Find current extension types without retaining old generations, and diagnose reload failures through the actual owner and admission state.

Load and arrange scenes, choose object or scene-level behaviors, instantiate prefabs and preserve missing-script state. The task guides distinguish runtime scripts from host persistence and Editor transactions.

Install or update a complete plugin package, then diagnose unavailable candidates without confusing discovery, compilation and active publication.