Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
UI/Tools
Summary
Ok, so I’m not sure how old the bug is, BUT I’m assuming it is as old as Lego Fortnite.
Basically, the controls are shared between Lego Fortnite and Battle Royale modes (not sure how many other modes but those 2 are where I noticed it for sure). The bug tying the controls together make it where if you try and remap controls to make it easier for you to play, it will remove the control from elsewhere.
Say you want to aim down your sights and you set that key to the right mouse button. Then, for using an off hand item in Lego Fortnite you also want to use the right mouse button. Well, it will ask you to remove it from targeting (the aim down sights). Then, when you try and set it back to targeting it wants to remove it from the offhand tool in Lego Fortnite.
Steps to Reproduce
Try to set the same button for usage in both Lego Fortnite and Battle Royale.
It will replace whatever that button is currently using in the other mode.
So, setting the key for targeting in Battle Royale and offhand tools in Lego Fortnite as right mouse button will replace one or the other. Also works with other keys.
Expected Result
To be able to use the same key for different functions in different game modes. So being able to use the same key for targeting/swapping etc. in Battle Royale while also using the same key for offhand or swapping to a different tool in Lego Fortnite.
Observed Result
The same key overwrites another function in a different game mode. Setting a key as a function in Lego Fortnite will overwrite and remove that key from Battle Royale controls and vice versa.
Platform(s)
PC
Additional Notes
I get that Lego Fortnite was made in a rush and doesn’t make as much money as other modes, but this is kind of a control scheme issue. I don’t know why the control interface in the settings is trying to overwrite Battle Royale settings by changing keys in Lego Fortnite and vice versa. Could we please get a fix for that?
I have a feeling the issue is some error catches or checks inside the code specifically for the Lego Fortnite setting where it checks after a key is set (whether it was set in Lego Fortnite section or Battle Royale section) to determine if there is a conflict with one or the other.