0.2.4

NodeGX 0.2.4 — alpha

The release where the things we shipped actually arrive. Three defects in 0.2.3 shared a shape: the fix existed, the feature was built, and the part that carried it to your machine was missing. Every documentation link in the editor pointed at a site that no longer exists. Half the MCP server was built and never packaged. A background picture on a sub-path deploy looked for itself at the wrong address.

None of these were visible from inside the repo, and that is the point — each was found by asking the installed app rather than reading the source.

Fixed

• Every documentation link in the editor works again. opennoodl-docs was renamed on 2026-08-07, and GitHub Pages does not follow a repo-rename redirect the way git does — so the old address is a hard 404, not something a fetch survives. One of the two origins was repointed at the time; the other was not, and shipped dead in 0.2.3. That was 176 node pages, the property panel's "read more", the node picker, and the MCP settings help link — all of them, for the whole release. There is now a check that resolves real pages through the editor's own address functions on every PR, so a moved origin fails a build instead of a click.

• The MCP server is complete for the first time. Its build produces four files; packaging shipped two. So kit-extract.cjs and cloud-bundle.cjs existed in every developer checkout and in no installed copy of NodeGX — which meant an assistant working on your project could not read the node types of any module you had installed, and answered as though your project simply had none. Every project the editor creates has modules in it, so this affected every project on every install. Cloud-function bundling was missing the same way.

• The MCP server now tells you which version it is. It reported 0.1.0 from every release ever cut, because that number was never bumped and the packaged copy carries no other marker. "My MCP server seems to be on an old version" was, until now, a thing nobody could confirm or refute. It reports the release it shipped inside.

• A background picture loads on a site served from a sub-path. If you deployed with --base-url /something/, a project-relative picture in a Background Image port resolved to the domain root and 404'd — while the Image node beside it, which applies the base itself, loaded correctly.

New

• Two templates. Pixel Dungeon — a grid game with keyboard movement, room-to-room progress and a HUD. Story Engine — a branching story whose entire product is one JSON array you can edit and remix.

About the parts library

Nothing here is needed to get it. The editor fetches the shelf from the content CDN while it runs, so all 46 prefabs and 32 modules have been browsable and installable since 2026-09-11 — including from 0.2.3. If you read in the 0.2.3 notes that some newly-added parts could not be installed, that is no longer true and has not been for some time; you do not need this update to use them.

Before you file a bug

• Code export is still alpha. The report names every node it left out and why. Explore the output; don't ship a production app straight out of it yet.
• Windows installers are unsigned and SmartScreen will warn. macOS is signed and notarised.
• Linux is install-only — download the next AppImage to update.
• If you use NodeGX's MCP server with an assistant, restart that assistant's session after updating. The server is started once per session, so a running session keeps the copy it launched with — which is the one thing that will still look "stuck on an old version" after this release.