🌟 Why Use Godot Advanced Input System (GAIS)?

1. Input Source & Device Separation:
   Decouples physical hardware from player entities. This makes local co-op straightforward to implement while allowing a single player to seamlessly use multiple input devices simultaneously (e.g., hybrid keyboard/mouse and gamepad setups).
2. Broad Device Support:
   Full support for standard desktop and mobile input sources: Keyboard, Mouse, Gamepad/Controller, and Touchscreen.
   (Note: Currently excludes Gyroscope, MIDI, built-in InputAction, and Shortcut events).
3. InputMap Independent:
   Bypasses Godot's static InputMap strings entirely, interfacing directly with hardware input events for zero-overhead, highly customizable routing.
4. Context Switching (Push & Pop Stack):
   Push and pop layered input contexts dynamically to handle distinct gameplay states (e.g., foot movement, vehicle control, inventory menus, or dialogue screens) where each situation requires its own scheme.
5. Input Prioritization:
   Fine-grained priority control over input consumption across multiple actions and overlapping active contexts.
6. Action State Machines:
   Actions deliver much more than raw primitives. Every action exposes lifecycle states (STARTED -> PROCESSING -> ENDED) along with comprehensive context: the sender action, triggering raw events, press duration, and metadata.
7. Input Modification via Proxies:
   Inspired by Unreal Engine's Input Triggers and Modifiers, GAIS uses extensible Input Proxy resources. It includes a complete library of standard proxies, custom utility proxies, and base templates with visual reference charts in the docs.
8. Accumulation & Directional Trimming:
   Easily composite multiple inputs into composite vectors (e.g., combining WASD/D-Pad into a normalized Vector2) or isolate continuous axis streams into discrete directional triggers (e.g., isolated "Mouse Motion Up").
9. Runtime Rebinding:
   Native, hassle-free key and button rebinding at runtime—crucial for responsive settings menus and persistent player profiles.
10. Input-to-Icon Mapping:
    Includes an integrated mapping resource that automatically correlates inputs to visual button prompts, simplifying dynamic UI glyph swaps and controller-aware HUDs.

📖 Documentation & "How to Use" Guide

For step-by-step "How to Use" guide and complete architecture breakdown, visit the documentation site:
👉 Online Documentation & How to Use Guide