# Features

## Kit System

*The CrownCore handles teleportation for our plugins.*

* You can configure this <mark style="color:blue;">`/plugins/CrownCore/config.yml`</mark>.
* To disable the delay completely you can set <mark style="color:purple;">`instant-teleport`</mark> to <mark style="color:green;">`true`</mark>. Otherwise you can set it to <mark style="color:red;">`false`</mark>.
* You can also disable the delay in certain worlds only. Add the world name to this list <mark style="color:purple;">`instant-teleport-worlds`</mark>.
* When displaying  the teleportation message (only with delay) you can choose between <mark style="color:blue;">`bossbar`</mark> and <mark style="color:blue;">`actionbar`</mark> in <mark style="color:purple;">`teleport-message-type`</mark>.
* The teleport delay is <mark style="color:orange;">automaticly disabled</mark> for players in <mark style="color:orange;">gmc</mark> and <mark style="color:orange;">gmsp</mark>.
* This also plays a cherry particle animation when teleporting.

## Location Handling

*The CrownCore handles location saving for our plugins.*

*Commands for this can be found* [*here*](/wiki/legacy-wiki/plugins/crowncore/commands-and-permissions.md)*.*

## Command and Chat cooldowns

*The CrownCore also comes with an option to set cooldowns to avoid spam.*

* You can configure this in <mark style="color:blue;">`/plugins/CrownCore/config.yml`</mark>.
* The command cooldown is set in <mark style="color:purple;">`command-cooldown`</mark>. This is in milliseconds.
* The message cooldown is set in <mark style="color:purple;">`message-cooldown`</mark>. This is in milliseconds.

## Join delay after restart

*When the server first starts up, CrownCore will not allow players to join for 5 seconds. This can not be disabled.*

## Global values

Each plugin can have its own values to use in its <mark style="color:blue;">`messages.yml`</mark>. To do this you simply add the key you want to the <mark style="color:blue;">`messages.yml`</mark> file <mark style="color:red;">(not in the messages path)</mark> and then you can call it by using the internal placeholder %\<pluginname>\_\<key>%. Here is an [example](/wiki/legacy-wiki/plugins/crownkits/messages.md).

* You can configure this in <mark style="color:blue;">`/plugins/CrownKits/messages.yml`</mark>.

| Key         | Internal placeholder | PAPI placeholder |
| ----------- | -------------------- | ---------------- |
| prefix      | %prefix%             | %cc\_prefix%     |
| whitecolor  | %accent%             | %cc\_accent%     |
| accentColor | %white%              | %cc\_white%      |

## Message color and hex translation.

All messages in the <mark style="color:blue;">`messages.yml`</mark> are able to undestand <mark style="color:green;">`legacy color codes`</mark> aswell as <mark style="color:green;">`hex color codes`</mark> in the following formats <mark style="color:purple;">`legacy & and §`</mark>, <mark style="color:purple;">`#ffffff`</mark> and <mark style="color:purple;">`&#ffffff`</mark>.


---

# Agent Instructions: 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:

```
GET https://obey.gitbook.io/wiki/legacy-wiki/plugins/crownkits/features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.