You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2020. It is now read-only.
A list of generally used keys would be scanned using GetKeyState and when their state changes call a pawn callback. (Obviously this would be much like OnPlayerKeyStateChange, but without the bitmask of keys.)
Mouse Movement
The mouse position would be repeatedly checked (every 20-50 ms if enabled?) when the mouse is enabled. When it is changed call a pawn callback. OnPlayerClick would still be called on clicks alongside this.
The text was updated successfully, but these errors were encountered:
I think it would be better to register a set of keys to monitor, send that to the client when they connect so the client side only sends updates for those keys. This way, large servers can ensure no data is wasted (maybe even allow changing of this key set in runtime so if a player transitions to a state where they no longer need to use a certain key, that key is never sent (such as a different sub-gamemode or mission)).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Key Presses
A list of generally used keys would be scanned using GetKeyState and when their state changes call a pawn callback. (Obviously this would be much like OnPlayerKeyStateChange, but without the bitmask of keys.)
Mouse Movement
The mouse position would be repeatedly checked (every 20-50 ms if enabled?) when the mouse is enabled. When it is changed call a pawn callback. OnPlayerClick would still be called on clicks alongside this.
The text was updated successfully, but these errors were encountered: