When unlocking a recipe via a usable item, the system behaves differently depending on the recipes Context.

Root cause was traced to isRecipeUnlocked performing an isContextCompatible check. That validation is appropriate for crafting/workstation requests but not relevant to the unlocking flow, causing the unlock system to mis-detect "already unlocked" for non-player contexts.

To fix: Move the context compatibility validation step out of the isRecipeUnlocked function and into the canCraftRecipe function instead.

Update 1/29: This fix has been submitted to Epic and is currently awaiting approval.

Update 1/30: This fix is now live.

This problem is specific to Unreal Engine 5.5 and is not an issue in any of the other supported versions.

In UE 5.5, the Enhanced Input actions used for hotbar slots (1, 2, 3, etc.) and modifier keys (CTRL, ALT, SHIFT) logic doesn’t run as expected. This is because of a UE 5.5 engine-level bug where the Action Value coming from an Enhanced Input event can incorrectly return 0 when the event executes via the Started path.

You can learn more about this Unreal 5.5 issue here.

To work around the UE 5.5 bug, either upgrade your project to a later version of the engine, or update the affected Enhanced Input events in UI_Hotbars and UI_InventorySystemHUD:

1. Switch the input event execution from Started to Triggered.
2. Add a Pushed trigger on the Input Action, or add a DoOnce node on the Triggered execution path, and reset the DoOnce on Completed / Canceled.

Update 1/14: This fix has been submitted to Epic and is currently awaiting approval.

Update 1/14: This fix is now live.