> For the complete documentation index, see [llms.txt](https://clientmodgate.gitbook.io/clientmodgate/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clientmodgate.gitbook.io/clientmodgate/core-concepts/player-inspection.md). # Player inspection ## Player inspection Player reports show the information visible to the Paper server during a check. ### Report contents * Detected CMG rules and their active policies * Confidence level for each matched rule * Visible client and loader components * Best-effort loader classification * Check time and result status * Failure reason when a check cannot complete ### Loader information Fabric, NeoForge, Forge, Quilt and Vanilla labels are context only. A generic loader identity is not treated as proof of cheating. ### Important limitation A player report is not a complete inventory of files on the player's computer. Modified clients can hide or falsify information, and Paper cannot read arbitrary local files. See [detection limits](/clientmodgate/reference/detection-limits.md) for the complete security model. --- # 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://clientmodgate.gitbook.io/clientmodgate/core-concepts/player-inspection.md?ask=&goal= ``` `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.