backupRoswaal has moved to roswaal.app. These pages are a backup copy.Go to roswaal.app

0.62.x✎

Search nodes by the runtime they work for.

0.62.x2026-09-16

FeatureChangeBugfixEditorDocs

Search nodes by the runtime they work for.

Releases

  1. 0.62.6A node's page is tagged with the runtime it needs.New2026-09-16
  2. 0.62.5The visual search finds what you named, not just what we shipped.New2026-09-16
  3. 0.62.4Search only what this graph declares.New2026-09-16
  4. 0.62.3The front page says what this version is about.New2026-09-16
  5. 0.62.2The runtime badges line up, and a Lune graph says what it is.New2026-09-16
  6. 0.62.1Switching a tab no longer leaves you on a blank page.New2026-09-16
  7. 0.62.0Search nodes by the runtime they work for.New2026-09-16

Warning

Worth knowing before you upgrade.
  • 0.62.5Both searches take the same list, built once, so they cannot disagree about what is in scope — including which of a function's parameters belong to the body you are looking at.
  • 0.62.4In a function's own graph, This graph includes that function's parameters — and only its own. A parameter exists where its body runs, so the file's graph offers none and a sibling function's are never listed. That was already how the menu worked; the filter inherits it rather than deciding again.
  • 0.62.4The node picker lists the built-in library only, so it has nothing of the graph's to offer and does not show the chip. The preference is shared, and falls back to showing everything there rather than to an empty list.
  • 0.62.2There are no Lune-only nodes yet, which is why a Lune graph offers base Luau and nothing else. They arrive with the Lune standard library — @lune/fs, @lune/net, @lune/process and the rest — which is a later release in this sequence.
  • 0.62.1It only ever happened to a real pointer. Focus is what moved the window, and a scripted click does not focus — which is why it survived three attempts to reproduce it.

Added

  • 0.62.6Every node page carries its runtime as a tag beside the title — the same word and the same colour the node menu puts on a row, so a badge in the editor and a badge in the documentation are one vocabulary rather than two.
  • 0.62.6Base Luau is tagged too, which is where the documentation differs from the menu. A list is scanned, so an absence reads; a page is arrived at one at a time, and a page that says nothing has not answered.
  • 0.62.5Ctrl + right-click now searches the graph's own declarations too — its variables, locals, functions and the parameters of the body you are in, beside the built-in library. The one search that shows you what a node looks like could not find the node you named yourself.
  • 0.62.5They come first in the list. A name you chose is likelier to be the one you are after than a built-in that happens to read similarly.
  • 0.62.5The This graph filter works here as well, so the picker can be narrowed to what this graph declares and nothing else.
  • 0.62.4A This graph filter in the node menu, beside the runtimes: the variables, locals, functions and parameters this graph declares, with the library set aside. The thing you are looking for when you know you named it.
  • 0.62.4Those entries carry a quiet badge in the unfiltered list too, so Get Accumulator is told apart from the Get Variable it sits next to under the same heading.
  • 0.62.0A runtime filter in the node menu and the node picker — All, Luau, Roblox — remembered between openings. It narrows what the graph's target already allows rather than replacing it, so a Lune graph never gains a Roblox node by picking a chip.
  • 0.62.0Luau is the useful one: it answers "which of these still works if I move this graph to the other runtime".
  • 0.62.0A badge on a node that needs something. Base Luau is unmarked — badging four rows in five would be noise, and the absence is the claim: this one runs anywhere.
  • 0.62.0Every node's page says which runtime it is for, base Luau included. Said nowhere, "works in both" and "nobody has decided" look identical, and for 237 nodes they were the same thing until 0.61.0.

Changed

  • 0.62.6The line under the title says what the runtime means rather than naming it again — needs the Roblox engine, its datatypes, its DataModel or its scheduler. The tag is the thing to scan; the line is the thing to read.
  • 0.62.6A guide carries no tag. It is about an idea rather than about something that runs, and tagging Controls with a runtime would answer a question nobody asked of it.
  • 0.62.5The preview draws the entry you are about to place. A graph's own entry is a node plus the configuration that makes it that one, so Get Accumulator is drawn as Get Accumulator rather than as the nameless capsule underneath it — otherwise every variable in a graph previews identically.
  • 0.62.5A search matches on the entry's own name. Typing accumulator finds Get Accumulator, whose definition is called Get Variable and would never have matched.
  • 0.62.4The filter is one control with four answers rather than two controls. Three of them say which runtime a node needs; This graph says it is not a library node at all. They are different kinds of claim, and a reader opening a search box is asking one question — narrow this — not two.
  • 0.62.3The front page's footer names the release rather than the moment. It read the first public release, which was true once and then quietly stopped being — a line about a day cannot go on describing the version beside it. It takes the release's own headline now, so it is right for every version without anybody remembering to change it.
  • 0.62.3The footer's links sit at the other end of the row, so a tagline has room to be a sentence.
  • 0.62.2A graph with only one runtime available says so rather than showing nothing where the filter goes. Every node a Lune graph can compile is base Luau today, so there was nothing to choose between — and an empty space read as the filter being broken instead of as there being one answer.
  • 0.62.0The filter offers only the runtimes actually present. A Lune graph has no Roblox nodes left to narrow to, so the chip is not there — a filter that can only return nothing is worse than no filter — and with one runtime present the row goes entirely.

Fixed

  • 0.62.3The runtime filter had no room under it, so the chips sat directly on the search box and the two read as one control stuck to another.
  • 0.62.2A row carrying both pure and a runtime badge put the pure in a different place on every row. Both were pushed right independently, so they split the space between them rather than travelling together — the column stopped being a column.
  • 0.62.2The badge sat two pixels low. A menu row aligns on the baseline, which is right for a swatch and a title and wrong for a bordered chip: its border hangs below the line its neighbour sits on. Every trailing chip centres now.
  • 0.62.1Clicking a tab on a documentation page could scroll the window to an empty part of the document. The switch hides its radio buttons by positioning them absolutely, and with no positioned ancestor they were measured against the page itself — so on Toolbars two of them sat two thousand pixels below anything that renders and stretched the document to three times its height. Clicking the label focused one, the browser scrolled it into view, and you landed on nothing at all. Nothing threw, so there was nothing in the console either.
  • 0.62.0Bringing a lit toolbar control into view measured from the wrong element on the Toolbars page, so on a page with anything positioned above it the bar scrolled to a meaningless offset.