Godot 4.7: Input Device IDs
- Mouse and keyboard are no longer device ID
0— useInputEvent.DEVICE_ID_MOUSEandInputEvent.DEVICE_ID_KEYBOARD. - NEVER compare
event.device == 0for mouse/keyboard; joypads may legitimately use ID 0.
/godot-input-handling
@9d6e91eExpert patterns for input handling covering InputMap actions, InputEvent processing, controller support, rebinding, deadzones, and input buffering. Use when setting up player controls, implementing input systems, or adding gamepad/accessibility features. Keywords InputMap, InputEvent, gamepad, controller, rebinding, deadzone, input buffer.
Ask your Agent
Use this Skill: https://skilld.dev/gh/thedivergentai/gd-agentic-skills/godot-input-handling
This session only. Nothing lands on disk.
≈63 tokens on demand. Your agent reads this file only when SKILL.md points to it.
Source: SKILL.md on GitHub
Third-party checks
1 warning17d4 checks · Risk MEDIUM
- Gen Agent Trust Hub17d
The skill provides comprehensive patterns for Godot input handling, but includes a medium-severity risk involving unsafe deserialization of local configuration files via bytes_to_var and str_to_var.
- Socket17d
No alerts
- Snyk17d
Risk: LOW · No issues
- Runlayer7mo
1/4 files flagged
Provenance
Signed by skilld at 9d6e91e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub 3 weeks ago.
Activeupdated 2 months ago