Nucleus handler tools › Docs › Checks

A message Proto Input can't block

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

Why it matters

Proto Input looks blocked messages up in its own list. A number that isn't in it blocks a different message, or nothing.

Example

✗ Wrong

Game.ProtoInput.InjectStartup = true;
Game.ProtoInput.MessageFilterHook = true;
Game.ProtoInput.BlockedMessages = [0x0009];

✓ Right

Game.ProtoInput.InjectStartup = true;
Game.ProtoInput.MessageFilterHook = true;
Game.ProtoInput.BlockedMessages = [0x0008];

How to fix it

Pick the message by name from the list (hover a number to see which message it is).

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": { "blocked-message": "off" } in your settings. Notepad++: Plugins › Nucleus Co-op handlers › Settings. Command line: ncdev lint --rule blocked-message=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