Nucleus handler tools βΊ Docs βΊ Checks
An option nothing reads
Why it matters
Nucleus shows the option and stores the player's choice, but never reads it itself (Game.ShowOptionAsStep only asks for it): only the handler's own Context.Options["key"] does. With no such read, the choice changes nothing, and players think a setting works when it doesn't. Shown faded, like unused code.
Example
β Wrong
Game.AddOption("FPS cap", "", "fps", ["30", "60"]);
Game.Play = function () {
Context.StartArguments = "-windowed";
};β Right
Game.AddOption("FPS cap", "", "fps", ["30", "60"]);
Game.Play = function () {
var fps = Context.Options["fps"];
Context.StartArguments = "-windowed -fps " + fps;
};How to fix it
Read the option where the choice matters (usually in Game.Play), check the key is spelled the same in both places, or remove the option. The quick fix removes the line when nothing else names the key.
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": { "unused-option": "off" } in your settings. Notepad++: Plugins βΊ Nucleus Co-op handlers βΊ Settings. Command line: ncdev lint --rule unused-option=off. Other editors: the lint.rules setting of ncdev lsp.