LiveReport

How it works

• Player X is reporting player Y
• Player X is notified that the report has been sent
• The staff team receives the report in chat and details
• A staff member clicks the message, taking the job
• All other staff members are notified that staff member Z took the job.
• Staff members can no longer take that job.
• Player X is notified that a staff member will look into Player Y
• Staff member Z looks into player Y

Commands

• /lr <user> <reason> or /livereport <user> <reason> - Reports a player
• /endjob <outcome> <reason> or /ej <outcome> <reason> - Ends the job you are currently on. Outcome can be none,warn,kick or ban (the plugin will not ban,kick or warn the players automatically. It's just for logs). Reason can be more than 1 word.
• /job - Displays your current current job.
• /jobs - Displays all jobs for all staff members.

Permissions

• livereport.send - Can send reports, execute the /livereport command.
• livereport.receive - Receives "staff" messages about reports. Player is in staff team. Can take jobs etc.
• livereport.immune - Player cannot be reported
• livereport.jobs - Access to the /jobs command. See all current staff jobs

MySQL Logging
Configuration in the config.yml Data folder of the plugin, generated automatically after first runtime.

The table in which logs of reports will be saved can be created by this query:

CREATE TABLE livereport_log (
id int NOT NULL AUTO_INCREMENT,
TD varchar(255),
Staff varchar(255),
Player varchar(255),
ReportedBy varchar(255),
Outcome varchar(255),
Reason varchar(255),
PRIMARY KEY( id )
);

Download
Latest release in the Releases section.