SUMMARY:
The "alert-click-command" field in xray-detection.json has been removed in replace of the "alert-click-commands" field. This new field is an array of strings which represent commands that will be executed when a user with sufficient permissions clicks on an xray alert. This multiple command execution is facilitated by an intermediate singular command called "xdet" (as required by API restrictions).
IMPORTANT NOTES:
- If you are using a previous version of the plugin and plan to update, you will also need to update your xray-detection.json file. An updated file can be found in the description.
- Do not use slashes before the commands specified in the array! (i.e. "tp [player], not "/tp [player]").
- The permission to view alerts is now xray.alerts.view
- The permission to use (click on) alerts is xray.alerts.use

This version is beta as it lacks thorough testing. If any errors come up and you are certain that your xray-detection.json file uses appropriate syntax, please notify me asap. As always, view the description of the plugin for further details.

xray-detection.json Additions:
- console-alerts field which determines whether xray alerts will be sent to the console or not.
- alert-hover-message displays a message when hovering over an xray alert (supports color codes).
- alert-click-command runs the specified command for any player that clicks an xray alert. The [player] placeholder can be used here, which represents the username of the subject corresponding to the clicked alert.

For no hover message or click command, simply remove the fields from the configuration.

Using an outdated configuration will result in a NullPointerException. Please check the description for the updated file.