> For the complete documentation index, see [llms.txt](https://corelab.gitbook.io/corelab-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corelab.gitbook.io/corelab-docs/commands-and-permissions.md).

# Commands & Permissions

## Commands & Permissions

Here is the complete list of commands, permission nodes, and bypasses available in CoreChat.

#### General Commands

| Command                           | Permission           | Description                                            |
| --------------------------------- | -------------------- | ------------------------------------------------------ |
| `/broadcast <msg>`                | `corechat.broadcast` | Broadcasts an announcement to the entire server.       |
| `/clear`                          | `corechat.clearchat` | Clears recent chat history for all online players.     |
| `/msg <player> <msg>`             | `corechat.msg`       | Sends a private message to a player.                   |
| `/reply <msg>`                    | `corechat.msg`       | Quick replies to the last private conversation.        |
| `/ignore <player>`                | `corechat.ignore`    | Blocks private messages and chat from a specific user. |
| `/ignorelist`                     | `corechat.ignore`    | Displays all players currently blocked.                |
| `/channel <local\|global\|staff>` | `corechat.channel`   | Switches default talk channel.                         |
| `/spy`                            | `corechat.spy`       | Toggles staff private message monitor mode.            |
| `/report <player> <reason>`       | `corechat.report`    | Reports rule violators directly to online staff.       |

***

#### Admin Commands

| Command                          | Permission          | Description                                                   |
| -------------------------------- | ------------------- | ------------------------------------------------------------- |
| `/corechat help`                 | Default             | Shows all available plugin commands.                          |
| `/corechat reload`               | `corechat.reload`   | Reloads `config.yml` and refreshes scheduled tasks.           |
| `/corechat mutechat`             | `corechat.mutechat` | Toggles server-wide global chat silence.                      |
| `/corechat mute <player> [time]` | `corechat.muteuser` | Mutes a player temporarily (e.g. `10m`, `1h`) or permanently. |
| `/corechat unmute <player>`      | `corechat.muteuser` | Removes mute restrictions from a player.                      |

***

#### Bypass & Special Permissions

* `corechat.color`: Allows using color codes (`&` or MiniMessage) in chat.
* `corechat.bypass.link`: Bypasses IP and domain advertisement filters.
* `corechat.bypass.caps`: Bypasses automatic uppercase text filtering.
* `corechat.bypass.cooldown`: Sends messages without anti-spam delays.
* `corechat.bypass.mute`: Allows speaking while server-wide chat is muted.
* `corechat.silent`: Hides join, quit, and firework events for the player.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://corelab.gitbook.io/corelab-docs/commands-and-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.