Skip to content

Documentation Gaps

This page tracks systems that are implemented in the engine but are not yet covered, or are only covered indirectly. It exists so gaps are visible rather than silently absent. Remove an entry when its page lands.

If you are looking for something to contribute, this is the list.

TopicWhere the source isWhat a page needs to cover
User Interface (authoring)Runtime/UI, Editor/.../RmlUiEditorAuthoring RmlUi documents and stylesheets in the editor, the world widget component versus screen-space UI, UI material brushes, and world text. The C# API is documented; the authoring side is not.
Input modes and contextsRuntime/Input/InputMode.h, InputContext, InputViewportHow UI versus Game input mode and mouse capture are chosen, and how input is routed per viewport. Actions and their bindings are covered in Input.
Project and editor settingsRuntime/Config, Editor/Source/SettingsWhat each settings class controls, where values are stored, and which ones require a restart.
FoliageRuntime/World/Entity/Components/FoliageComponent.h, Editor/.../FoliageEditModePainting instanced foliage, density and scale, and how foliage re-projects after terrain edits. Currently only mentioned in passing on the Terrain page.
Blackboards (authoring)Runtime/Assets/AssetTypes/Blackboard, Editor/.../BlackboardAuthoring a blackboard asset and its keys. The C# API is documented; the asset editor is not.
Audio streams and procedural audioRuntime/Assets/AssetTypes/Audio, ProceduralAudioComponentStreaming audio assets and the procedural audio component. The Audio section covers sources, buses, and settings.
Camera shakesRuntime/World/Entity/Components, camera rig systemAuthoring shakes and playing them. Cameras covers components and rigs.
Geometry collections and destructionRuntime/Assets/AssetTypes/GeometryCollection, DestructibleComponentAuthoring destructible assets end to end. Materials & Destruction covers part of this.
Console variables referencegrep TConsoleVar across Engine/SourceA user-facing list of the console variables worth setting. The mechanism is documented in Diagnostics.
TopicWhere the source isWhat a page needs to cover
UI internalsRuntime/UI, RmlUiBridge, RmlUiRendererThe RmlUi integration: document and context lifetime, the world widget render path, material brushes, and the editor context tick.
TopicStatus
Generated API referenceDeferred. A class reference generated from the reflection database is the intended eventual home for per-type and per-property documentation. The hand-written manual comes first.
  • Verify against the source. Do not describe intended behavior, describe what the code does.
  • Distinguish implemented, partially implemented, and planned explicitly. If a system has a role or a flag reserved for future work, say so rather than implying the feature exists.
  • Keep code examples in step with the real API. Never invent a call to round out an example.
  • No em dashes.
  • Add the page to the sidebar in astro.config.mjs, and remove its row here.