Nucleus handler tools › Docs › ProtoInput › SetControllerIndex

ProtoInput.SetControllerIndex

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

ProtoInput.SetControllerIndex(
  instanceHandle: number,
  controllerIndex: number,
  controllerIndex2: number,
  controllerIndex3: number,
  controllerIndex4: number
): void

Chooses the controllers the game instance sees through the XinputHookID hook. Parameters: the instance handle, then the controller for the game's XInput slots 1 to 4, counted from 1; 0 means no controller in that slot. With ProtoInput.SetTranslateXinputtoMKB on, the first controller is translated to mouse and keyboard and every slot reports no controller.

✎ AI-written, based on Nucleus ProtoInput.cs (SetControllerIndex), ProtoInputLoader Inject.cpp, ProtoInputHooks PipeCommunication.cpp (SetControllerIndex), ProtoInputHooks XinputHook.cpp (GetTargetControllerIndex). Not from the official docs. Is it wrong? Tell us

Handler API docs

Is this right? Tell us what's wrong
Stuck, or not sure? Ask other handler authors: Discordr/nucleuscoop