“Enable Debug Input” can affect Fortnite controls after closing UEFN

Summary

I discovered a potential issue between UEFN and the Fortnite client.
During an editing session in UEFN, it is possible to enable debug inputs through:
Debug Commands → Enable Debug Input

Once enabled, a controller button can be assigned to a debug command. In my case, I assigned the D-pad Up button to a debug command that gives gold coins.
The issue occurs if I close UEFN without disabling “Enable Debug Input” first.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Other

Steps to Reproduce

1- Open UEFN and start an editing session.
2- Go to Debug Commands.
3- Enable Enable Debug Input.
4- Assign a controller button, for example D-pad Up, to a debug command.
5- Close UEFN without disabling Enable Debug Input.
6- Launch Fortnite normally.
7- Enter a Battle Royale match.
8- Try to use the D-pad Up button.

Expected Result

The D-pad Up button should work normally according to Fortnite’s default controller bindings, including opening the inventory.

Observed Result

The D-pad Up button no longer works correctly in Fortnite Battle Royale.

Platform(s)

PC Windows 11

Additional Notes

The issue appears to be related to closing UEFN while Enable Debug Input is still enabled.

This could potentially affect other controller buttons, debug commands, or Fortnite experiences as well, not just the D-pad Up button.

It may be worth checking whether UEFN’s debug input state is properly reset when UEFN is closed, so that debug inputs cannot interfere with the Fortnite client afterward.

Seems to be related to this I also have reported a similar issue where my building buttons become blocked If I don’t remember to disable debug inputs before leaving uefn

Ah yes, indeed, it’s the same problem.

1 Like