File / file system module. Module that handles file / file system access.

Input module. Module that handles generalized inputs (keyboard, mouse, joystick, …)

Input events may be defined either in the config file or in code with orxInput_Bind*() functions. They can be changed on the fly, of course, and you can create inputs than don't necessarily map to physical device by using the orxINPUT_TYPE_EXTERNAL value of the enum.

It allows to group everything through the generic input system. Events can be bound to whatever any input source: physical device, GUI “buttons” by activating the input using orxInput_SetValue(), etc… This way, when going from one peripheral to the other, or when going to another platform, only the bindings need to be changed, the processing code itself doesn't change.

Joystick plugin module. Plugin module that handles joystick-like peripherals.

Keyboard plugin module. Plugin module that handles keyboard peripherals.

Mouse plugin module. Plugin module that handles mouse-like peripherals.

• Input
• Joystick inputs
• Keyboard inputs
• Mouse inputs

• Grey's Tutorial 4: Interaction and Physics (Warning: You are recommended to start with Grey's Tutorial 1)