Nucleus handler tools › Docs › ProtoInput › SetXinputtoMKBkeys
ProtoInput.SetXinputtoMKBkeys
Open in the workbench (search, and try it in a handler)
ProtoInput.SetXinputtoMKBkeys(
instanceHandle: number,
XinputtoMKBAkey: number,
XinputtoMKBBkey: number,
XinputtoMKBXkey: number,
XinputtoMKBYkey: number,
XinputtoMKBRSkey: number,
XinputtoMKBLSkey: number,
XinputtoMKBrightkey: number,
XinputtoMKBleftkey: number,
XinputtoMKBupkey: number,
XinputtoMKBdownkey: number,
XinputtoMKBstickR: number,
XinputtoMKBstickL: number,
XinputtoMKBstickright: number,
XinputtoMKBstickleft: number,
XinputtoMKBstickup: number,
XinputtoMKBstickdown: number,
XinputtoMKBoption: number,
XinputtoMKBstart: number,
XinputtoMKBsens: number,
XinputtoMKBsensmult: number,
XinputtoMKBDeadzone: number
): void
Sets the controller-to-keyboard mapping used by ProtoInput.SetTranslateXinputtoMKB. Parameters, in order: the instance handle; virtual-key codes for A, B, X, Y, right shoulder, left shoulder, D-pad right, left, up, down, right stick press, left stick press, stick right, left, up, down, Back and Start; then sensitivity, acceleration and deadzone.
✎ AI-written, based on Nucleus ProtoInput.cs (SetXinputtoMKBkeys), ProtoInputLoader Inject.cpp, ProtoInputHooks PipeCommunication.cpp (SetXinputtoMKBkeys), ProtoInputHooks TranslateXtoMKB.cpp (ButtonStateImpulse, Sens, Sensmult, Deadzone), Nucleus ProtoInputLauncher.cs (defaults). Not from the official docs. Is it wrong? Tell us