Nucleus Handler Workbench

Home
Home

Welcome to the workbench

A handler is the file that tells Nucleus Co-op how to run a game split-screen (it goes in Nucleus' handlers folder). Here you write one, check it and try it, then save it for Nucleus.

  1. 1 Start one, or open yours
  2. 2 Fix what Nucleus would reject
  3. 3 Try it per player
  4. 4 Save it for Nucleus

Or drop a .js, .zip or .nc file anywhere on this page.

· edited
Tip

Check

F8 next problem · hover code for docs · . or Ctrl Space completes

      Try it

      Each player's window, launch arguments and file changes, as Nucleus would set them up. Simulated: nothing on your computer is touched, and the game itself still needs a test in Nucleus. How: the handler is loaded and Game.Play runs once per player in this browser, following the Jint 2.11.58 rules Nucleus uses (checked against the real engine on every probe). File, registry and process calls are recorded, not performed.

      Docs

      Your draft is kept in this browser only.About these toolsQuestions? Discord · r/nucleuscoopMade by Snailedlt (Jørgen KH)
      ↑↓ moveEnter open> commandsEsc close

      Settings

      Look and feel Working You More

      No setting matches.

      Light or dark

      Look

      The colours, corners, fonts and motion of the whole workbench. Your own theme files go here too.

      to start your own

      Code colours

      The editor's colours, with any look.

      Motion

      Layout

      Files and Lines

      On a phone both open as a sheet from the bottom.

      Panel sizes

      Drag the edges between panels to resize them. Double-click an edge to reset it.

      Drag the bar at the top of the Lines sheet to make it taller or shorter.

      Check

      Built in everywhere: keyboard access, contrast that meets WCAG 2.1 AA in every look, screen-reader labels, and less motion when your device asks for it (Motion has more). These go further.

      Problems, not by colour alone

      Seeing where you are

      Reading

      Text size: Editor › Text size for the code, and your browser's zoom (Ctrl and +) for everything.

      Timing

      Screen readers

      Start-up questions

      Nucli's two questions from your first visit: how much guidance, and where the tools go.

      Privacy

      Credit linesAdvanced

      Updates

      Back up or move your settings

      A file with your settings (look, layout, editor, keyboard shortcuts, Check, Lines, accessibility, tips), to use in another browser or on another computer. Your handlers, drafts and WakaTime key aren't in it.

      Fix with AI

      Which AI fixes handlers when you press Fix with AI. The handler's code goes to that provider then, and only then. Keys stay in this browser, go only to that provider, and are never in exported settings, links or feedback.

      WakaTimeAdvanced

      Where's my API key?

      Share

      Get the big files from the Hub page, then add them with Files › Add files… to include them.

      To get a file for Nucleus, use Save (Ctrl+S).

      1. Open Nucleus Co-op and drag the file onto the Extract handler button (the box-with-arrow icon next to the game list).
      2. Nucleus asks to replace the old handler if there is one, then offers to add the game. Pick the game's .exe when asked.

      By hand instead: copy the code into Nucleus Co-op\handlers\, then restart Nucleus.

      What's new

      All changes: workbench · VS Code extension

      Files in this package

      🧪 Help test this beta

      Each item says what to try, how long it takes and what to look for. Tick what you've tried (kept in this browser), and report anything you find. Test on a desktop or laptop: that's what most people write handlers on.

      ⇄ This is a big update. to compare: what got better, what got worse, what you miss.

      Your game on this PC

      Only the names and sizes of the files are read, in this browser. Nothing is uploaded.

      Keyboard shortcuts

      The editor uses VS Code's keys. On a Mac, ⌘ instead of Ctrl. Keys with [ ] / \ ; go by position, as in VS Code: on a German, Spanish or Nordic keyboard, press the key where a US keyboard has that one (e.g. Ü for [).

      Workbench
      Ctrl Shift P · F1Command palette: every command (format, fix, try it, theme…)
      Ctrl PExamples and Hub handlers (type > for commands, : for a line); Ctrl K too, outside the code
      Ctrl F5Try it (simulate the handler), as VS Code's Run Without Debugging
      Ctrl ; then ATest all combinations, as VS Code's Run All Tests
      Ctrl SSave (the .zip for Nucleus, or the format you picked last)
      Ctrl Shift SSave as: .zip, .js or .nc
      Ctrl Alt SSave into Nucleus Co-op's handlers folder
      Ctrl BShow or hide the Lines list
      Ctrl ,Settings
      ?This list (outside the editor)
      Esc then TabLeave the code editor (Tab alone indents)
      Problems
      F8 / Shift F8Next / previous problem
      Ctrl .Problems and fixes on this line
      Shift Alt FFormat the code (indentation and spacing)
      Find and navigate
      Ctrl F · Ctrl HFind · find and replace (⌘ ⌥ F on a Mac); Enter / Shift Enter or F3 / Shift F3 through the matches; Alt C / W / R match case, whole word, regex; Ctrl Alt Enter replace all
      Ctrl GGo to line (42 or 42:7 for a column)
      F12 · Shift F12Go to definition · select every use
      F2Rename a variable or function everywhere
      Ctrl Shift \Matching bracket
      Ctrl Shift [ / ]Fold / unfold the block; Ctrl K Ctrl 0 / J all
      Editing
      Ctrl SpaceSuggestions (also after typing .)
      Tab · Shift TabIndent (a selection: its lines) · outdent
      Ctrl / · Shift Alt ALine comment · block comment (Ctrl K Ctrl C / U add / remove)
      Alt ↑ / ↓Move the line up / down
      Shift Alt ↑ / ↓Copy the line up / down
      Ctrl Shift KDelete the line
      Ctrl Enter · Ctrl Shift EnterNew line below · above
      Ctrl ] / [Indent / outdent
      Ctrl LSelect the line
      Ctrl D · Ctrl Shift LSelect the next match too · every match (edit several at once)
      Alt click · Ctrl Alt ↑ / ↓Add a cursor; Shift Alt I one at each selected line's end (Esc for one cursor again)
      Ctrl Z · Ctrl YUndo (including applied fixes) · redo
      Debugger (Try it › Step through)
      F9Breakpoint on this line (or click beside the line number); Shift F9 a condition (Advanced mode)
      F5Start, or continue to the next breakpoint (in the code or Try it)
      F10 · F11 · Shift F11Step over · into · out
      Alt F10 · Alt F5Step back · back to the previous breakpoint
      Ctrl Shift F5 · Shift F5Restart · stop

      Tips under the code: ·

      Links like #hub-<id>, #probe-17 or #example-mistakes open that example directly.

      New handler

      Shown in Nucleus. Also used for Game.GUID (letters, digits and spaces only).
      Drop to open it in the workbenchA handler (.js), or a package (.zip, .nc) with its files