Describe the bug
If Steam is currently running in the background, all Gamepad inputs under Bluetooth mode do not work. This doesn't affect USB mode. Most likely, this is probably due to the way Steam Input and GLFW handle Bluetooth Gamepad devices.

To Reproduce

1. Steam must be launched first before launching with the Midnight Controls mod.
2. Connect your Game Controller of choice under Bluetooth. For my case: I use both DualShock 4 and DualSense Controller.
3. Launch Minecraft Fabric
4. Try to press any buttons
5. [Optional] Open a new or existing world
6. Gamepad Inputs no longer work

Alternatively: you can also reproduce this issue by launching Steam during your Minecraft gaming section. That also means the last Button/Joystick press is going to be active until you reconnect your controller (under USB mode)

Workarounds

1. Close Steam
2. Disconnect your Controller of choice and then reconnect it.
3. Now Gamepad inputs work as intended.

Expected behavior
Gamepad Inputs under Bluetooth mode should always work while Steam is currently running in the background.

Desktop (please complete the following information):

• OS: Windows 11 21H2 (Build 22000.708)
• Minecraft 1.19
• Fabric Installer 0.11.0
• Fabric Loader 0.14.7-1.19
• Fabric API 0.55.3+1.19
• Mods: sodium-fabric-mc1.19-0.4.2+build.16, spruceui-1.5.2-fabric1.16, midnightcontrols-1.1.0+1.19

1. Your FLoader version is seriously outdated
2. Yeah Steam is weird with gamepad inputs. It likes to take it all for itself. Sometimes I had issues with gamepads not working unless Steam was open, which is insanely weird. I have no fucking clue what Steam is doing but it's doing some weird shit

1. Update Fabric
2. You should get into the habit of fully exiting Steam when opening certain programs, for example DS4Windows.

@ExoPlant: Your FLoader version is seriously outdated

...Actually, that was an oversight on my part. (Sorry for the late reply)

At the time of the issue report (June 10th, 2022), I was running on the latest version of FLoader, however, I accidentally used Fabric API's version naming scheme into the Fabric Loader version. That part has been stealthily edited to include the proper FLoader ver. number.

but now that I'm back from the future, I can confirm that the issue still persist with Version: 1.5.0, with Fabric API (fabric-api-0.59.0+1.19.2) and FLoader (0.14.9-1.19.2). Hopefully, I can avoid that mistake again, unless I did it again?

@spudpiggy: 2. You should get into the habit of fully exiting Steam when opening certain programs, for example DS4Windows.

While ya correct that certain programs don't play nicely, DS4Windows (more specifically, the "soon-to-be-discontinued" Ryochan4 fork) doesn't have any problem with Steam Input conflicting with each other. In fact: Steam Input can automatically be disabled if DS4 Output is enabled via DS4Windows, but they don't have any problem with you enabling Xbox 360 Mode...

However: if a game uses Steam Input API or a game developer explicitly opts-in to Steam Input for a specific Controller Type: you'd receive a pop-up warning for it.

Regardless of that, that's something I also pointed out as a workaround to that problem. Whenever that occurs; You'd have to fully exit Steam just for one program.

edit: oh, and I'm running on Steam Beta Client of August 10th, 2022 build; in case anyone is curious.