Input System Overview
Input System Overview
Flowscape input is built as a two-level model:
Inputis a static runtime state source- controllers read that state and apply behavior to scene layers
This design keeps low-level device state centralized and keeps interaction logic modular.
Why this exists
Use this architecture when you need:
- predictable keyboard/mouse/wheel state access
- separate world and overlay interaction responsibilities
- custom input tools without rewriting scene internals
Topics
Input01
Static input state API: keyboard, mouse, wheel, and runtime input configuration.
Controllers02
Controller architecture: overview, world/overlay built-ins, and custom controller patterns.