Read Studio output
consoleRead Roblox Studio output logs to see prints, warnings, and errors after playtesting, with filtering by severity and pattern.
Instructions
Reads the Studio Output window — prints, warnings and runtime errors, newest last.
This is how to find out what actually happened after a playtest or an execute_luau call. An error here usually names the script and line, which script_read can then open directly.
Filter with level to see only errors, or pattern to follow one subsystem's logging. Up to 2000 lines are held, so prefer a filter over a large limit.
Each connected session keeps its own log, recorded from the moment its plugin loaded — the editor session and a running playtest server do not share one. To read what a playtest printed, target the playtest's studioId (see list_studios); the editor's log will not have it. Nothing printed before the plugin loaded is recoverable, and output from the playtest client is not reachable at all, because Studio forbids client sessions from making HTTP requests.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | Only this severity. Omit for everything. | |
| limit | No | Maximum items to return (1-500). | |
| pattern | No | Lua pattern the message must match, e.g. "Combat" or "^%[Server%]". Lua patterns escape with %, not backslash. | |
| studioId | No | Target Studio; omit for the active one. |