Nucleus handler tools › Docs › Checks

Proto Input options that never start

Warningprotoinput-inactiveA Nucleus check · Probably wrong: Nucleus runs it, but not the way you meant.

Why it matters

Proto Input only starts with Game.ProtoInput.InjectStartup or one of the InjectRuntime_… options. Without one, every other Game.ProtoInput option is ignored.

Example

✗ Wrong

Game.ProtoInput.FocusHooksHookGetFocus = true;

✓ Right

Game.ProtoInput.InjectStartup = true;
Game.ProtoInput.FocusHooksHookGetFocus = true;

How to fix it

Turn on the way Proto Input should start (usually Game.ProtoInput.InjectStartup = true), or remove the unused options.

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-inactive": "off" } in your settings. Notepad++: Plugins › Nucleus Co-op handlers › Settings. Command line: ncdev lint --rule protoinput-inactive=off. Other editors: the lint.rules setting of ncdev lsp.

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