> 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/features.md).

# Features

## Features

### Player inspection

Review detected rules, server-visible client components, loader information and the confidence assigned to each match.

### Rule policies

Every installed CMG rule can use one of three modes:

* **Allow** — keep the observation without enforcement.
* **Monitor** — save the result and alert staff.
* **Block** — apply the configured punishment when the rule threshold is met.

### Progressive punishments

Repeated blocked detections increase the player's strike level. The default ladder starts with a kick and can end in a permanent ban.

### Administration

Important actions are available from the inventory interface and through commands. Console-compatible commands are documented in the [command reference](/clientmodgate/administration/commands.md).

### Rule sources

Administrators can manage bundled rules, import local files, and browse supported projects from Modrinth or CurseForge.


---

# 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/features.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.
