EVENT PROCESSINPUT: Difference between revisions
Jump to navigation
Jump to search
Doom64hunter (talk | contribs) m This event can no longer be used to lock mouse input because the mouse input is now updated at the framerate, not the game's ticrate. |
Doom64hunter (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
EVENT_PROCESSINPUT is a [[EDuke32_event_list|Game Event]]. | EVENT_PROCESSINPUT is a [[EDuke32_event_list|Game Event]]. | ||
This [[event]] is called when the game processes input from the player, before any of the other input events. It can be used with [[getinput]] to check for particular button presses. | This [[event]] is called when the game processes input from the player, before any of the other input events. | ||
It can be used with [[getinput]] to check for particular button presses. | |||
[[Category:Events]] | [[Category:Events]] | ||
[[Category:Input manipulation]] | [[Category:Input manipulation]] | ||
Latest revision as of 14:04, 4 February 2022
| Event ID | player# | THISACTOR | RETURN | |
|---|---|---|---|---|
| EVENT_PROCESSINPUT | player that executed the input | player->i | 0 values |
EVENT_PROCESSINPUT is a Game Event.
This event is called when the game processes input from the player, before any of the other input events.
It can be used with getinput to check for particular button presses.