Nucleus handler tools β€Ί Docs β€Ί ProtoInput β€Ί SetDinputDeviceGUID

ProtoInput.SetDinputDeviceGUID

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

ProtoInput.SetDinputDeviceGUID(
  instanceHandle: number,
  Data1: number,
  Data2: number,
  Data3: number,
  Data4a: number,
  Data4b: number,
  Data4c: number,
  Data4d: number,
  Data4e: number,
  Data4f: number,
  Data4g: number,
  Data4h: number
): void
ProtoInput.SetDinputDeviceGUID(
  instanceHandle: number,
  guid: any
): void
AI-writtenAI-written. Based on: Nucleus ProtoInput.cs (opens in a new tab) (SetDinputDeviceGUID, both overloads); ProtoInputLoader Inject.cpp (opens in a new tab); ProtoInputHooks PipeCommunication.cpp (opens in a new tab) (SetDinputDeviceGuid); DinputOrderHook.cpp (opens in a new tab) (SetControllerGuid, Hook_DinputCreateDevice8W).

Chooses the DirectInput controller the DinputOrderHookID hook opens for every DirectInput device the game creates. Parameters: the instance handle and the controller's GUID (Nucleus passes player.GamepadGuid); a second form takes the GUID as 11 numbers (Data1, Data2, Data3, then the 8 bytes of Data4).

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