Get the tools
One engine, wherever you write handlers
The same checks, docs, suggestions and Try it in each of them, so pick where you already work. You can use more than one: a handler checked in one is checked the same in the others.
WorkbenchIn your browser. Nothing to install; also the visual editor and the debugger.VS CodeRecommended. An extension, also for VSCodium, with the most to show.
Notepad++A plugin, installed with one command.
Other editorsNeovim, Helix, Sublime Text, Emacs, Kate, JetBrains, Zed: through a language server.
- Command line
ncdev: check, fix, format and test handlers, one at a time or a whole folder. - AI agentsClaude Code, Copilot, Cursor and others write handlers that load, checked by the same engine.
The workbench, in your browser
Open it and start: nothing to install, nothing leaves your browser. It has everything the editors have, plus a visual editor (Form, Blocks and Lines) beside the code, and a debugger that steps through each player.
- Test all combinations: every player count, input setup and monitor size in one click, with what fails and why.
- Whole packages: open a .zip or .nc and save it again with its Goldberg files, configs and DLLs.
- A visual editor beside the code (Form and Blocks), and a debugger that steps through each player.
- Phones and desktops: symbol keys above the on-screen keyboard; VS Code's shortcuts, hovers and suggestions on a keyboard.
- WakaTime, if you use it: your handler time in your dashboard (off by default; the code is never sent).
In your editor
Pick yours to see how to set it up. We recommend VS Code: it shows the most (hovers with docs, a Docs panel, Try it, a debugger). Notepad++ has every feature too, in a plainer way. The others get them through a language server (LSP): ncdev lsp, from ncdev.exe on your PATH.
VS CodeExtension · also VSCodiumRecommended
Notepad++Plugin, one commandFull support
Neovim5 lines of LuaTested
Helix6 lines of TOMLUntested
Sublime TextLSP package + one entryUntested
EmacsOne eglot lineUntested
KateOne LSP Client entryUntested
JetBrains IDEsLSP4IJ pluginUntested
ZedNeeds a small extensionUntested
Anything with LSP
ncdev lspover stdioUntested
Using an editor marked Untested, or one that's missing? Vote in the editor poll on Discord (join the server first if you're new). It decides which editors get tested next.
VS Code
- Download splitscreenme-vscode-v0.8.0.vsix (v0.8.0).
- In VS Code: Ctrl+Shift+P › Extensions: Install from VSIX… › the file.
- Open a handler: problems are underlined, hover for docs, Ctrl+. for fixes, ▷ for Try it.
Notepad++
- Download
ncdev.exeand close Notepad++. - In PowerShell as administrator, in its folder:
.\ncdev setup notepad++ - Open a handler: everything is under Plugins › Nucleus Co-op handlers.
A portable Notepad++ (no administrator needed): .\ncdev setup notepad++ --path "C:\path\to\Notepad++"
Neovim 0.11+
- Add to your
init.lua:vim.lsp.config('nucleus', { cmd = { 'ncdev', 'lsp' }, filetypes = { 'javascript' }, root_markers = { 'handlers', '.git' }, }) vim.lsp.enable('nucleus') - Open a handler: problems show within a second. Older Neovim: the setup for it.
Helix
- Add to
languages.toml:[language-server.nucleus] command = "ncdev" args = ["lsp"] [[language]] name = "javascript" language-servers = ["typescript-language-server", "nucleus"] - Open a handler (
:lsp-restartif Helix was already open).
Sublime Text
- Install the LSP package (Package Control).
- Preferences › Package Settings › LSP › Settings, add:
{ "clients": { "nucleus": { "enabled": true, "command": ["ncdev", "lsp"], "selector": "source.js" } } } - Open a handler.
Emacs 29+ (eglot)
- Add to your init file:
(with-eval-after-load 'eglot (add-to-list 'eglot-server-programs '((js-mode js-ts-mode) . ("ncdev" "lsp")))) - Open a handler and run M-x eglot.
Kate
- Settings › Configure Kate › LSP Client › User Server Settings, add:
{ "servers": { "nucleus": { "command": ["ncdev", "lsp"], "highlightingModeRegex": "^JavaScript$" } } } - Open a handler. (Kate runs one server per language: this one takes over
.jsfiles.)
JetBrains IDEs
- Install the LSP4IJ plugin.
- Settings › Languages & Frameworks › Language Servers › +: name
Nucleus, commandncdev lsp, and under Mappings the file pattern*.js. - Open a handler.
Zed
- Zed only starts language servers that an extension provides, so it needs a small Zed extension first; how, in PORTING.md.
Any other editor
- Point its LSP client at
ncdev lsp(stdio) for JavaScript files. It only answers for handler files, so your usual JavaScript server keeps working. - Settings, Fix all, Try it and the debugger (
ncdev dap) for each editor: PORTING.md.
Something wrong, or an editor that doesn't work? Tell us. Every editor in detail: PORTING.md.
The command line: ncdev
ncdev (Nucleus Co-op dev tools) is the same engine on the command line: check a handler or a whole handlers folder, fix and format it, Try it, look up an option, search the Hub, and package or install a handler. It also runs the servers for other editors and AI agents.
Windows, nothing else to install: download ncdev.exe and run it from a terminal in its folder (in PowerShell, as .\ncdev). ncdev update keeps it current. With Node.js 18+: nucleus.js from a release does the same (node nucleus.js lint MyGame.js).
ncdev lint MyGame.js # every problem, with line and why
ncdev lint handlers --fix # apply the safe fixes in a whole folder
ncdev format MyGame.js --write # indentation and spacing, never what it does
ncdev simulate MyGame.js # Try it: what each player gets
ncdev api Game.KillMutex # an option's type, default and docs
ncdev hub search "borderlands" # how other handlers did it
ncdev --help lists everything; more in the README. It isn't code-signed yet, so Windows SmartScreen may ask once (More info › Run anyway).
AI agents
Agents guess option names from memory, and Nucleus quietly ignores the wrong ones. The agent kit gives them the real API and the same checks, so what they write loads and works.
- Claude Code:
/plugin marketplace add Snailedlt/splitscreenme-vscode, then/plugin install nucleus-coop@splitscreenme. Its skill loads when you ask about handlers. - VS Code (Copilot agent mode): nothing to set up. The extension brings the tools; turn them on under MCP Servers in the Extensions view.
- Claude Desktop, Cursor and other MCP clients:
ncdev mcpserves the tools (check, fix, Try it, API lookup, Hub search). The setup. - Any agent in your handler folder: the agent kit (the skill, the API reference and a one-file command-line tool).
Compare the tools
One engine runs underneath all of them: the checks, suggestions and docs are the same. What differs is what each editor can show.
| Feature | VS Code | Notepad++ | Workbench | Other editors (LSP) |
|---|---|---|---|---|
| Problems as you type, with the why | ✅ | ✅ | ✅ | ✅ |
| Quick fixes and Fix all | ✅ | ✅Alt+Enter | ✅ | ✅ |
| Suggestions, snippets, New handler | ✅ | ✅ | ✅ | ✅ |
| Hover docs and parameter hints | ✅ | ✅ | ✅ | ✅ |
| Docs for every option and function | ✅panel | ✅API reference | ✅Docs tab | ✅links here |
| Format (never moves a line) | ✅ | ✅ | ✅ | ✅ |
| Go to definition, references, rename | ✅ | ✅ | ✅ | ✅ |
| Outline | ✅ | ✅panel | — | ✅ |
| Try it (each player's setup) | ✅ | ✅ | ✅ | ✅command |
| Debugger, per player | ✅ | — | ✅ | ✅ncdev dap |
| Visual editor (Form, Blocks, Lines) | — | — | ✅ | — |
| Checks against the game's folder | ✅ | ✅ | ✅ | ✅ |
| Browse and open Hub handlers | ✅ | ✅ | ✅ | ncdev hub |
| Package as .nc for the Hub | ✅ | ✅ | ✅ | ✅command |
| Install into Nucleus Co-op | ✅ | ✅ | ✅Chrome, Edge | ✅command |
| Test in Nucleus Co-op (starts it) | ✅ | ✅ | —a browser can't | ✅command |
| What to install | the extension | ncdev setup notepad++ | nothing | ncdev |