Nucleus handler tools › Docs › Checks
Old input options fighting Proto Input
Why it matters
With Proto Input and several keyboards and mice, the old input options (Game.HookGetCursorPos, Game.SendNormalMouseInput…) must be off: several default to on and get in Proto Input's way.
Example
✗ Wrong
Game.ProtoInput.InjectStartup = true;
Game.SupportsMultipleKeyboardsAndMice = true;
Game.HookGetCursorPos = true;✓ Right
Game.ProtoInput.InjectStartup = true;
Game.SupportsMultipleKeyboardsAndMice = true;
Game.HookGetCursorPos = false;
Game.HookSetCursorPos = false;
Game.HookGetKeyState = false;
Game.HookGetAsyncKeyState = false;
Game.HookGetKeyboardState = false;
Game.HookMouseVisibility = false;
Game.SendNormalMouseInput = false;
Game.SendNormalKeyboardInput = false;
Game.DrawFakeMouseCursor = false;How to fix it
Set the old options it lists to false; the quick fix adds the lines.
Turn it off, or change how it shows
Each check can be shown as an error, warning, info or hint, or turned off. VS Code: "splitscreenme.lint.rules": { "protoinput-legacy-hooks": "off" } in your settings. Notepad++: Plugins › Nucleus Co-op handlers › Settings. Command line: ncdev lint --rule protoinput-legacy-hooks=off. Other editors: the lint.rules setting of ncdev lsp.
Is this right?
Tell us what's wrong