unreal-inputcore

Name: unreal-inputcore
Availability: InStock
Author: Orion

Analyze Unreal Engine FKey and InputCore systems for input compatibility issues.

16|3|Updated Jun 13, 2026

Search Tags:#game development #unreal engine #commoninput #enhancedinput #inputcore #fkey #eKeys

Ready to run

npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill unreal-inputcore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unreal-inputcore
Source: https://github.com/OrionUE/Orion_FreeEdition/tree/main/.agents/skills/unreal-inputcore
Command: npx skills add https://github.com/OrionUE/Orion_FreeEdition --skill unreal-inputcore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers diagnose and modify Unreal Engine low-level input systems without confusing key identity, input state, action mappings, and UI input layers.

Core Features & Use Cases

InputCore Analysis: Guides work with FKey, EKeys, FKeyDetails, FInputKeyManager, key metadata, classifications, and platform input conversion.
Legacy Input Support: Helps inspect UPlayerInput, UInputComponent, action and axis mappings, and input component stack behavior alongside modern systems.
Compatibility Workflows: Clarifies boundaries between InputCore, EnhancedInput, CommonInput, and project-specific input frameworks during debugging and implementation.

Quick Start

Use the unreal-inputcore skill to analyze this Unreal Engine input issue and identify the relevant FKey, InputCore, or legacy input systems involved.

Frequently Asked Questions about unreal-inputcore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does FKey identity work in Unreal Engine InputCore and how do I resolve key mapping conflicts?▼

FKey identity in Unreal Engine InputCore defines unique input keys across platforms, resolving mapping conflicts by inspecting EKeys, FKeyDetails, and FInputKeyManager metadata to validate keyboard, mouse, gamepad, and touch input behaviors accurately.

What is the best way to debug Unreal Engine legacy input compatibility with EnhancedInput?▼

Debugging Unreal Engine legacy input compatibility with EnhancedInput requires inspecting UPlayerInput and UInputComponent stack boundaries, clarifying action and axis mappings alongside modern input systems to isolate framework conflicts during project implementation.

Can I use CommonInput with Unreal Engine InputCore to handle platform key conversion for gamepad and touch?▼

Yes, CommonInput integrates with Unreal Engine InputCore for platform key conversion, utilizing FKeyDetails and FInputKeyManager to standardize gamepad, touch, and keyboard metadata across different hardware platforms within your project input framework.

Why does my Unreal Engine action mapping fail when migrating UPlayerInput to EnhancedInput?▼

Unreal Engine action mapping fails during UPlayerInput migration to EnhancedInput due to unresolved module dependencies and legacy input component stack behavior, requiring engine source inspection to verify FKey classifications and input state boundaries.

Do I need engine source inspection to fix Unreal Engine FKeyDetails metadata issues?▼

Yes, resolving Unreal Engine FKeyDetails metadata issues requires accurate engine source inspection to validate EKeys classifications, verify InputCore module dependencies, and ensure correct low-level input behavior for keyboard, mouse, gamepad, and touch devices.