A community about game development.
Rules:
More rules might follow if they become necessary; general rule is don't be a pain in the butt. Have fun! ♥
Accept all inputs. Update on-screen prompts depending on which one was used last.
But be careful with processing those inputs. Team Fortress 2 used to have an exploit where you could move the mouse and tilt a stick and turn twice as fast as you were supposed to be able to.
The way I do it would work well. Treat such vectors as two separate components. Not as X and Y, but Direction and Magnitude. No matter how many ways you can find to break the input, as long as you clamp the magnitude you'll never go faster than intended! This also conveniently solves the √2 problem when moving diagonally.
It's easy. Just check if mouse moves left OR left key is pressed OR joystick is pushed left THEN move left.
The consensus solution. The Steam Deck and Steam Controller's touchpads can result in both mouse and joystick input being used simultaneously. Locking down which input is used prevents this from working as intended.
Ideal for me is auto-switching with a debounce time.
There's been a few incidents where I'm using my gamepad and accidentally bumped my desk/mouse and completely lose my orientation in game. With a debounce, one form of input needs to have completely stopped for a certain period (say 500ms) before starting to register movements on the other input device.
I think I'd find that annoying. If a player wanted to quickly switch to the other input method in an intense moment then they'd just be waiting for half a second for their inputs to register. They'd probably think the game is bugged!
I just pulled 500 randomly. I don't know how long it would take me to throw the gamepad and reach for the mouse. 50 might be more realistic. The point is just to prevent accidental bumps.
I also came in with that comment fully expecting younger and much faster players with their 240Hz monitors to disagree profusely.
While I'm all for dynamic swapping during gameplay, in the menus I suggest an option to disable controller, in case there is a malfunction. Also, to the same problem I'd suggest havinge the mouse cursor to have a) priority, that affects the menu element under the cursor (not the element selected) and b) a fade out time, so it can be active at the same time as controller is active, to prevent the case, where the game detects controller to be drifting. This will be a godsent feature, when, for some reason, even removing the controller does not fix the game detecting the drifting input.
Also, it would be cool to have a manual option to force displayed prompts, not only between keyboard and controller, but also between x-input, Direct-input and PlayStation controllers.