MonoGame input, camera and UI
Turns device states into single, deliberate game or menu actions. It accounts for virtual resolution, black bars, focus loss and controller disconnection, preventing offset clicks and repeated confirmations.
monogame-input-camera-ui
See how it helpsWhen is it useful?
Use when resizing, controller changes or focus loss cause incorrect clicks or stuck movement.
What does it help you do?
- Tracks previous and current input with one consumer for each action edge.
- Converts pointer coordinates through virtual resolution and letterboxing.
- Handles focus loss and controller disconnection explicitly.
Try asking this
Our tactics game uses a fixed virtual resolution with black bars. Click a unit near the edge, hold Confirm while opening a dialog and disconnect the controller. Selection must match the world cell, confirmation must occur once and the menu must offer a usable remaining input path.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
MonoGame — input camera ui
Use when implementing MonoGame input edges, controllers, cameras, UI or resolution changes.
Version and project gate
Inspect Project and .NET target, MonoGame package/backend, Game loop settings, MGCB files/tool versions, content root, GraphicsProfile, platform libraries and existing screen/state architecture. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Store previous/current input snapshots and define one consumption point for action edges. Keep virtual game resolution separate from backbuffer and window coordinates. Convert mouse positions through viewport/letterbox transforms and define focus loss and controller disconnection behavior.
Deliver
An input/resolution contract with usable play and menu interactions. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Reading an edge independently in several systems can trigger duplicate commands; mouse coordinates do not automatically match a render target.
Acceptance scenario
Resize and letterbox the window, reconnect a controller and release a held key while the app is unfocused. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Mox. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md