Nucleus handler tools โ€บ Docs โ€บ Game.Hook โ€บ DInputEnabled

Game.Hook.DInputEnabled

Open in the workbench (search, and try it in a handler)

Game.Hook.DInputEnabled: boolean

If enabled, will allow DInput devices to be used as a device input in Nucleus. This doesn't mean that it will work with the game if not supported.

AI-writtenAI-written. Based on: Nucleus DevicesFunctions.cs (opens in a new tab) (if g.Hook.DInputEnabled || g.Hook.XInputReroute || g.ProtoInput.DinputDeviceHook); XInputPlusDll.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

True makes the setup screen list DirectInput controllers (as do Game.Hook.XInputReroute and Game.ProtoInput.DinputDeviceHook); with the custom XInput DLL it also goes into its settings. Only for the rare games that read controllers through DirectInput; almost every handler sets it false.

Is "In practice" right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).
Game.Hook.DInputEnabled = false;
Is the doc right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).

Handler API docs

Stuck, or not sure? Ask other handler authors: Discordr/nucleuscoop