Nucleus Co-op handler tools · Beta

Catch it before Nucleus does.

Checks, docs and a per-player preview for your handlers.

  • Mistakes underlined as you type
  • Every option explained, right where you use it
  • Each player's setup, before you press Play

New to handlers? Make your first one, step by step →

Vibe-coded, and early: written mostly by an AI with a person steering, tested against Nucleus' real script engine. Expect rough edges, and tell us what you find.

What it catches

The docs, one page per option and call, and every check, one page each: what it means, why, an example and the fix. Every check is tested against the real Jint engine (121 probes), and every week against the verified Hub handlers: no errors on any of them, and Try it agrees with the real engine.

See it

In the editor you already use

Problems underlined as you type, each with why it matters and often a one-click fix. Every option's docs on hover. Suggestions that know what Nucleus has, Try it for each player, and Test in Nucleus Co-op, which installs the handler and starts Nucleus for you.

VS Code, about a minute: problems, quick fixes, suggestions, parameter hints, the Docs panel and Try it. Download
Notepad++, under a minute: the same checks, fixes, suggestions and docs, and the plugin's menu. Download

Or skip installing: the workbench

Everything above in a browser tab, nothing to install, and nothing leaves your browser. Open your handler, an example or any Hub handler. And for when code isn't your thing yet, a visual editor beside the code: options as a form, Game.Play as steps, and every name a handler can use in a list, each with its docs.

The workbench, two minutes: checks, fixes, suggestions, Docs, Try it, the visual editor, the debugger, and Settings (light or dark, looks, code colours, the side rail). Download

Also in the workbench

  • 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).

Want to help build it?

Most of the useful help needs no code. Handler authors know Nucleus better than any linter: better option docs, new checks for mistakes you keep seeing, and Jint probes (small scripts that pin down how Nucleus' engine behaves) are all welcome.