Runtime state tracking which actions are currently active.

Gamepad subscription helpers.

Gamepad analog input values (thumbsticks and triggers).

Functions for translating between raylib's GamepadButton and Mibo's backend-neutral GamepadButtonCode.

Functions for translating between MonoGame's Buttons and Mibo's backend-neutral GamepadButtonCode.

Backend-neutral gamepad button, following the standard gamepad layout (face buttons, D-pad, shoulder/bumper, stick clicks). Backends map their native ordering (which differs between raylib and MonoGame) onto this DU.

Gamepad button state changes for a single frame.

Gamepad connection state change event.

Per-player gamepad delta containing button and analog changes.

Gesture subscription helpers.

Gesture detection events for touch-capable devices.

Functions for translating between raylib's Gesture and Mibo's backend-neutral GestureKind.

Backend-neutral touch gesture kind.

Per-game input service providing reactive observables for hardware input.

Service interface for input mapping. The contract lives in Core; each backend supplies an implementation that polls its native API to evaluate whether each Trigger is held.

Service accessors and the concrete IInput factory hook.

Functions for building InputMap configurations.

Configuration mapping game actions to their trigger inputs.

Service accessors for the registered IInputMapper.

Keyboard subscription helpers.

Keyboard state delta containing keys that changed this frame.

Functions for translating between raylib's KeyboardKey and Mibo's backend-neutral KeyCode.

Functions for translating between MonoGame's Keys and Mibo's backend-neutral KeyCode.

Backend-neutral keyboard key. Covers the standard US-layout key set that any game backend (raylib, MonoGame, SDL, …) can produce.

Mouse subscription helpers.

Functions for translating between raylib's MouseButton and Mibo's backend-neutral MouseButtonCode.

Backend-neutral mouse button.

Mouse button state changes for a single frame.

Mouse state delta containing position and button changes.

Touch subscription helpers.

Touch input state containing all active touch points.

A single touch point for touch input.

Touch point state for tracking individual touch lifecycle.

Represents a physical hardware input trigger, expressed in backend-neutral codes so an InputMap is portable across backends.