Key Conflict Display Plus

Minecraft 26.2 registers every F3 debug combo (F3+B, F3+A, F3+D, ...) as a real key binding, but the vanilla controls screen only compares raw key codes. The result: any binding that shares a letter with a debug combo gets flagged as conflicting, even though pressing B alone never triggers the debug function, and holding F3 never fires your normal bindings.

Key Conflict Display Plus fixes those false positives, in the vanilla controls screen and in Controlling's key binding list alike.

Features

No more false conflicts

• F3+ debug combos are no longer treated as conflicting with normal bindings. While F3 is held, vanilla never dispatches the key to regular bindings, so the two never actually fight over input.
• Keys that only respond inside their own GUI (JEI's R / U / left / right click lookups, Client Sort's middle-click sort, and similar) are exempted by default. Outside their screen they simply do nothing, so a shared key is harmless.
• Real conflicts stay. Two bindings that genuinely answer the same physical key at the same time are still marked red (for example, two debug combos both bound to C).

Clearer key labels

• Debug combos display as F3+B instead of just B, so you can see the modifier at a glance.
• Unbound keys show as "Unbound" instead of the confusing "Unknown Key".

Everything is configurable

On first launch the mod generates config/keyconflictplus.json:

• suppressDebugComboConflicts — exempt F3 combos from conflict checks (default: true)
• showDebugComboLabel — render debug combos as F3+B (default: true)
• suppressScopedConflicts — exempt GUI-only keys (default: true)
• friendlyUnboundLabel — show "Unbound" instead of "Unknown Key" (default: true)
• scopedKeyMappings — register your own GUI-only keys; supports * wildcards (e.g. key.jei.*)
• ignoredKeyMappings — keys that should never take part in conflict detection at all

Key names are the ones used in options.txt without the key_ prefix, for example key.jei.showUses or gui.xaero_open_map.

Requirements

• Minecraft 26.2 with Fabric Loader 0.19.5 or newer
• Controlling (by BlameJared) — required; this mod patches the same conflict logic that Controlling uses
• Client-side only. Works on multiplayer servers without being installed there.
• Fabric API is not required.

Notes

No gameplay changes. The mod only affects how the controls screen reports key conflicts.