THE SHORT ANSWER
Roblox has launched structured stack traces for server logs in Creator Hub. Each frame now shows script path, function name, and line number as a hyperlink that opens Studio directly to that location in the correct place version. The Server Management Service API also gains a structuredStackTrace field with parsed JSON metadata per frame for building custom debugging tools. Dynamic scripts cloned at runtime remain non-clickable.
- Stack traces in Creator Hub server logs now link directly to script and line in Studio
- Server Management Service API adds structuredStackTrace field with parsed JSON frames
- Each StackFrame includes Line, FunctionName, ScriptPath, ScriptUniqueId, and IsDynamic
- Dynamic scripts (cloned at runtime) show isDynamic=true and are not clickable
- Roblox-generated errors without creator code will lack stack traces
Clickable Stack Traces Land in Creator Hub
Roblox has rolled out structured stack traces for game server error logs. When developers inspect server errors in Creator Hub, each frame now displays the script path, function name, and line number as a hyperlink. Clicking a link opens Roblox Studio directly to the specific place version and the exact script and line where the error originated. The change aims to cut the time spent cross-referencing log output with source files.
API Surface Expands for Custom Tooling
The Server Management Service API adds a new structuredStackTrace field on the GameServerLog resource. It returns an array of StackFrame objects with parsed JSON metadata: Line (integer), FunctionName (string), ScriptPath (string), ScriptUniqueId (string), and IsDynamic (boolean). Teams can now ingest this data into internal dashboards, alerting systems, or automated triage pipelines without scraping the web UI.
Dynamic Scripts Stay Non-Clickable
Frames where IsDynamic is true do not produce a stable Studio reference. This most often happens when a script is cloned at runtime — for example, via Instance.new("Script") or Clone() — but can also appear in other edge cases. Those frames still surface in the structured data, so custom tooling can flag them, but the Creator Hub UI will not render them as links.
Gaps and Known Limitations
Certain Roblox-generated errors — those not tied to creator code — will not include stack trace data at all. The announcement invites developers to report errors they believe should have traces but do not. No timeline was given for backfilling older logs; the feature applies to new server logs going forward.
What This Means for Live-Ops Workflows
For teams running live experiences, the update reduces the friction of moving from an error spike in the dashboard to a fix in Studio. The structured API also opens the door for automated regression checks: a CI step could pull recent structuredStackTrace entries, diff them against known-good baselines, and flag new error patterns before they hit players.