Repository navigation
v0.6.0 (beta)
✨ New
- Nucleus names in your theme's colours.
GameandContextshow as objects, with their properties, methods and enum values (Nucleus.Folder.InstancedGameFolder) each in their own colour, so a name Nucleus doesn't know stands out in plain text next to its underline. In VS Code and the LSP editors that colour by meaning (semantic highlighting). - Explain this line. Not sure what a line does? Ctrl+Alt+E (or right-click › Explain This Line) says it in plain words: what it sets or calls, the docs of the names in it, and what Check says about it. In Notepad++: Plugins › Nucleus Co-op handlers › Explain this line. Other editors get it as a code action (
nucleus.explainLine). - A page for every check. Each problem links to its own page: what it means, why Nucleus cares, a wrong and a right example, the fix, and how to turn it off. All checks, one page each, so you can link one in Discord too.
- Test in Nucleus Co-op, one click. The ▷ button above a handler (and Plugins › Nucleus Co-op handlers in Notepad++) installs it and starts Nucleus Co-op with its game selected: pick the players and press Play. An open Nucleus is restarted with your OK (it reads handlers when it starts), its debug log can be turned on with one answer, and Open Nucleus Co-op's Debug Log shows what happened. Also
ncdev testfor other editors. - Docs one click from your code. API names in hovers, parameter hints and suggestion docs are links. In VS Code they open Nucleus Docs beside the editor (offline): the name's page, a path back to its group and the main page (Docs / Context / ModifySaveFile), Search…, and Open in the workbench. Other editors (Neovim, Helix, Zed…) link to the same page in the browser workbench. Also Nucleus: Docs and Nucleus: Search the Docs… in the Command Palette.
- A Notepad++ plugin. Problems are underlined as you type, hovering a name shows its docs, suggestions know where you are (the members that exist there, an option's values, the game's own files), and
(shows the parameters. Alt+Enter offers the fixes for the line; Plugins › Nucleus Co-op handlers has Fix all, Format, Try it, a Problems panel and Link the game's folder.ncdev setup notepad++installs it. ncdev, one download, nothing else to install. The command-line tools are nowncdev(Nucleus Co-op dev tools), andncdev.exeon the release page runs on Windows without Node.js.ncdev updategets the newest version, checked against the release's checksums.nucleusstill works.- A getting-started guide in VS Code. Help › Welcome › Make a Nucleus Co-op handler walks from an empty file to the Hub in six steps (start, check, Try it, the game's folder, testing in Nucleus, sharing), each with its button.
- Notepad++: Browse the Hub, Package and Settings. Plugins › Nucleus Co-op handlers can now browse and search the Hub and download a handler with its files, package a handler as
.ncfor upload, and set how strict each check is and the format style in a Settings dialog. - Package, Install and New handler in every editor. Editors that use
ncdev lsp(Neovim, Helix, Zed, Sublime Text…) get Package as .nc and Install to Nucleus Co-op in their source actions, and anucleus.newHandlercommand. In an empty file, typinghandleroffers the whole New Handler template (VS Code and Notepad++ too). - One house style, your call. Format Document now also writes double quotes (what the Hub install reads
Game.GameNamebetween) and ends statements with semicolons, and only if the program provably stays the same. Both can be changed or turned off (splitscreenme.format.quotes,splitscreenme.format.semicolons;--quotes,--semicolonsforncdev format). Format Selection and format-as-you-type work too. - What to pass, for every parameter. Parameter hints and hovers now say what each parameter of the most used Nucleus methods takes (e.g.
ReplaceLinesInTextFile's"N|text"lines, counting from 1), written from the Nucleus source and marked AI-written, and JavaScript's own methods get theirs too. - Snippets for what most handlers do. Type the start of
iniset,replacelines,regkey,startargs,ifoption,firstplayer,eachplayeroroptionat the start of a line and pick it: ready-made code the way Hub handlers write it, to fill in. - Your own functions, understood.
myFunction().suggests what its result has when itsreturns (or an@returns {type}) say what it gives back, and@paramlines in the comment above it show in its parameter hints. - Smarter suggestions after a dot. A string literal, a joined string (
path + "\\x.ini"), what a method gives back (.replace(…).,.split(",")and its items) and numbers now get their own methods, hovers and parameter hints.Context.Options["…"]with a key noGame.AddOptionadds is flagged (a typo in the key), with a fix to the right one; hoveringContext.Optionslists the handler's keys. - Suggestions know your own code.
Context.Options["suggests the keys yourGame.AddOptionlines add,== "their choices, and hovering a key shows the option (all editors). In Notepad++ and other editors, your own functions and variables are suggested and explained too (with the comment above them), with parameter hints, and Rename… changes one everywhere. - New handler, Install and Outline in Notepad++. Plugins › Nucleus Co-op handlers can now create a handler (name, exe, Proto Input, Goldberg…), install it into Nucleus Co-op, and show an outline panel of its options and functions to jump around in.
ncdev installdoes the same from a terminal. - Go to definition. On a function or variable of the handler, F12 (VS Code, other editors) or Alt+F12 (Notepad++) jumps to where it's declared; on
Game.Playor any option to where it's set; onContext.Options["key"]to itsGame.AddOption. Find references lists every use (Language Server, Notepad++). - Open a handler in the browser workbench. Nucleus: Open in the Browser Workbench (VS Code) and Plugins › Nucleus Co-op handlers › Open in the browser workbench (Notepad++) open the handler you're editing there, for its visual editor, Lines and Test all.
- Common JavaScript mistakes caught. The checks now include ESLint's rules for real bugs:
=where==was meant, a backslash that disappears from a Windows path ("C:\Games"), the same key twice, code that never runs, a line that does nothing, and more, each explained in plain words. On the Hub's 896 handlers they found only real bugs. - AI agents sign their handlers. With the agent kit, Claude Code and other AI agents add a few comment lines at the top of a handler they write or change: which agent, what
ncdev lintandncdev simulateshowed, and that it wasn't run in Nucleus. Helpers see at a glance how a handler was made. - Notepad++, 32-bit too.
ncdev setup notepad++installs the plugin for 32-bit Notepad++ as well as 64-bit.
🛠️ Improved
- AI agents get the newer tools. The MCP server adds
nucleus_debug(breakpoints with conditions, watches),nucleus_explain(what a line does) and check explanations (nucleus_ruleswith a rule id); every problem carries its docs link, a path also checks the handler's folder, and the server hands every agent the hard rules. The CLI hasncdev rules <id>andncdev explain, and the skill lists them all. - Where to ask for help. Nucleus: Open Documentation lists the SplitScreen.Me Discord and r/nucleuscoop, and
ncdev --helpends with both. - The feedback form fits what you report. It's for checks and the editor tools, with up-to-date choices under Where, and links fill that in from where they are. Workbench and site feedback has its own form in the workbench's repository.
- The Notepad++ plugin says its version.
NcDev.dllnow carries its version and name (Properties › Details in Windows, and what Notepad++'s Plugins Admin reads), ready for a listing there. - Try it never freezes the editor. It runs in a background thread: a handler stuck in an endless loop is stopped, a new edit cancels the old run, and Test all shows progress and can be cancelled. The same goes for
ncdev lsp,ncdev mcpand the debugger. - Notepad++ stays responsive while ncdev works. Hub search and download, Install, Package, Test, Update and the API reference run in the background with a timer in the status bar, and a tool that hangs is stopped.
- Lighter on hub.splitscreen.me, and it knows who asks. Requests at the same time are shared, at most two downloads run at once, retries back off on errors, and when the Hub is down the last list is used for a while. Every request names these devtools, which tool sent it and why (e.g.
vscode-extension hub-browse), and nothing about you. ncdev lspwatches only handlers and their folders. Changes innode_modulesand.gitno longer wake it up.- Zip packages read more file names correctly. Names stored without the UTF-8 flag are read as UTF-8 when they are valid UTF-8.
- Missing required options, explained and filled in. A missing
Game.GUID,Game.GameNameorGame.ExecutableNamenow says what each one is for, and the fix fills in what the handler already tells it (the GUID from the game's name, or the other way round), so Fix all can add it; only real unknowns get a placeholder to fill in. A missingGame.ExecutableNameis reported once, not twice. - Every use of a name, highlighted. In editors that use
ncdev lsp, the cursor on a variable or function highlights its other uses, as VS Code does. - The Hub's most downloaded.
ncdev hub search --popularlists the Hub's most downloaded handlers. - Set it up in your own editor. The README has a new section for experienced developers: how to point Neovim, Helix, Sublime Text, Emacs, Kate, JetBrains IDEs or Zed at
ncdev lsp, how much setup each takes, and which ones we've tested. - Neater code in hovers and docs. Examples and long signatures are laid out the way prettier would: one parameter, list item or argument per line when they don't fit, a last list hugged by its call, long
+chains broken after=. Short code stays on one line, and what the code does never changes. - JavaScript's own methods in suggestions. After a string (
Context.StartArguments.), a list,Math.orJSON., suggestions, hover and parameter hints cover JavaScript's built-in methods, only the ones Nucleus's engine has (replace,split,indexOf,Math.floor…), with a link to their docs. A misspelledMathmethod is flagged. - Names Nucleus itself gets wrong. Nucleus misspells two Proto Input options (
WindowActvateAppFilter,TranslateXAccelration), and its readme and Handlers Tool give a few names that don't exist (Usex360ce,IgnoreWindowBordercheck…). Writing the correct spelling, or the readme's, now explains why it does nothing and offers the name that works. - A fix for an exe that isn't there. With the game's folder linked, a wrong
Game.ExecutableNamenow offers the one exe it most likely means (e.g. Unreal's…-Shipping.exe), not only for near spellings.
🐛 Fixed
- "Fix all" is back in the Ctrl+. menu. VS Code dropped it from the quick fixes; it now shows next to the single fix whenever more than one problem can be fixed.
- Every problem links to its docs. Package and game-folder problems in VS Code now link to the checks pages, as the others do.
- Search finds the obvious name first. "mutex" lists
Game.KillMutexbeforeGame.KillLastInstanceMutex. - New Handler checks every value. In the CLI, the MCP server and the language server, a max player count that isn't 1 to 16, a Steam id that isn't digits, an exe that isn't a file name, or an unknown feature is refused with a plain reason, instead of ending up in the handler's code.
- Clear answers to wrong input. The MCP tools say what's wrong (a folder instead of a file, a missing name, players out of range) instead of showing a raw error or quietly changing the value, and
ncdevnames a missing file plainly. - Breakpoints past the end are flagged. The debugger marks a breakpoint beyond the last line as not set, and
ncdev debugsays it can't be hit. - Long files lint quickly. Checking a handler with thousands of lines no longer slows down with every problem found.
ncdev setupsuggests the right spelling. A typo such asncdev setup nodepad++now says Did you mean: ncdev setup notepad++.- The extension works in folders VS Code doesn't trust yet (Restricted Mode). Before, it was switched off there, so a downloaded handler showed no checks and no suggestions. Install, Test in Nucleus Co-op and Set up AI agents ask you to trust the folder first, since Nucleus Co-op runs the handler's code.
- Docs links open the name's own page on the site (
docs/Context.ModifySaveFile/): from hovers and suggestions in Notepad++, Neovim and the other LSP editors, and from Open on the web in VS Code's Nucleus Docs panel. Each page has the 👍/👎 and the report link. - Notepad++ in dark mode: the problem and outline lists' column headers and scroll bars are dark too, with Windows' own dark themes (the ones Notepad++ uses).
- A misspelled Context property in
var x = (Context.X = …)is now a warning with the fix (the idiom itself stays a quiet hint).PauseBetweenStartsis documented in seconds, which is what Nucleus waits (the official docs say milliseconds), andHook.CustomDllEnabledsays it's on by default. Context's file, registry and process functions are in their own docs categories instead of "Path variables". - Long handlers no longer freeze the editor. With thousands of assignments, moving the cursor near the end re-read the whole handler once per line above it (finding values to pick from a list); it's read once now.
ncdev lintno longer stops on a wrong value type. A value of the wrong type (Game.MaxPlayers = "4") made the command line crash, and VS Code showed it as an error instead of a warning.- Browse the Hub can't copy over your workspace. A Hub handler whose game name was
.or..could make Copy into Workspace write over the workspace folder (or the one above it). - Try it runs can't affect each other. A handler that changed JavaScript's own functions could change what later Try it runs showed, until VS Code restarted.
- Package and Install follow your rule settings. A rule you turned down or off no longer blocks them.
- Examples in the docs mean what they say. Laying out an example could drop parentheses it needed (
(a + b) * c); such examples now stay as written. - The rule link in each problem works. It pointed at an empty repository.
- No suggestions inside comments and strings. Typing
Game.in a comment or a string no longer opens the API list; option keys and choices insideContext.Options["…"]still come up. - The Hub install name, the same everywhere. Check, Try it (
Game.Folder) and the package checks readGame.GameNameexactly as Nucleus' Hub install does: no indentation, the second of two matching lines wins, a BOM is ignored. - Format keeps unusual line breaks. Files with an old Mac line break (
\r) or U+2028/U+2029 are formatted with each break left where it was. - Files saved with a BOM. Problems, fixes and Add
Game.GUIDland in the right place, and a BOM no longer causes a false Hub install error. - Quick fixes keep Windows line endings. In a CRLF handler, quick fixes and Fix all insert CRLF, so lines no longer end up mixed.
- New Handler checks the game name. A name with a double quote, backslash, line break or control character is refused with the reason (it would break the Hub install). Accented names give a readable GUID ("Pokémon" → "Pokemon").
📦 Install: download splitscreenme-vscode-v0.6.0.vsix below, then in VS Code run Extensions: Install from VSIX… (Ctrl+Shift+P). New to the tools? Start with the intro and install guide and TESTING.md.
🤖 AI agents: nucleus.js (below) is the command-line tool and MCP server: node nucleus.js mcp. See the README.
🌐 Offline workbench: workbench.html (below) is the whole browser workbench in one file; open it locally or host it yourself.
💬 Feedback: tester feedback form.