#Input Routing

1 messages · Page 1 of 1 (latest)

rustic spade
#

Instead of handling my input directly inside my Player.cs script, do you guys think its worth using some kind of Input Router class. The way i imagined it is having a dedicated struct something like 'IInputFrame', where i basically grab all inputs in a fixed PreUpdate order, with a low script execution order. That way the event callbacks cant fire before physics

#

what im hoping to accomplish is that i dont need to call the inputsystem apis directly from other scripts, but rather have them just read that struct

short root
#

Seems pointless unless you want some object to recieve input from other sources instead via an abstraction layer