forked from github-mirror/CoreProtect
52 lines
2.7 KiB
Markdown
52 lines
2.7 KiB
Markdown
# Configuration
|
|
|
|
The CoreProtect configuration file can be found within the CoreProtect folder, at `config.yml`.
|
|
|
|
## Per-World Configuration
|
|
|
|
If you'd like to modify the logging settings for a specific world, simply do the following:
|
|
|
|
1. Copy the config.yml file to the name of the world (e.g. world_nether.yml)
|
|
2. In the new file, modify the logging settings as desired.
|
|
3. Either restart your server, or type "/co reload" in-game.
|
|
|
|
Secondary configuration files override the value specified in config.yml. If you leave an option out of a secondary configuration file, then the option specified in config.yml will be used.
|
|
|
|
#### Examples
|
|
* If you'd like to disable all logging for the End, copy the `config.yml` file to `world_the_end.yml` (matching the folder name for the world). Then, simply disable all logging options within the new file.
|
|
* If you just want to disable entity death logging in the Nether, but keep all other logging options the same, simply create a file named `world_nether.yml` containing the text "rollback-entities: false".
|
|
|
|
## Disabling Logging
|
|
|
|
To disable logging for specific users, blocks or commands, simply do the following:
|
|
|
|
1. In the CoreProtect plugin directory, create a file named `blacklist.txt`.
|
|
2. Enter the names of the users, commands, blocks, or entities you'd like to disable logging for (each entry on a new line).
|
|
3. Either restart your server, or type "/co reload" in-game.
|
|
|
|
The blacklist supports disabling logs for:
|
|
|
|
- Users, which includes Players and non-player users, such as "#creeper"
|
|
- Commands, such as `/help`
|
|
- Blocks, such as minecraft:stone. Only `block` actions are affected.
|
|
- Entities, such as minecraft:creeper, which will disable logging the death for that entity. *Note: renamed entities will be logged even if blacklisted.*
|
|
- Filters can also be specified for a particular user, by using the `@` symbol after the specific item, block, or entity namespaced ID. The format is `id@user`. This will filter all `block`, `kill`, `item` and `container` actions involving that particular block, item or mob, only when caused by the specified player or non-player user.
|
|
- Items and container actions are only affected by filtered blacklist entries, not by generic item or block IDs.
|
|
|
|
*Please note that you must include the namespace (e.g. minecraft:) for blocks, entities and items.*
|
|
|
|
An example blacklist.txt file would look like this:
|
|
|
|
```text
|
|
Notch ; User
|
|
#tnt ; TNT explosions
|
|
/help ; Help command
|
|
minecraft:stone ; Stone blocks
|
|
minecraft:creeper ; Creeper entity
|
|
minecraft:shears@#dispenser ; Shears being dispensed
|
|
```
|
|
|
|
|
|
*Please note that to disable logging for blocks, CoreProtect v23+ is required.*
|
|
*To disable logging for entities or to use filtering, CoreProtect v23.4+ is required.*
|