# How do I see Godot’s output and errors in Flockbay?

Press Play (F5): the game is attached to the Godot editor’s debugger, prints show in Output, and errors with their stack traces under Debugger › Errors. When Flockbay runs the game itself, its step in the chat shows Godot’s Output and the exit code.

Source: https://flockbay.com/docs/how-do-i-see-godots-output-in-flockbay/ · Updated 2026-11-01

## When you play

Output and the Debugger are Godot’s bottom panel, in the Standard and Full views. Editor Settings › Run › Bottom Panel › **Action on Play** sets whether Play brings Output, the Debugger or nothing forward. A script error stops the game at its line, and the running scene tree is under **Remote** in the Scene dock.

## When Flockbay runs it

After a turn, Flockbay runs the game headless or in the Game screen and reads stdout and the debugger, GDScript parse errors included. Open the run’s step in the chat: Godot’s Output, error lines in red, and the exit code. A `res://` path or an error line there opens in your external editor at its line.

![A headless run’s step in the chat: Ran rooftops.tscn headless, Godot’s Output with a SCRIPT ERROR line and at: res://ui/run_timer.gd:31, and exit 1.](https://flockbay.com/docs-captures/play-and-debug-headless-output.webp?v=5a50617284)

## Hand an error to Flockbay

Type @ in the message box and pick **Debugger** or **Output**: the errors, or the end of the last run’s Output, go under your message. A failure card’s **Fix with Flockbay** sends the failure to the chat as it is.

Related: [Play, Stop and the Game screen](/docs/play-and-debug/), [How do I get Godot’s Scene dock and Inspector back?](/docs/how-do-i-get-godots-docks-back/), [Godot 4 errors, verified](/godot/)