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.

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.

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.

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.

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.

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.

FeatureVS CodeNotepad++WorkbenchOther 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 installthe extensionncdev setup notepad++nothingncdev