I’ve been banned for this officially as of just now. I don’t always play with a controller, and sometimes when I boot up Halo I forget that I last played on a controller when intending to play on KBM. Instead of the game detecting that there is in fact no gamepad in existence in the observable universe as far as the computer knows, it just keeps the input defaulted to gamepad. This means that I join a game not realizing it as there also is no warning that I have gamepad input enabled with no gamepad hooked up, and then when I join the game I am locked with no way of controlling my character and no way of switching my input as the game rather foolishly has input changing disabled, even on social matchmaking where there are no input restrictions. If I, like today, happen to let a friend borrow my Xbox controller for a few days then the only choices I have are to be AFK the whole match or to quit. Both are equally frustrating for my team mates and both will result in me being ejected from the lobby and then temporarily banned from matchmaking.
This needs to be fixed. There needs to be a detection system for input devices. Plenty of other AAA games have them. Halo is a triple-A game. It should have some sort of detection. Better yet, don’t follow in CoD’s mistaken footsteps and stop people from changing inputs in social matches where there’s gonna be a mix of people on both inputs anyway. It’s not like there’s any sense of team balancing, anyway. Half the time I play it’s a team of sweats vs a team of casual players who don’t care about stats and the HCS tryout players end up smashing the other team 50-15 anyway. There is no reason to restrict swapping input if you’re literally going to ban people for NOT EVEN BEING ABLE TO PLAY.
Thank you for coming to my TEDX Talk. I think this rant took enough time for my ban to expire. Happy hunting, everyone.
. I was condemned to stay a poor stuck target just good to be shooted at will
, by reflex I grabbed my mouse, thinking, too bad I will pass the game like that but… meeeh
… since the introduction of prefered input lock impossible to do that, even if its a accidental banal disfunction.
: In-fine, the good way would be to simply be able to switch from one of the available inputs to the other when we want (/need) if we have not enabled an input-restricted search in matchmaking options.
).