from event 3 and onward, we plan to share the coreprotect database for each world along with world downloads

# look at this if you don't know what to do

## coreprotect info

coreprotect is a block logging plugin for minecraft servers, really good for being able to rollback griefs and other things.
It can also be used as a rough history of places, but do be careful if you try to use it as such, can be easy to mess things up, ensure you know what you are doing.

## setup

### TLDR: replace coreprotect db with the one from the world downloads

after you install the coreprotect plugin on your server, make sure you run the server at least once so that the Coreprotect folder in the plugins folder is made,
in that Coreprotect folder, there should be a file named database.db, this is the file you will want to replace, go https://civlabs.org/downloads , then to the event you wish to use, then go to the coreprotect folder in that event folder,
from there, grab the db for the world you want, this may or may not have the .gz or .zip file extension on it, after downloading you will need to extract it so it's just .db at the end of the file, depending on how your hosting,
your server, you may be able to do this on the server itself, but it will likely be easier to just unzip/unarchive it on your device and upload the database itself
after all that, ensure the server is off, then delete the old database.db and rename the uploaded one to database.db
after starting the server, coreprotect should use the new database and you should be good to use coreprotect to do whatever you want, though it is highly highly recommended to also use the world download for the world that the database
you grabbed corresponds to. while it could be assumed that most that know how to setup a server with plugins can figure this out on their own, i think this should help most that might not know fully how to do it, or at least help them figure out what to do
be warned that due to the size, that during rollback and restore operations, the database and the queue/consumer can freeze, sometimes for a really long while, it eventually fixes itself, but be warned, since while the queue is stuck, you can't do other operations, like inspect or other rollbacks or restores

## more complicated

now, for the more complicated stuff, coreprotect by default uses the file based database, this is called a SQLite database, very nice since it can just be a file, but limited in it's performance
for civlabs we use a real database, MariaDB , most do not need to do this, but it pretty much gets rid of the db freezes of the SQLite version, these instructions expect some basic understanding of databases, but hopefully not too much

for any world's db that you want to setup, there are 2 things to do

1. setup the database schema, telling the database how we want to be organized, you should be able to just run setup.sql that is in this directory and it should handle the rest, it contains SQL commands to setup the tables and indexs that coreprotect expects

2. in the same place that you would download the SQLite databases, there should be .sql version, this contains all the SQL commands to insert/recreate all the data of the database

from there, set the database credentials in coreprotect's config and it should be good, if stuff doesn't work, i'm not sure how much we can help, LLMs could help, but it is reccomended to try to understand and learn whatever it suggests rather than just doing it.