ReportSystem (+ API) | Only Sourcecode

When using SQL database systems, there could be problems reading out the report history via the /reporthistory command. This should now be fixed.

Fixes

• History Get

Changes

• Upgrade mongo-java-driver dependency to the latest stable version
• Upgrade postgresql dependency to the latest stable version
• Upgrade jetbrains annotation dependency for api to the latest stable version

This release brings the ability to disable commands via the configuration file, as well as a few enhancements to the API.

New

• Commands can now be disabled
• The selected database system can be queried via the API
• Individual message strings can be sent to Notify Users via the API
• The login/logouts via the API can now be saved in the database by specifying a boolean

Important
If you upload the update to your server, you have to recreate the configuration file once. Means renaming or deleting the configuration file (config.json) once and reloading the plugin.
You can then copy the old settings and adapt the new configuration options to your server.

This update offers an extension of the API as well as the possibility that players who have reported a player will be informed by a report when the player is closed.

New

• Update open report with api
• Handle notification service with api
• Send information to reporters on report close (Can be disabled)

Important
If you upload the update to your server, you have to recreate the configuration files once. Means renaming or deleting the configuration files (config.json and messages.json) once and reloading the plugin.
You can then copy the old settings and adapt the new configuration options to your server.

This update adds the ability to save history calls from team members.

New

• Save history requests in database (can be disabled)

Changes

• New SQL tables are now created with a BIGINT instead of an INT

Important
If you upload the update to your server, you have to recreate the configuration file once. Means renaming or deleting the configuration file (config.json) once and reloading the plugin.
You can then copy the old settings and adapt the new configuration options to your server.

With this update an API for the report system is available.

New

• API to integrate the report system into your own BungeeCord plugins

Changes

• PostgreSQL has been updated to the latest release version

This version is a small bugfix for all customers with a SQL database system.

Bug fixes:

• SQL Connection timeouts

This small update now offers the possibility to customize the report chat more.

New configurations

• Add option to enable chat colors in report chat
• Add option to disable console for report chat
• Add option to use normal or display name of players

Important
If you upload the update to your server, you have to recreate the configuration file once. Means renaming or deleting the configuration file (config.json) once and reloading the plugin.
You can then copy the old settings and adapt the new configuration options to your server.

This update offers the possibility of a report chat. In addition, an update checker and other small changes have been implemented.

New features

• Update Checker [Can be disabled]
• /reportadmin Command (report.admin)
• /reportchat Command (report.chat) [Can be disabled]
• Command aliases are now configurable in config.json.
• The name of the reporter can now be displayed in report notification messages.
• Sub commands can now be tabbed.

Changes

• The report history is now divided into several pages.
• The report list is now divided into several pages.
• History entries are now sorted by when they were first created.

Bugfixes

• No letters could be entered in custom report reasons, this is now fixed.
• If config entries have not been set, the plugin should no longer throw errors.

Important
If you upload the update to your server, you have to recreate the configuration files once. Means renaming or deleting the configuration files (config.json and messages.json) once and reloading the plugin.
You can then copy the old settings and adapt the new configuration options to your server.