Repository navigation
v0.4.0-beta.1 (closed beta)
Pre-releaseThe biggest update yet. Checks that catch settings which quietly do nothing, docs for 150 more API members (and a way to help check them), the same tools in any editor with LSP support, and a first look at stepping through a handler line by line. The workbench got its biggest update too: see its What's new.
✨ New
- Settings that silently do nothing. Four new checks, each from Nucleus' and Proto Input's source: Proto Input options with no way to start it (
protoinput-inactive);BlockedMessagesand the message filters withoutGame.ProtoInput.MessageFilterHook(protoinput-needs-hook); a blocked number Proto Input can't block as written (blocked-message); and options only read when another is on, likeFakeFocusIntervalwithoutFakeFocus(needs-option). On the Hub they find 15 handlers with settings that never take effect. Each comes with a fix. - Docs for 150 more API members, and you can check them. Hovers, suggestions and the reference now explain the Proto Input functions and hook IDs, the
Playermembers and the most used undocumented options, written from the Nucleus and Proto Input source. Each one is marked as AI-written and says what it's based on, since the official docs don't cover them. Hovers have Is it wrong? Tell us, which opens a short GitHub form with the doc attached; once a person confirms one, it says who checked it. - Other editors: a Language Server.
nucleus lspbrings the checks with their quick fixes, hover docs, suggestions, signature help, Format Document, window-message names and Try it to Neovim, Helix, Zed, Sublime Text, Emacs, JetBrains IDEs, Kate and any other editor with LSP support. PORTING.md has the setup for each one. - Step through a handler:
nucleus debug. Stop at a line (also only for one player:--break "14 if Context.PlayerID == 1") or where an error ends the run, and see where it is (top of the file,Game.Playfor player 2 of 4,Game.OnStop), the variables, the call stack,--watchvalues and what the handler did so far. The engine behind the coming debugger in VS Code and the workbench. - Window messages by name. In
Game.ProtoInput.BlockedMessages = [0x0008, 0x02a3, 0x02a1], each number shows its name after it (WM_KILLFOCUS,WM_MOUSELEAVE,WM_MOUSEHOVER), hovering says what it does and how many Hub handlers block it, and typing inside the brackets suggests the common ones. The names come from Proto Input's own list. Suggested by messenils.
🛠️ Improved
- A typo no longer hides every other problem. While a line doesn't parse yet (say you're halfway through
player.), the rest of the handler is still checked, and the error sits on the unfinished code with a plain message ("a name is missing afterplayer.") instead of on the next line. - Focus loop settings that do nothing.
Game.ProtoInput.FocusLoop_…andFocusLoopIntervalMillisecondsonly work withGame.ProtoInput.EnableFocusMessageLoop = true; theneeds-optioncheck now says so (14 Hub handlers). - More suggestions after
=.Game.Play =(and the other callbacks) insertsfunction () { }with the cursor inside, andGame.ProtoInput.BlockedMessages =offers the set most Hub handlers block. - Set twice: keep either value. The quick fixes for
duplicate-assignmentnow offer both: remove the overwritten line, or keep it and remove the later one. Hub.*lines explained. Hover andnucleus apinow say whatHub.Handler.Id,Hub.Handler.VersionandHub.Maintainer.*are for (the Hub writes them on upload; Nucleus uses the ID and version to link the handler to its Hub page). They still aren't suggested, since authors don't write them.
🐛 Fixed
- Format Document no longer splits
=>. In code that isn't ES5 yet, formatting turned() => 1into() = > 1(also**and??); these now stay in one piece.
🙏 Thanks
- messenils for the idea of naming the window messages.
📦 Install: download splitscreenme-vscode-v0.4.0-beta.1.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.