> For the complete documentation index, see [llms.txt](https://wiki.darrionatplugins.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.darrionatplugins.com/plugins/command-cooldown/mysql.md).

# MySQL

Command Cooldown stores data locally by default. In particular, all cooldown data of players is stored in the plugin's `playerdata` folder. 

**What is stored in the database?** Two important things are stored in the database: The command a player has a cooldown for **AND** when that cooldown will end.

**Why is this helpful?** If you, the administrator, want cooldowns to apply across multiple servers linked through BungeeCord, you must use the database connection. 

Example: Assume Player1 has a cooldown on `/tpa` on Server1 that ends in 30 minutes. By default, if Player1 uses /tpa on Server2, then the player will have no cooldown, **BUT** if the plugin is using the database connection, then the player will not be able to run `/tpa` *only if Server2 also has a cooldown on* `/tpa`*.* 

The database connection can be enabled in the plugin's `config.yml` file. A full plugin restart is required once enabled.


---

# 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://wiki.darrionatplugins.com/plugins/command-cooldown/mysql.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.