Purge old block data. Useful for freeing up space on your HDD if you don't need the older data.
| Command | Parameters |
| --- | --- |
| /co purge | `t:<time> r:<world>` |
For example, `/co purge t:30d` will delete all data older than one month, and only keep the last 30 days of data.
> If used in-game, only data older than 30 days can be purged.
> If used from the console, only data older than 24 hours can be purged.
**Purging Worlds**
You can also optionally specify a world in CoreProtect v19+.
For example, `/co purge t:30d r:#world_nether` will delete all data older than one month in the Nether, without deleting data in any other worlds.
**MySQL Optimization**
In CoreProtect v2.15+, adding "#optimize" to the end of the command (e.g. `/co purge t:30d #optimize`) will also optimize your tables and reclaim disk space.
This option is only available when using MySQL, as SQLite purges do this by default.
*Please note adding the #optimize option will significantly slow down your purge, and is generally unnecessary.*
___
### /co reload
Reloads the configuration file.
___
### /co status
Displays the plugin status and version information.
___
## Parameter Details
### `u:<user>`
*You can specify a single user or multiple users.*
* Example: `u:Notch`
* Example: `u:Notch,Intelli`
---
### `t:<time>`
*You can specify weeks, days, hours, minutes, and seconds.*
*Time amounts can be combined, and decimals may be used.*
*Can be used to exclude a block/item/entity/user.*
* Example: `e:tnt`*(exclude TNT)*
---
### `#<hashtag>`
Add a hashtag to the end of your command to perform additional actions.
* Example: `#preview`*(perform a rollback preview)*
#### Hashtags
| Hashtag | Effect |
| --- | --- |
| `#preview` | Preview a rollback/restore |
| `#count` | Return the number of rows found in a lookup query |
| `#verbose` | Display additional information during a rollback/restore |
| `#silent` | Display minimal information during a rollback/restore |
___
## Example Commands
### Example Rollback Commands
By default, if no radius is specified, a radius of 10 will be applied, restricting the rollback to within 10 blocks of you. Use `r:#global` to do a global rollback.
*`/co rollback Notch t:1h`
*(rollback Notch 1 hour (with default radius of 10))*
*`/co rollback u:Notch,Intelli t:1h #preview`
*(PREVIEW rolling back both Notch & Intelli 1 hour (with default radius of 10))*
*`/co rollback u:Notch t:23h17m`
*(rollback Notch 23 hours and 17 minutes (with default radius of 10))*
*`/co rollback u:Notch t:1h i:stone`
*(rollback ONLY stone placed/broken by Notch within the last hour (with default radius of 10))*
*`/co rollback u:Notch t:1h i:stone a:-block`
*(rollback ONLY stone BROKEN by Notch within the last hour (with default radius of 10))*
*(rollback everything done in the last 15 minutes by anyone within 30 blocks of you)*
*`/co rollback t:15m r:#worldedit`
*(rollback everything done in the last 15 minutes in a WorldEdit selection)*
---
### Example Lookup Commands
Lookup commands are generally the same as rollback commands. The primary difference is that a default radius is not applied to lookups, meaning all lookup commands do a global search by default.
*`/co lookup i:diamond_ore t:1h a:-block`
*(lookup all diamond ore mined in the last hour)*
*`/co lookup u:Notch t:30m a:chat`
*(lookup chat messages sent by Notch in the last 30 minutes)*
