Spectate Safety

Updates World specific spec points: You can now set per-world spec points. When setting a spec point, you can type in a world name as a param and it'll become the specpoint of that world. A world's spec point can be in a different world and it'll still work Info commands: We now have help, info and reload commands. The help command displays and describes all plugin commands accessible to the sender. The info command states the plugin version and which dependencies have been found. Finally the reload command reloads the files into the plugin (Code optimisation) Update Requirements Due to the new messages this update brings, the messages.yml file will have to be reset. You can do this by taking the old messages.yml file out of the SpectateSafety folder and starting up the server. This will generate a new updated messages.yml file which you can update to your desired messages

Updates Group spec-ing: You can now put a group into spectate or take them out using the "g:" prefix in the command. For example /spec g:default would put all players in the "default" group into spectate. This feature requires the Vault plugin to work. If you don't have Vault installed on your server, the plugin will still be operational, it just won't have the group spec feature Plugin now tells players when they've been put in spec by someone else: Honestly dunno how I missed this one when making v1.0 but it's there now. New messages in the messages.yml file to match! New and improved messages.yml: v1.0's messages.yml was meant to be a temporary thing but I ended up leaving it alone to get the plugin out faster. I've now spent time making it more descriptive and easier to use. In order to get this new messages.yml format, you need to delete the old messages.yml text file and then run the server. This should generate a new text file based on the updated default BIG improvements to code readability and documentation: Unlike v1.0, v1.1 actually has readable code (Sorry for what I released before). This means forking it or making pull requests should be much easier for anyone who wants to Update requirements With v1.1.0 comes new messages, which causes a bit of an issue. See, the plugin will try and get all the required messages from the messages.yml file. If it's missing any messages, the plugin won't register any messages and you'll get an error anytime the plugin wants to send you a message. The old messages.yml doesn't have the new messages and won't update automatically. THEREFORE, if updating the plugin, you need to delete the old messages.yml to let the new one generate. After that you can edit the messages all you want. Sorry about the inconvenience