CoreReport

I made this plugin for my own server but a lot of people told me that I should upload it to bukkit.
As the name says,this is a report plugin, it's easy to use but it's efficient.
This is my first Bukkit plugin so I would like to hear some tips down below.

Features

* Operators will get an Ingame message when someone uses the report command.
* You can now add SQL, for multiple servers!
* When a report has been reviewed, it's status changes to "Reviewed".
* Easy to use for admins.
* Reports will be saved in a file.
* Reports can be reviewed and get stored in a "reviewed" file.
* Operators can see the report details with a command.
* Every report has his own report-ID.
* You can change the cooldown between reports in the config file!
* A join-message for all operators with all the OPEN reports. This can be toggled in the config!

Commands

/report [Playername] [Reason] (Report a player.)
/corereport list (Shows a list of all OPEN reports.)
/corereport admin view [report-ID] (See the details from a specific report-ID.)
/corereport admin review [report-ID] (Moves it into the "reviewed" file and removes it from the open reports.)
/corereport admin delete [report-ID] (Delete a specific report from the open reports.)

Permissions

cr.admin /*Gives a player permission for every CoreReport command.*/
cr.report /*Gives a player permission to report players.*/
cr.nocooldown /*Removes the cooldown for a player between reports*/
cr.reportdetails /*Sends the player a message with the reportdetails when someone reports a player*/

Config

This is how the config looks like.

Reportcooldown: 1 /*Amount of MINUTES between reports*/
Join-message: true /*Set this to false to disable it, any other things will set it back to true*/
SQL: true
SQL-host: host /*Host*/
SQL-name: /*Database name*/
SQL-username: /*Database username*/
SQL-password: /*Database password*/

Screenshots

This is how it will look like when an OPERATOR types in /report (Playername) (Reason)
As you can see the Operator gets a special message, all the online operators will get the same message.

This is how it will look like when a NON-OPERATOR types in /report (Playername) (Reason), as you can see, there is no extra message.
And it shows the cooldown between the reports, this can be changed in the config file.

This is how it will look like when an OPERATOR types in /corereport list. It shows all the open report IDs.
If an Operator joins, he will see the same message. This can be toggled in the config file.

This is how it will look like when an OPERATOR types in /corereport admin view [report-ID].

This is how it will look like when an OPERATOR types in /corereport admin review [report-ID].
The report will be moved from the openreports.yml to reviewedreports.yml

MIND THAT IF SQL IS TURNED ON, THESE TWO CONFIGFILES WILL BE TURNED OFF!

This is how the reviewedreports.yml will look like.

The openreports.yml will look the same as the reviewedreports.yml.