Output: find messages and interpret errors
Panel filters do not change application behavior or replace error handling.
If output is missing
- Open Output in the editor bottom panel.
- Clear the text filter and enable the relevant message categories.
- Check the running level and successful C# build.
- Print one recognizable marker in _Ready before adding per-frame tracing.
Hiding categories, clearing the panel and combining repeated lines affect display. They do not fix the error or stop the code. Repeated markers usually require finding repeated calls rather than raising a message limit.
Read the message
Start with the first error from the current run: its text, path, line and stack when available. Later null/cast failures may be consequences. Treat dotnet build errors as compilation errors; clearing Output cannot fix them.
Use LogProbe from the logging guide. Its expected-warning and expected-error are intentional; continued confirms execution proceeds. The ordinary attached SCRIPT_TOOLS example should print ok=True.
C# breakpoints require a configured managed debugger. A clickable Output line does not prove C# breakpoint support in the built-in editor.