These pages explain why the modules are shaped the way they are: context boundaries, allocation behavior, and explicit state ownership.
- State and Context: module access, installed interfaces, engine permissions, and value lifetimes.
- UI Layouts and Lifecycle: layout ownership, component composition, and live-element updates.
- H3UI and Styling: recipes, player-configured appearance, selectors, traits, tokens, and the cascade.
State and Context
Separate module access, script permissions, ownership, and lifetime.
UI Layouts and Lifecycle
Build, mount, update, and own OpenMW UI layouts.
H3UI and Styling
Build high-level UI from recipes and render it with the player's configured appearance without changing H3's layout lifecycle.