> For the complete documentation index, see [llms.txt](https://unknown-56-works.gitbook.io/luigiscreen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unknown-56-works.gitbook.io/luigiscreen/administration/debug.md).

# Debug Statistics

Run:

```
/screen debug
```

Run it again to disable debugging.

## Boss bar pages

The boss bar cycles through:

1. Stream state, source resolution and last-frame age
2. Total/enabled screens, shared sources, primary screen maps, viewers and FPS
3. Received, rendered and replaced frames
4. Last and average render time
5. JVM, non-heap and system memory
6. Estimated LuigiScreen image buffers
7. Process CPU, system CPU and threads
8. TPS, MSPT, uptime and garbage collection
9. Reconnect and error health

## Sidebar

The 15-line sidebar shows the most important values simultaneously:

* Stream state
* Source resolution
* Total screens, enabled screens and shared source count
* Primary screen size
* Output resolution
* Viewer count
* Input and output FPS
* Frame counters
* Queue and replaced frames
* Render timings
* Heap usage
* Estimated buffers
* CPU usage
* TPS and MSPT
* Uptime and threads
* Reconnects and current error

## Scoreboard compatibility

LuigiScreen stores the player's previous scoreboard and restores it when debug mode is disabled.

If another plugin replaces the scoreboard while LuigiScreen debug is active, LuigiScreen does not overwrite that newer scoreboard and does not restore over it.

## Memory limitations

The displayed buffer estimate includes LuigiScreen Java image buffers.

It cannot accurately assign all native FFmpeg or MapEngine memory to this plugin. Use operating-system tools or a profiler for complete process memory.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://unknown-56-works.gitbook.io/luigiscreen/administration/debug.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.