0.64.x✎

Releases

1. 0.64.8The published pages get the palette and a gear of their own.New2026-09-16
2. 0.64.7Settings in Node Design, and no more flash of the wrong scheme.New2026-09-16
3. 0.64.6The landing page follows your scheme too.New2026-09-16
4. 0.64.5Your colour scheme reaches every window, and the documentation site.New2026-09-16
5. 0.64.4A gesture reads as one input, and a migration nobody can have needed is gone.New2026-09-16
6. 0.64.3A drawn panel holds something, and says which part the page is about.New2026-09-16
7. 0.64.2The Functions guide, caught up with the editor.New2026-09-16
8. 0.64.1A drawn panel's headings, and each section explained where it belongs.New2026-09-16
9. 0.64.0Modules, documented — and panels can be drawn now.New2026-09-16

Added

• 0.64.8Ctrl + K opens the search palette on the published site, the way it does in the editor and in Node Design. It used to put the cursor in the sidebar's field instead. That field is still there and still filters the tree.
• 0.64.8Settings on a published page, from the gear at the end of the header: your theme and the face these pages are set in. The icon alone rather than a labelled button — a page gives its width to what you came to read.
• 0.64.7Settings in Node Design, from the gear beside Open Editor. The same panel the docs window opens, without the Project tab — roswaal.json describes a project and stays the editor's to change. It is where node corners and wire style live, which is the window that draws nodes all day.
• 0.64.3Every section of the drawn Variables panel has rows in it — two variables, two modules, two locals and two functions, with the const badge, a module's specifier and a function's hoisted or here all shown. A section drawn empty said the section held nothing.
• 0.64.3The section a page is about keeps the light, and the rest dim — a scrim with a cutout. Modules lights Modules, Functions lights Functions, and Variables and locals lights both of its own.
• 0.64.2How to call one, which the page never said: Get Function for the value, Call Function for a call that does something, Call For Value for a call that asks something — and why a Get Function above a Declare Function is an error where a hoisted Function has no order to get wrong.
• 0.64.2The signature: what the Name, Parameters and Return values fields do, that a type there is free text, and what renaming, reordering and removing a parameter each do to the nodes reading it.
• 0.64.2Returning, with the Return node drawn. Return values configured on the function become named, typed pins on every Return in it.
• 0.64.2Reading a parameter, with Get Parameter drawn, the Get ‹parameter› search entry, and where a parameter is offered.
• 0.64.2Finding one: the Variables panel, the This graph filter in the node menu, and the node picker on Ctrl + right-click.
• 0.64.2Previewing the function you are in with P, rather than the whole script.
• 0.64.2The Variables panel is drawn on the Functions page, with functions explained there and the other sections pointing at their own pages.
• 0.64.1The Variables panel is drawn on its own page too, at Variables and locals, with variables, locals and functions explained in full there.
• 0.64.0A page about requiring, at Modules: how to declare one, what each runtime resolves, why the name is yours to choose, and what @lune/roblox members make possible. Requiring is the one subject where Roblox and Lune genuinely differ, and there was nowhere to look.
• 0.64.0A table of what resolves where — ./ and ../ anywhere, @self/ and @game/ under Roblox, @lune/* under Lune, and .luaurc aliases under Lune with Roblox still to come.
• 0.64.0The Variables panel is drawn, the way the toolbars are: hover a section to light its explanation, and hover an explanation to light the section.

Changed

• 0.64.8Verified: the Functions guide, rewritten in 0.64.2 and read against the editor.
• 0.64.8The drawn bars on Toolbars show the gear Node Design and the published pages gained, and say why it is a gear on those and a button in the documentation window.
• 0.64.8The site's palette takes the sidebar's index and the sidebar's ranking rather than a second copy of either, so the two searches cannot disagree about the best answer.
• 0.64.5The three windows share one listener rather than a copy each. A theme is stored in localStorage, which is exactly so that every window on the origin — including the static site — can be told when it moves.
• 0.64.4Ctrl + right-click on Functions marks the whole gesture, rather than highlighting the key and leaving the click as prose.
• 0.64.3Hovering a dimmed section's explanation lights that section in the picture, scrim and all. A highlight that leaves the thing it points at unreadable is pointing at nothing.
• 0.64.2Which locals a function can see now says which declaration it is talking about: a Declare Function closes over the file's locals, and a hoisted Function is written above them and cannot.
• 0.64.2The Functions section of the drawn panel points at Functions from the pages that are not about functions, the way Modules and Variables already did.
• 0.64.1A section of the drawn panel is explained on the page that is about it, and points there from the others. Modules explains modules and links out for the rest; Variables and locals does the reverse. Same drawing, different words.
• 0.64.0The machinery behind a drawn toolbar now draws a panel too. It was never about bars — a spec, the editor's own class names, a legend from the same spec, and the pointing between them. One more shape rather than a second copy, so the pointing, the layout traps and the fixes that took three attempts are paid for once.
• 0.64.0A drawn row takes its swatch from the palette the canvas uses, so a number in a picture is the number on your screen. Without a palette it falls back to the ring a module gets, rather than inventing a colour.

Fixed

• 0.64.7The app no longer opens in the wrong colours. A module script runs after the page is parsed, so the stylesheet painted first and the scheme you picked arrived a frame later — a flash on every load, worst when your scheme disagrees with your operating system, which is the whole reason for picking one. The scheme is now applied before the first paint. Measured on the built site: ready 38ms before the page painted.
• 0.64.7The Not Found page takes your theme. It kept the colours it was written with, and now uses them only as the fallback for a reader whose stylesheet did not arrive.
• 0.64.6The site's front page takes your theme. It is drawn from the same tokens everything else is, so it was one page away from the fix that reached the documentation — and it is the first page anyone sees.
• 0.64.5The published documentation follows your theme. It shipped the editor's stylesheet and nothing else, so it followed the operating system — a scheme picked in the editor stopped at the Docs button. It now reads the same preference the editor writes, before the page paints, along with your node corners and reading face.
• 0.64.5Node Design follows a theme picked in the editor. It took the scheme it opened in and kept it, because it has no settings panel of its own and nothing was telling it.
• 0.64.5The editor follows a theme picked in the docs window. The docs have their own settings panel, and the editor was the one window not listening.
• 0.64.4The Functions guide no longer explains what happens to a graph made before 0.33.0. Roswaal has been public since 0.59.1, so no reader has one.
• 0.64.1The Modules, Locals and Functions headings in a drawn panel took the article's heading style instead of the editor's, so they came out large and dark where the panel shows small grey caps.