Nucleus handler tools › Docs › Checks
Game or Context replaced
Why it matters
Nucleus gives the handler its own Game and Context and reads the settings from those. A variable, parameter or function of the same name puts a new object in their place, so Nucleus never sees what is set on it: with var Game = {} at the top it finds no Game.Play, and a var Context in Game.Play loses StartArguments.
Example
✗ Wrong
Game.Play = function () {
var Context = {};
Context.StartArguments = "-windowed";
};✓ Right
Game.Play = function () {
Context.StartArguments = "-windowed";
};How to fix it
Remove the declaration, or give your own variable another name.
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": { "replaces-nucleus-object": "off" } in your settings. Notepad++: Plugins › Nucleus Co-op handlers › Settings. Command line: ncdev lint --rule replaces-nucleus-object=off. Other editors: the lint.rules setting of ncdev lsp.