Input (Blueprint)

Blueprint Cheats integrates with Enhanced Input on two layers:

1. A dedicated Input Mapping Context that carries the menu hotkey and (optionally) any project-specific bindings.
2. Per-cheat Input Action assets that fire individual cheats directly.

The cheat IMC

The plugin defines its own IMC class — Blueprint Cheats Input Mapping Context — which extends the standard IMC with a single extra field:

The shipped default is /BlueprintCheats/Input/IMC_BlueprintCheats_Default, with IA_BlueprintCheats_Menu as the menu hotkey.

Replacing the IMC

You don't have to use the shipped IMC. To roll your own:

1. Right-click in the Content Browser → Input → Blueprint Cheats Input Mapping Context.
2. Add bindings as you would on a standard IMC.
3. Set Menu Hotkey to whatever Input Action should open the overlay.
4. Point Project Settings → Blueprint Cheats → Input Mapping Context at it.

The subsystem registers the IMC at priority 0 on the local player's Enhanced Input subsystem on every world match start.

Per-cheat hotkeys

Every cheat has an Input Action field on its Class Defaults. When set, the subsystem binds:

• Triggered → fires Execute once.
• Ongoing → also fires Execute while the key is held, if the cheat's Continue Executing With Ongoing Key Press field is on (default).

Turn that field off for toggle-style cheats where holding the key shouldn't retrigger.

Hotkey arguments

Hotkey invocations pass an empty token list to Execute Raw Arguments. That means parsing only succeeds when every argument either has a configured Default Value or is marked Optional. Otherwise the hotkey will error with the usual missing-argument message.

For cheats meant to be hotkey-driven, either omit arguments entirely or default every argument.

Sample input assets

The plugin ships:

• IA_BlueprintCheats_Menu — toggles the overlay.
• IA_BlueprintCheats_ResetLevel — example per-cheat hotkey, used by the shipped BPCheat_BlueprintCheats_ResetLevel.
• IMC_BlueprintCheats_Default — wires both actions to default keys.

These live under /BlueprintCheats/Input/. They're reasonable starting points to copy and rebind.

Mobile

iOS and Android skip both the menu IMC registration and the per-cheat hotkey bindings. Cheats can still be invoked via console commands or by calling Execute Script on the subsystem from your own UI.

If you need the overlay menu on mobile, surface it from your own input path (a debug button, gesture, etc.).