The problem is that these create input events on behalf of the user.
forexample: When pressing A while still having D pressed, the keyboard sends a KEY_UP=D event even as the user is still pressing D.
As for your comparisom, lowering latency is something different, if anything it’s attempting to make the users actions registered more accurately.
Do note that without this kind of processing, the games already knows that D is still pressed while A is presses, and they decide how to act on it. Games handle this differently, a common one being both keys as “stand still”.
So we’re:
creating new input eventson behalf of the user
tricking the game to to avoid a state the devs have intended
resulting in a huge advantage for the player.
In my opinion this should be implemeted on a OS level for all to use, but I don’t struggle one bit to see how this is disruptive and a no-go in competitive games.
The problem is that these create input events on behalf of the user. forexample: When pressing A while still having D pressed, the keyboard sends a KEY_UP=D event even as the user is still pressing D.
As for your comparisom, lowering latency is something different, if anything it’s attempting to make the users actions registered more accurately.
Do note that without this kind of processing, the games already knows that D is still pressed while A is presses, and they decide how to act on it. Games handle this differently, a common one being both keys as “stand still”.
So we’re:
In my opinion this should be implemeted on a OS level for all to use, but I don’t struggle one bit to see how this is disruptive and a no-go in competitive games.
You’re confusing changing the priority of the inputs with creating them. Not the same thing.
Tons of keyboard/mice features are applied per device. If you want to do this on yours, it’s free. Look it up.
There’s no barrier for entry and it makes the gameplay quicker. There are no downsides here, this feels like plain gatekeeping.