Nucleus handler tools โ€บ Docs โ€บ Game โ€บ XInputPlusDll

Game.XInputPlusDll

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

Game.XInputPlusDll: string[]

Set up XInputPlus | If multiple dlls required, use comma seperated strings.

Category: Input

AI-writtenAI-written. Based on: Nucleus XInputPlusDll.cs (opens in a new tab) (SetupXInputPlusDll); GenericGameHandler.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (opens in a new tab).

In practice

The names XInputPlus' DLL is copied in as, next to the game in each instance (for example xinput1_3.dll), with its settings telling it which controller that instance gets. Handlers that list DLLs nearly always set Game.Hook.XInputEnabled too. ["xinput1_3.dll"] is the usual list, above all in Unreal Engine games; some games load xinput1_4.dll instead.

Is "In practice" right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).
Game.XInputPlusDll = ["xinput1_3.dll"];
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