https://gsplay.genomestudios.ca/categories/input/Recent content in Input on GS_Play Gameplay FrameworkHugoen-ushttps://gsplay.genomestudios.ca/docs/the_basics/unit/input/Mon, 01 Jan 0001 00:00:00 +0000https://gsplay.genomestudios.ca/docs/the_basics/unit/input/<p>The Input Data system is the pipeline that converts raw hardware signals into structured intent your movement code can consume. It sits between the active input profile and the mover stack, so controllers, movement components, and action systems all read from a single consistent source rather than polling hardware directly. Swapping input profiles at runtime — for remapping, controller switching, or accessibility options — requires no change to any downstream component.</p>https://gsplay.genomestudios.ca/docs/the_basics/core/gs_options/Mon, 01 Jan 0001 00:00:00 +0000https://gsplay.genomestudios.ca/docs/the_basics/core/gs_options/<p>The Options system manages player-facing configuration and input handling. Its primary feature is the Input Profile system, which provides group-based input binding management that can be toggled at runtime without code changes.</p> <p>For architecture details, component properties, and extension patterns, see the <a href="../../../framework/core/gs_options/">Framework API reference</a>.</p> <p><img src="https://gsplay.genomestudios.ca/images/core/OptionsManager.png" alt="Options Manager component in the O3DE Inspector"></p> <p> </p> <h2 id="contents">Contents</h2> <ul> <li><a href="#options-manager">Options Manager</a></li> <li><a href="#input-profiles">Input Profiles</a></li> <li><a href="#input-groups">Enabling and Disabling Input Groups</a></li> <li><a href="#input-flow">How Input Flows</a></li> <li><a href="#quick-reference">Quick Reference</a></li> <li><a href="#glossary">Glossary</a></li> <li><a href="#see-also">See Also</a></li> </ul> <hr> <h2 id="options-manager">Options Manager</h2> <p>The Options Manager is a singleton that holds the active Input Profile and makes it available to all Input Reader components. It responds to the Game Manager lifecycle automatically.</p>https://gsplay.genomestudios.ca/docs/the_basics/unit/Mon, 01 Jan 0001 00:00:00 +0000https://gsplay.genomestudios.ca/docs/the_basics/unit/<p>GS_Unit is the complete character control system for GS_Play. It handles how entities are registered as controllable units, which controller possesses each unit, how raw player input is captured and converted into intent, and how that intent is translated into physical movement through a modular stack of movers, grounders, and influence fields.</p> <p>For architecture details, component properties, and extending the system in C++, see the <a href="../../framework/unit/">GS_Unit API</a>.</p> <hr> <h2 id="quick-navigation">Quick Navigation</h2> <table> <thead> <tr> <th>I want to…</th> <th>Feature</th> <th>API</th> </tr> </thead> <tbody> <tr> <td>Register units, track active controllers, or spawn units at runtime</td> <td><a href="#unit-manager">Unit Manager</a></td> <td><a href="../../framework/unit/unit_manager/">API</a></td> </tr> <tr> <td>Possess and release units with player or AI controllers</td> <td><a href="#controllers">Controllers</a></td> <td><a href="../../framework/unit/unit_controllers/">API</a></td> </tr> <tr> <td>Capture raw input and convert it into structured movement intent</td> <td><a href="#input-data">Input Data</a></td> <td><a href="../../framework/unit/input_data/">API</a></td> </tr> <tr> <td>Move characters with movers, grounders, and movement influence fields</td> <td><a href="#movement">Movement</a></td> <td><a href="../../framework/unit/units/">API</a></td> </tr> </tbody> </table> <hr> <h2 id="installation">Installation</h2> <p>GS_Unit requires GS_Core. Add both gems to your project before using any Unit components.</p>