Do your server admins struggle to keep track of bug, player, and suggestion reports? Then look no further. Discover a whole new level of player interaction with Reports! Make reporting on your Minecraft server a breeze for players. This plugin introduces a user-friendly in-game menu, ensuring a smooth experience in managing reports. Elevate your server's safety, integrity, and enjoyment now.

Down below you can find some core features of Reports:

• Create reports → Easily create bug, player, and suggestion reports through an intuitive prompt of questions.
• Manage reports → Through the user-friendly interface, manage and read all sorts of information on different reports. Resolve or delete reports, teleport to the reporter, or read the chat history of a reported player. This can all be done through the menu.
• Chat history tracking → The plugin offers the ability to automatically track chat messages. This works cross-server for all servers using the Reports plugin. Chat history can be read for up to 50 messages back!
• Cross-server support included → Reports works cross-server out-of-the-box without the need for any sort of database. All of this is done for you by the plugin.
• Discord integration → Reports will send real-time notifications in your Discord server through a webhook when any report is made. This way the moderation team can easily get straight into action as soon as a report is made.

The plugin is in an early development stage. Please report any bugs on Discord. These will then be fixed as soon as possible.

Discord for support and bug reports: Click here

Note: This plugin utilizes the official Reports API (cloud application) that is hosted and developed by the developer of the plugin. Running the server of this API brings monthly costs to it. If you wish to contribute to the upkeep of the plugin, we would appreciate a donation by using this link.

Donations:
€6,57 - Forgotten Empires


Reports utilizes a central server that manages storing and retrieving reports made by a server. This central server is referred to as the "Reports API". This is a REST API that runs in the cloud. The API is connected to a database that stores all of the reports.

To support cross-server, Reports utilizes containers. These containers define the Minecraft server instances running the Reports plugin and link them together. Containers are necessary to avoid conflict between your servers' reports and the reports of other servers.

Down below you can find yourself a graphic representation of Report's server flow.

Before using Reports, the server has to know to what container it belongs to. Without a container, the plugin will not be able to store/retrieve information.

Creating a new container
If you are new to the plugin, you will have to create a new container. A container only has to be created once for all of your servers, so make sure to only create one. This can very easily be done by using the /reports register <identification> <key phrase> command. The identification is an alias for your container. This can be whatever you would like. The key phrase is used later to link the server to this container.


Linking to a container
Since v1.2 you no longer have to manually link the container to your server after creating it. This is done automatically. You do however have to link your other servers to the container.

After successfully creating a container, you can now link your server(s) to this container. Simply use the /reports link <identification> <key phrase> command. Use the identification and the key phrase you used when you created your container, and it will be linked.


Changing the key phrase of a container
If you wish to change the key phrase of an existing container, you can do so by using the /reports changekeyphrase <identification> <current key phrase> <new key phrase> command. After changing the key phrase of the container, all servers that were linked to this container will be automatically unlinked. You will have to relink them after changing the key phrase. If you wish to change the key phrase without knowing the current key phrase, you can contact the developers on Discord to request a container reset.


Down below you can find the default config.yml file that is provided with the plugin:


The plugin has a minimal set of permissions, just for commands. These can be found below.
/Reports : reports.reports
/Report : reports.report

/Reports help - Will prompt you with more commands for admins.