⚡Admin360-Reloaded⚡Manage Real-Time Help Requests! ✅ HEX ✅ Ratings ✅ Statistics -----
Redefines Player-Staff Interaction; Fosters Disciplined & Quality Service!This update allows you to notify your staff members about any existing tickets in the queue that haven't been fully resolved when they join the server. This helps your team get quick updates and resume work quickly. Thanks
@Dartanboy and Technofied for contributing this feature for us!
Changelogs
Configurations
Changes have been made to config.yml.
Configuration Changes
9.2.0 -> 9.3.0: https://www.diffchecker.com/fAEVoY7u/
Changelogs
- Added an option to notify staff members about any pending tickets in the queue when they join the server; Contributed by @Dartanboy
- Made the on-join notification feature configurable in config.yml; Contributed by @Dartanboy
- Approved the pull request https://github.com/denniemok/Admin360-Reloaded/pull/6 by @Dartanboy
- Reviewed the feature contributed by Dartanboy.
- Tested on 1.8.8 and 1.20.6.
Configurations
Changes have been made to config.yml.
Configuration Changes
9.2.0 -> 9.3.0: https://www.diffchecker.com/fAEVoY7u/
This update makes your staff invulnerable to attacks or damage (similar to god mode) when attending a ticket. This helps prevent disruptive players from interfering with your admins' duties. Thanks
@Dartanboy and Technofied for contributing this feature for us!
Changelogs
Configurations
Changes have been made to config.yml.
Configuration Changes
9.1.0 / 9.1.0b -> 9.2.0: https://www.diffchecker.com/dHfDbo7y/
Changelogs
- Added invulnerability support for staff while they are attending to a ticket; Contributed by @Dartanboy
- Made the invulnerability feature configurable in config.yml; Contributed by @Dartanboy
- Approved the pull request https://github.com/denniemok/Admin360-Reloaded/pull/4 by @Dartanboy
- Verified the feature contributed by Dartanboy, in which the invulnerability mode will be toggled on for staff when attending a ticket, and off when a ticket is no longer in the system.
- Built against 1.20.2-API to resolve vulnerability warnings on maven.
- Tested on 1.8.8 and 1.20.6.
Configurations
Changes have been made to config.yml.
Configuration Changes
9.1.0 / 9.1.0b -> 9.2.0: https://www.diffchecker.com/dHfDbo7y/
You're highly recommended to update to this release as soon as possible. There are no changes to 9.1.0's config.yml so it's a simple drag-and-drop replacement!
Changelogs
Configurations
There are no changes made to config.yml relative to release 9.1.0.
Changelogs
- Fixed the error "java.lang.IllegalArgumentException: Illegal group reference: group index is missing" when there is a regex keyword in chat message, e.g., $, \.
Configurations
There are no changes made to config.yml relative to release 9.1.0.
This version is a complete overhaul of previous releases, with a few feature additions, a bunch of QoL changes and performance patches. For details of the new implementation, please refer to the config.yml. Most of the things you need to know already sit there.
Changelogs
Since this version is a complete overhaul of previous releases, bugs are bound to occur more frequently (although I've tested most of the features). Always feel free to report any issues you find and don't forget to rate this resource to show your support!
In case of big issues that cannot be addressed in a timely manner, you may resort to using the last stable release (i.e., 8.1.2b). Thank you for your understanding.
Also, feel free to check out 2 of my new plugins if you have time to do some exploring:
Configurations
There are BIG changes made to config.yml, so I would suggest (throwing away the old one and) using the new config as a starting point. Sorry for the inconvenience caused.
Changelogs
- Added HEX colour support for 1.16+ servers.
- Restructured the configuration file using a hierarchical layout.
- Enabled multiple custom commands to be run by the console (a.k.a. the trigger feature) on 4 major events: on ticket created, on ticket attend, on feedback received, and on reminder sent.
Very useful in giving out custom rewards, opening custom GUIs, or implementing custom actions. - Switched some of the most commonly used messages to multiple-line messages.
- Added a few new messages to better reflect user behaviour.
- Executed database-related tasks asynchronously to prevent Admin360 from lagging the main thread when the database grows to a very large size (very unlikely I suppose... but better than not)
- Recoded how the plugin gets options from config by adding a Config Class, now loading all options into memory on server start or config reload instead of consulting the file every time to reduce I/Os.
- Added /request and /helpop as aliases to /ticket.
- Enhanced the functionality of /ticket purge and /ticket remove.
- Added some more placeholders for custom commands and messages.
- Renamed some of the built-in placeholders for consistency.
- Renamed a few permissions and commands.
- Updated a large part of comments in config.yml to explain the new mechanism.
- Rewrite a few core modules with object-oriented concepts in mind.
- Reinforced better stage transitioning (from pending to attending to completing to completed) with a more in-depth utilisation of existing data structures.
- Migrated the project to the Maven build system.
- Specified 1.14 as api-version to stop legacy errors from appearing in the console (Does not affect legacy versions).
- Dropped 1.7 support. Don't ask me why...
- And of course, Admin360 is now open-sourced on GitHub.
Since this version is a complete overhaul of previous releases, bugs are bound to occur more frequently (although I've tested most of the features). Always feel free to report any issues you find and don't forget to rate this resource to show your support!
In case of big issues that cannot be addressed in a timely manner, you may resort to using the last stable release (i.e., 8.1.2b). Thank you for your understanding.
Also, feel free to check out 2 of my new plugins if you have time to do some exploring:
- SlashPing: Enables the checking of in-game ping with /ping; Modify ping values before display in chat!
- StaffChat (Simplified): Enables staff communication in-game with a designated chat channel!
Configurations
There are BIG changes made to config.yml, so I would suggest (throwing away the old one and) using the new config as a starting point. Sorry for the inconvenience caused.
8.1.2b - Sub-Release
This release aims at fixing a minor forward compatibility issue (i.e., dropping the api-version restriction).
This sub-release is to prevent people from downloading the wrong file.
- The plugin should now be compatible with Spigot1.8 and onwards.
- Unless Spigot drops legacy support or makes massive changes to its API, this plugin should be forever compatible with the latest Spigot release.
- Simply ignore those legacy warnings in the console if any. These warnings do no harm to your server.
- There are no changes to the configuration file (i.e., config.yml). Everything is identical to the previous release (i.e., 8.1.2). Your 8.1.2 config file will not be changed.
And the project is now open-sourced and the source code is available on GitHub.
Unless there is a need for a patch, or I find the need or time to implement some new features, there will be no further updates for a while.
This release aims at fixing a minor forward compatibility issue (i.e., dropping the api-version restriction).
This sub-release is to prevent people from downloading the wrong file.
- The plugin should now be compatible with Spigot1.8 and onwards.
- Unless Spigot drops legacy support or makes massive changes to its API, this plugin should be forever compatible with the latest Spigot release.
- Simply ignore those legacy warnings in the console if any. These warnings do no harm to your server.
- There are no changes to the configuration file (i.e., config.yml). Everything is identical to the previous release (i.e., 8.1.2). Your 8.1.2 config file will not be changed.
And the project is now open-sourced and the source code is available on GitHub.
Unless there is a need for a patch, or I find the need or time to implement some new features, there will be no further updates for a while.
This is a Release for 1.17.x ONLY.
- It's the same as v8.1.2, nothing new has been added.
- You don't have to update or reset the config file if you are already in v8.1.2.
- It's built against Java 16.
- It's built against Spigot 1.17 API. No more legacy plugin warnings on server start.
Requirements
- Spigot 1.17.x or equivalent
- Java 16
The plugin will fail to load if the above requirements cannot be met.
Use v8.1.2 if you for Spigot < 1.17 or Java < 16.
How to use Hex Color?
I just figure out a simple way for you to use Hex Color in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
- It's the same as v8.1.2, nothing new has been added.
- You don't have to update or reset the config file if you are already in v8.1.2.
- It's built against Java 16.
- It's built against Spigot 1.17 API. No more legacy plugin warnings on server start.
Requirements
- Spigot 1.17.x or equivalent
- Java 16
The plugin will fail to load if the above requirements cannot be met.
Use v8.1.2 if you for Spigot < 1.17 or Java < 16.
How to use Hex Color?
I just figure out a simple way for you to use Hex Color in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
Code (Text):
Conversion: #96c3eb → &x&9&6&c&3&e&b
Code (Text):
e.g. '&x&9&6&c&3&e&bPermission Denied!'
This is a Release for 1.16.x ONLY.
- It's the same as v8.1.2, nothing new has been added.
- You don't have to update or reset the config file if you are already in v8.1.2.
- It's built against Java 16.
- It's built against Spigot 1.16 API. No more legacy plugin warnings on server start.
Requirements
- Spigot 1.16.x or equivalent
- Java 16
The plugin will fail to load if the above requirements cannot be met.
Use v8.1.2 if you for Spigot < 1.16 or Java < 16.
How to use Hex Color?
I just figure out a simple way for you to use Hex Color in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
- It's the same as v8.1.2, nothing new has been added.
- You don't have to update or reset the config file if you are already in v8.1.2.
- It's built against Java 16.
- It's built against Spigot 1.16 API. No more legacy plugin warnings on server start.
Requirements
- Spigot 1.16.x or equivalent
- Java 16
The plugin will fail to load if the above requirements cannot be met.
Use v8.1.2 if you for Spigot < 1.16 or Java < 16.
How to use Hex Color?
I just figure out a simple way for you to use Hex Color in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
Code (Text):
Conversion: #96c3eb → &x&9&6&c&3&e&b
Code (Text):
e.g. '&x&9&6&c&3&e&bPermission Denied!'
8.1.2 - Minor Release
It's highly recommended to upgrade to this version if you're still using 8.1.1-DEV or 8.0.0.
Changelog
- Fixed a bug that loads the content from the old config.yml even after the old one has been renamed to old_config.yml on the first server restart.
- Fixed a potential bug that may modify an array concurrently, which may possibly trigger the ConcurrentModificationException in some situations.
- Added a disconnect method to the DataSource for managing database connection when the server is closing.
- Added an option to change the upvote and downvote indicator in /ticket history.
- Refactored a large portion of codes:
a. splitting up the command handler for the 2 different commands
b. reorganizing packages
c. changed some while loops into enhanced for loop
d. deleted several unused methods
e. improved efficiency of the command handler
f. removed redundant codes
g. improved constructor calling and instance parsing
Alpha Test
- Tested SQLite and MySQL functionality with a large data set.
- Tested each of the commands and permissions.
Beta Test
- Tested on a 1.16.5 production server with 50 players.
- No issue reports have been received for 8.1.1-DEV.
Compilation
- Built against Java 8 and Spigot 1.8.8 API.
Hex Colour
You can use hex colour code in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
Upgrade Instructions
If you are upgrading from 8.1.1-DEV, add or change the following settings in your config.yml:
Step 1: Change the version string from 8.1.1 to 8.1.2 (near line #13)
Step 2: Add these 2 lines under the "Ticket / HP History" section (near line #499-500)
which may look like this:
If you are upgrading from other versions, please follow these instructions:
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
8.1.1 -> 8.1.2: https://www.diffchecker.com/Q41wiVN7
8.0.0 -> 8.1.1: https://www.diffchecker.com/ObzXRm8I
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
It's highly recommended to upgrade to this version if you're still using 8.1.1-DEV or 8.0.0.
Changelog
- Fixed a bug that loads the content from the old config.yml even after the old one has been renamed to old_config.yml on the first server restart.
- Fixed a potential bug that may modify an array concurrently, which may possibly trigger the ConcurrentModificationException in some situations.
- Added a disconnect method to the DataSource for managing database connection when the server is closing.
- Added an option to change the upvote and downvote indicator in /ticket history.
- Refactored a large portion of codes:
a. splitting up the command handler for the 2 different commands
b. reorganizing packages
c. changed some while loops into enhanced for loop
d. deleted several unused methods
e. improved efficiency of the command handler
f. removed redundant codes
g. improved constructor calling and instance parsing
Alpha Test
- Tested SQLite and MySQL functionality with a large data set.
- Tested each of the commands and permissions.
Beta Test
- Tested on a 1.16.5 production server with 50 players.
- No issue reports have been received for 8.1.1-DEV.
Compilation
- Built against Java 8 and Spigot 1.8.8 API.
Hex Colour
You can use hex colour code in any plugins that support legacy '&' colour code.
Let's say you want to give a light blue colour for a message, something like #96c3eb.
Actually, you just have to put &x&9&6&c&3&e&b in front of that message and it works!
Code (Text):
Conversion: #96c3eb → &x&9&6&c&3&e&b
Code (Text):
e.g. '&x&9&6&c&3&e&bPermission Denied!'
Upgrade Instructions
If you are upgrading from 8.1.1-DEV, add or change the following settings in your config.yml:
Step 1: Change the version string from 8.1.1 to 8.1.2 (near line #13)
Code (Text):
version: '8.1.2'
Code (Text):
upvote-indicator: '&a▲'
downvote-indicator: '&c▼'
downvote-indicator: '&c▼'
Code (Text):
# History body message
#<TIME> is the time that the player opened the ticket.
history-body: '&7[&f<TIME>&7] &aP:&f<PLAYERNAME> &cS:&f<ADMINNAME> &dR:&f<RATING> &eD:&f<DETAILS>'
upvote-indicator: '&a▲'
downvote-indicator: '&c▼'
#<TIME> is the time that the player opened the ticket.
history-body: '&7[&f<TIME>&7] &aP:&f<PLAYERNAME> &cS:&f<ADMINNAME> &dR:&f<RATING> &eD:&f<DETAILS>'
upvote-indicator: '&a▲'
downvote-indicator: '&c▼'
If you are upgrading from other versions, please follow these instructions:
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
8.1.1 -> 8.1.2: https://www.diffchecker.com/Q41wiVN7
8.0.0 -> 8.1.1: https://www.diffchecker.com/ObzXRm8I
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
8.1.1 - Minor Release
This release might not be that stable due to the newly implemented MySQL support.
It's completely fine if you choose not to upgrade to this version at the moment.
Changelog
- Added "/ticket list" (admin360.staff.basic) so that your staff can see a list of tickets that are currently in the queue.
- Added "/ticket pick <name>" (admin360.staff.basic) so that your staff can pick a ticket to process from the queue without the need to always do the next ticket in the queue.
- Added "/ticket drop" (admin360.staff.drop) so that your staff can drop / abandon a ticket, maybe from an unreasonable guy, to avoid getting revenge rating from him.
- Added "/ticket redirect <name>" (admin360.staff.redirect) so that your staff can redirect / reassign his ticket to another staff.
- Added MySQL Support. You can still use SQLite.
- Fixed a bug that shows incorrect upvote percentage.
- Optimized some arrays and code sections
- Tested on Spigot 1.8.8 and 1.16.4. Should work flawlessly.
- The new MySQL part is tested on a production server and it appears to work properly.
- Fixed some typos in the comment section of the config file.
Upgrade Instructions
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
8.0.0 -> 8.1.1: https://www.diffchecker.com/ObzXRm8I
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
This release might not be that stable due to the newly implemented MySQL support.
It's completely fine if you choose not to upgrade to this version at the moment.
Changelog
- Added "/ticket list" (admin360.staff.basic) so that your staff can see a list of tickets that are currently in the queue.
- Added "/ticket pick <name>" (admin360.staff.basic) so that your staff can pick a ticket to process from the queue without the need to always do the next ticket in the queue.
- Added "/ticket drop" (admin360.staff.drop) so that your staff can drop / abandon a ticket, maybe from an unreasonable guy, to avoid getting revenge rating from him.
- Added "/ticket redirect <name>" (admin360.staff.redirect) so that your staff can redirect / reassign his ticket to another staff.
- Added MySQL Support. You can still use SQLite.
- Fixed a bug that shows incorrect upvote percentage.
- Optimized some arrays and code sections
- Tested on Spigot 1.8.8 and 1.16.4. Should work flawlessly.
- The new MySQL part is tested on a production server and it appears to work properly.
- Fixed some typos in the comment section of the config file.
Upgrade Instructions
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
8.0.0 -> 8.1.1: https://www.diffchecker.com/ObzXRm8I
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
8.0.0 - Major Release
This release imposes a lot of changes to the current base.
Changes
- Added "/ticket history" (admin360.staff.history).
- Added command cooldown for "/ticket create" to avoid spamming.
- Added an option to disable auto-teleport.
- Added "/ticket tp" (admin360.staff.tp) for manual teleport
- Added "/ticket info" (admin360.staff.info) so that staff can read back the "details" submitted by the player when attending a ticket.
- Added an option to notify staff about the player who makes feedback to them, whether or not it is a good rating or bad rating.
- Changed the default colour scheme of config.yml so that it looks more alike to a standard premium plugin.
- Reworked the Honor Point System, introducing upvotes and downvotes.
- Reworked /ticket stats, /ticket hptop and /ticket hpstats to reflect the above changes. It now calculates the number of upvotes, downvotes, the total amount of tickets and the upvote ratio a staff has accomplished.
- Added a column in the database to store the "details" from /ticket create [details] to make /ticket history possible.
Other Changes
- officially support 1.16.4, tested on all other major versions from 1.8.8 all the way up to 1.16.4
- updated many comments in config.yml
- clean up some unused code sections
- optimized some code blocks
- minimized the use of memory and unnecessary java instance
- patched a few potential bugs (e.g. fixed tp errors when the target is dead)
- tested on a few production servers and no major issues were found
Because of these changes,
some new commands have been added;
some permissions have been changed/added;
the database structure has been altered;
many changes have been made to config.yml.
Version 8.0.0 is a big rework. If you don't understand how it works, feel free to contact me. I am happy to explain it to you.
New commands and permissions will all be updated soon on the spigot project page. Stay tuned.
Upgrade Instructions
Since version 7.1.0 is very stable, you can decide whether or not to upgrade to this version.
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
This release imposes a lot of changes to the current base.
Changes
- Added "/ticket history" (admin360.staff.history).
- Added command cooldown for "/ticket create" to avoid spamming.
- Added an option to disable auto-teleport.
- Added "/ticket tp" (admin360.staff.tp) for manual teleport
- Added "/ticket info" (admin360.staff.info) so that staff can read back the "details" submitted by the player when attending a ticket.
- Added an option to notify staff about the player who makes feedback to them, whether or not it is a good rating or bad rating.
- Changed the default colour scheme of config.yml so that it looks more alike to a standard premium plugin.
- Reworked the Honor Point System, introducing upvotes and downvotes.
- Reworked /ticket stats, /ticket hptop and /ticket hpstats to reflect the above changes. It now calculates the number of upvotes, downvotes, the total amount of tickets and the upvote ratio a staff has accomplished.
- Added a column in the database to store the "details" from /ticket create [details] to make /ticket history possible.
Other Changes
- officially support 1.16.4, tested on all other major versions from 1.8.8 all the way up to 1.16.4
- updated many comments in config.yml
- clean up some unused code sections
- optimized some code blocks
- minimized the use of memory and unnecessary java instance
- patched a few potential bugs (e.g. fixed tp errors when the target is dead)
- tested on a few production servers and no major issues were found
Because of these changes,
some new commands have been added;
some permissions have been changed/added;
the database structure has been altered;
many changes have been made to config.yml.
Version 8.0.0 is a big rework. If you don't understand how it works, feel free to contact me. I am happy to explain it to you.
New commands and permissions will all be updated soon on the spigot project page. Stay tuned.
Upgrade Instructions
Since version 7.1.0 is very stable, you can decide whether or not to upgrade to this version.
Step 1: Shut down your server and make a backup of the /plugins/Admin360-Reloaded/ folder.
Step 2: Open the /plugins/Admin360-Reloaded/ folder and check if there is any existing "config_old.yml" in it. If you find one, please delete it or rename it to something else.
Step 3: Rename the .db file from "xxx.db" to "database.db".
Step 4: Download the "Admin360-Reloaded.jar" from our spigot project page.
Step 5: Drag and replace the "Admin360-Reloaded.jar" in your plugin folder.
Step 6: Restart your server.
Step 7: A new "config.yml" is generated. Your old "config.yml" is renamed to "config_old.yml". Compare the new one with the old one and start migrating your settings if you want to.
(Tips: Use "/admin360 reload" to reload the config file)
(Tips: Use a diff checker to find the changes between the new and old config.yml.)
Configuration Changes
7.1.0 -> 8.0.0: https://www.diffchecker.com/8J218FlC
7.1.0 - Minor Release
Finally, there's another update!
Changelog
- clean up and optimized a lot of code sections
- added a few new options in config.yml
- updated many comments in config.yml
- fixed a few potential bugs (e.g. catch errors, unnecessary loops, unused methods, unexpected behaviour etc.)
- added and changed many commands and permissions
- removed /request, the main command is replaced by /ticket
- thoroughly tested on spigot 1.8.8, 1.12.2, 1.14.4 and 1.15.2
- should be compatible with spigot 1.7.x - 1.15.x
- tested on a few production servers and no major issues were found
- [Important] added a config rename module: Admin360 will rename the old config file into "config_old.yml" while generating a new one
Update Instructions
You are highly recommended to update to this version as soon as possible. You do not have to delete your old config file because it will be renamed automatically to "config_old.yml" on server restart. But it is always the best practice if you can make a backup of it. After a new config is generated, you can compare the new one with the old one and start migrating your settings and custom messages.
Updated Documentation
For the new workflow, commands and permissions, please take a look at the updated plugin home page: https://www.spigotmc.org/resources/admin360-reloaded.28285/
Finally, there's another update!
Changelog
- clean up and optimized a lot of code sections
- added a few new options in config.yml
- updated many comments in config.yml
- fixed a few potential bugs (e.g. catch errors, unnecessary loops, unused methods, unexpected behaviour etc.)
- added and changed many commands and permissions
- removed /request, the main command is replaced by /ticket
- thoroughly tested on spigot 1.8.8, 1.12.2, 1.14.4 and 1.15.2
- should be compatible with spigot 1.7.x - 1.15.x
- tested on a few production servers and no major issues were found
- [Important] added a config rename module: Admin360 will rename the old config file into "config_old.yml" while generating a new one
Update Instructions
You are highly recommended to update to this version as soon as possible. You do not have to delete your old config file because it will be renamed automatically to "config_old.yml" on server restart. But it is always the best practice if you can make a backup of it. After a new config is generated, you can compare the new one with the old one and start migrating your settings and custom messages.
Updated Documentation
For the new workflow, commands and permissions, please take a look at the updated plugin home page: https://www.spigotmc.org/resources/admin360-reloaded.28285/
7.0.2 - Minor Update
Hey, this is probably the last update for this week!
Upgrade Reminders
Although the config file has undergone some minor changes, it is not a must for you to regenerate your old config.yml this time. In fact, in this update, we have just changed our directory from "plugins/Admin360/" to "plugins/Admin360-Reloaded/", meaning that you would have a completely new separate folder generated in your server plugins directory. Your old Admin360 folder would be kept untouched, and you can decide what to do with it. But don't forget to backup your old one if you have already changed a lot of settings there!
Plugin Directory Changed
As mentioned above, Admin360-Reloaded will now access "plugins/Admin360-Reloaded" instead of "plugins/Admin360".
Ticket Force-Remove Command
/ticket remove <name> is a staff command that allows staff to forcibly delete a player's ticket no matter it is inQueue, inProgress or AwaitingFeedback. A very powerful command indeed.
Added Admin_Online_Required Option
In the old version, the system requires at least a staff to be online for allowing ticket creation. However, in this update, you can turn it off right there in the config file, so that tickets could be created without any staff online.
New Comand Syntaxes
/ticket, /ticket help, /request, /request help, /admin360, /admin360 help, /admin360 info (default: no permission)
/helpme [details], /ticket create [details] (admin360.player.helpme)
/ticket status (admin360.player.status)
/ticket count (admin360.player.count)
/ticket cancel (admin360.player.helpme)
/ticket yes (admin360.player.helpme)
/ticket no (admin360.player.helpme)
/ticker next (admin360.admin. interact)
/ticket close (admin360.admin. interact)
/ticket purge (admin360.admin.purge)
/ticket remove <name> (admin360.admin.remove)
/ticket stats [name] (admin360.admin.stats)
/ticket leaderboard [#] (admin360.admin.leaderboard)
/admin360 reload (admin360.admin.reload)
Command Alias: /ticket = /request
Difference between /ticket purge and /ticket remove
Purge: a staff command, delete all "pending" (inQueue) tickets.
Remove: a staff command, forcibly delete a player's ticket no matter it is inQueue, inProgress or AwaitingFeedback. A very powerful command.
The system recognises staff as a player with the following permission node:
admin360.admin. interact
New Permission Nodes
admin360.*
admin360.player.*
admin360.player.helpme
admin360.player.status
admin360.player.count
admin360.admin.*
admin360.admin. interact
admin360.admin.purge
admin360.admin.remove
admin360.admin.stats
admin360.admin.leaderboard
admin360.admin.reload
Major Bug Fixed
After testing Admin360-Reloaded 7 on a server with more than 200 players online simultaneously, we have spotted a few bugs that might have affected you as well. We would like to address them immediately in this new update:
1. NullPointerException
This error is triggered when someone has left the server unexpectedly and the feedback reminder scheduler is still running for a null-pointed player, causing the error. This is a rare issue, but it is addressed in this update.
[Admin360] Task #7313135 for Admin360 v7.0.0 generated an exception
java.lang.NullPointerException
2. Internal Exception: players are trapped inside a loop of endless feedback reminders even after they have submitted their feedback.
This error is triggered when a staff leaves the server after closing a ticket, and right before the player has submitted his/her feedback.
This issue is, however, addressed in this update.
It is believed that these errors will not crash your server, but you are suggested to update immediately so as to ensure the overall stability of the system and your service.
Optimizing Config
Changed a few default message options in terms of language, grammar, tone, and formatting.
Compatible with 1.7 - 1.14
Admin360-Reloaded 7.0.1 has undergone some testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Tested on Big Server
Admin360-Reloaded 7.0.1 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
New Config
Added a few new options and changed some messages to support multiple-line layouts.
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.2
#Whenever there is an update available, read the upgrade procedures as instructed on our spigot project page.
#If there are any changes made to this file, for instance an addition of new settings, then you might have to
#delete the old config file and retrieve a new one to ensure proper functioning of the updated version.
#Should you have any problems, please let us know. by kay.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/admin360 help &7to display a list of commands.'
is_player: '&6Admin360 &f» &7Unsupported command sender. This is a player-only command.'
reload: '&6Admin360 &f» &7You have successfully reloaded the config file.'
#This option support multiple lines.
commands_player:
- ''
- '&6Usage&f:'
- ''
- '&6/helpme &e[details] &fSubmit a support request.'
- '&6/request &ecreate [details] &fSubmit a support request.'
- '&6/request &estatus &fCheck your request status.'
- '&6/request &ecount &fCheck overall request status.'
- '&6/request &ecancel &fCancel your request.'
- '&6/admin360 &einfo &fAbout admin360.'
- ''
#This option support multiple lines.
commands_staff:
- ''
- '&cUsage&f:'
- ''
- '&c/request &enext &fProceed to the next request.'
- '&c/request &eclose &fMark a request as completed.'
- '&c/request &epurge &fPurge all the requests.'
- '&c/request &eremove <name> &fRemove a specific request.'
- '&c/request &estats [name] &fHonor points statistics.'
- '&c/request &eleaderboard [#] &fHonor points leaderboard.'
- '&c/admin360 &ereload &fReload the config file.'
- ''
############################################################
# +------------------------------------------------------+ #
# | Creating Requests (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a support request.
#In this section, you can modify messages that are related to /helpme.
#This is a player command with permission node admin360.player.helpme.
# 5 Cases:
# 1 (helpme_status_inqueue) : You have already submitted a ticket. No new tickets will be created.
# 2 (helpme_status_inprocess) : A staff is handling your case right now. No new tickets will be created.
# 3 (helpme_status_feedback) : You still have not provided a valid feedback. No new tickets will be created.
# 4 (no_admin_online) : There are no staff available at the moment. No new tickets will be created.
# 5 (new_ticket) : Not 1 - 4. A new ticket is created and is put in the next position of the queue.
#After a ticket is created, staff_online (with permission admin360.admin.interact) will be notified.
#If there is a reason specified by the user who opened the ticket, more details will be provided in the notification section.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a request.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is now handling your request.'
helpme_status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
#If it is set to true, players will not be allowed to open any requests if there are no staff available online.
admin_online_required: false
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try again later.'
new_ticket: '&6Admin360 &f» &7You have just submitted a request (Position: &c<queue>&7).'
#Use command? Default example using title manager.
new_ticket_usecommand: true
new_ticket_command: 'tm msg <player> &6\n&6Case Created (Position: &c<queue>&6).'
#This option support multiple lines.
notify_staff_new_ticket:
- ''
- '&a<player> &bhas created a new case &b(&a<queue> &brequests remaining).'
- ''
#This option support multiple lines.
notify_staff_new_ticket_with_reason:
- ''
- '&a<player> &bhas created a new case &b(&a<queue> &brequests remaining).'
- '&bFurther details: &f<reason>'
- ''
############################################################
# +------------------------------------------------------+ #
# | Cases Handling (/request next) | #
# +------------------------------------------------------+ #
############################################################
#/request next: Proceed to the next case.
#In this section, you can modify messages that are related to /request next.
#This is a staff command with permission node admin360.admin.interact.
# 3 Cases:
# 1 (next_no_tick et) : There are no tickets in the queue to be handled right now.
# 2 (next_attending) : The ticket is still not closed yet. Proceeding to the next case is not possible.
# 3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the case opening permission for staff: -admin360.player.helpme
#so that they would not be able to exploit the loopholes.
#Since 7.0.2, the plugin itself will not allowed staff with permission admin360.admin.interact
#to do /helpme.
#Staff_online (with permission admin360.admin.interact) will be notified when a ticket status is changed
#from pending to processing.
#The user who opened the ticket will be notified as well.
next_no_ticket: '&6Admin360 &f» &7There are no other cases in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the current case first before proceeding to the next one.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to process your own case.'
#This option support multiple lines.
ticket_user_notify:
- '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Default example using title manager.
ticket_user_notify_usecommand: true
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
#This option support multiple lines.
ticket_staff_notify:
- ''
- '&e<staff> &dis now handling &e<player>&d''s case &d(&e<tickets> &drequests remaining).'
- ''
############################################################
# +------------------------------------------------------+ #
# | Closing Cases (/request close) | #
# +------------------------------------------------------+ #
############################################################
#/request close: Mark a request as completed.
#In this section, you can modify messages that are related to /ticket close.
#This is a staff command with permission node admin360.admin.interact.
# 2 Cases:
# 1 (close_not_attending) : No tickets would be closed because there are no cases currently in progress.
# 2 (close_ticket_closed) : There is a case in progress and it is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully marked this case as completed.'
############################################################
# +------------------------------------------------------+ #
# | Cases Feedback (/request yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/request yes, /request no: Providing service feedback
#In this section, you can modify messages and settings that are related to /request yes and /request no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded to give
#a feedback right after their requests were marked as Completed.
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for your players if the frequency is set to a lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or he/she has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your case is now closed. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to submit a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Your support is our motivation to work better.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Default example using chestcommand: Opening a feedback gui with buttons triggering /request yes and /request no.
feedback_required_usecommand: true
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Requests Status (/request status) | #
# +------------------------------------------------------+ #
############################################################
#/request status: Display your request status.
#In this section, you can modify messages that are related to /request status.
#This is a player command with permission node admin360.player.status.
# 4 Cases:
# 1 (status_no_ticket) : You have not submitted any requests yet.
# 2 (status_inqueue) : You have already submitted a request, which is in the queue now.
# 3 (status_inprogress) : A staff is handling your case right now.
# 4 (status_feedback) : Your case is closed but you still have not submitted any feedback.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any requests. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your case is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is now processing your case.'
status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Requests (/request cancel) | #
# +------------------------------------------------------+ #
############################################################
#/request cancel: Cancel your submitted request.
#In this section, you can modify messages that are related to /request cancel.
#This is a player command with permission node admin360.player.helpme.
# 4 Cases:
# 1 (cancel_no_ticket) : You have no opened requests. There are no requests for you to cancel.
# 2 (cancel_cancelled) : You have cancelled your submitted request successfully.
# 3 (cancel_inprogress) : You cannot cancel your request because a staff is now processing it.
# 4 (cancel_feedback) : You cannot cancel your request because you still have not submitted a feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any requests. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&6Admin360 &f» &7You have successfully cancelled your submitted request.'
cancel_inprogress: '&6Admin360 &f» &7A staff is now processing your case. Request cancelling is not possible.'
cancel_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Requests (/request count) | #
# +------------------------------------------------------+ #
############################################################
#/request count: Display the number of requests.
#In this section, you can modify messages that are related to /request count.
#This is a player command with permission node admin360.player.count.
#This option support multiple lines.
count_message:
- ''
- '&7&m--------------&r &6Counting Requests &7&m--------------'
- ''
- ' &c<inQueue> &frequest(s) in the queue.'
- ' &e<inProgress> &frequest(s) in progress.'
- ' &a<completed> &frequest(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Removing Requests (/request purge, remove) | #
# +------------------------------------------------------+ #
############################################################
#/request purge, /request remove: Purge all or remove part the requests from the database.
#In this section, you can modify messages that are related to /request purge and /request remove.
#This is a staff command with permission node admin360.admin.purge and admin360.admin.remove.
#Purging Requests: Remove all tickets.
#Removing Request: Remove a particular ticket. Only for ticket in queue.
#This option support multiple lines.
purge_message:
- ''
- '&7&m--------------&r &6Purging Requests &7&m--------------'
- ''
- ' &fPurged &c<purged> &fpending requests.'
- ''
- '&7&m--------------------------------------------'
- ''
remove_message: '&6Admin360 &f» &7You have successfully removed <player>''s case.'
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/request leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/request leaderboard, /request stats: Honor points leaderboard and statistics.
#In this section, you can modify messages and settings that are related to /request leaderboard and /request stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
#default_leaderboard_output: Set the number of records shown.
default_leaderboard_output: 5
#This option support multiple lines.
leaderboard_title:
- ''
- '&7&m-------------&r &6Staff Leaderboard &7&m-------------'
- ''
leaderboard_message: ' &6<name>: &f<points> &7honor points'
#This option support multiple lines.
leaderboard_footer:
- ''
- '&7&m--------------------------------------------'
- ''
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
# End of file. You're done with the configuration.
Hey, this is probably the last update for this week!
Upgrade Reminders
Although the config file has undergone some minor changes, it is not a must for you to regenerate your old config.yml this time. In fact, in this update, we have just changed our directory from "plugins/Admin360/" to "plugins/Admin360-Reloaded/", meaning that you would have a completely new separate folder generated in your server plugins directory. Your old Admin360 folder would be kept untouched, and you can decide what to do with it. But don't forget to backup your old one if you have already changed a lot of settings there!
Plugin Directory Changed
As mentioned above, Admin360-Reloaded will now access "plugins/Admin360-Reloaded" instead of "plugins/Admin360".
Ticket Force-Remove Command
/ticket remove <name> is a staff command that allows staff to forcibly delete a player's ticket no matter it is inQueue, inProgress or AwaitingFeedback. A very powerful command indeed.
Added Admin_Online_Required Option
In the old version, the system requires at least a staff to be online for allowing ticket creation. However, in this update, you can turn it off right there in the config file, so that tickets could be created without any staff online.
New Comand Syntaxes
/ticket, /ticket help, /request, /request help, /admin360, /admin360 help, /admin360 info (default: no permission)
/helpme [details], /ticket create [details] (admin360.player.helpme)
/ticket status (admin360.player.status)
/ticket count (admin360.player.count)
/ticket cancel (admin360.player.helpme)
/ticket yes (admin360.player.helpme)
/ticket no (admin360.player.helpme)
/ticker next (admin360.admin. interact)
/ticket close (admin360.admin. interact)
/ticket purge (admin360.admin.purge)
/ticket remove <name> (admin360.admin.remove)
/ticket stats [name] (admin360.admin.stats)
/ticket leaderboard [#] (admin360.admin.leaderboard)
/admin360 reload (admin360.admin.reload)
Command Alias: /ticket = /request
Difference between /ticket purge and /ticket remove
Purge: a staff command, delete all "pending" (inQueue) tickets.
Remove: a staff command, forcibly delete a player's ticket no matter it is inQueue, inProgress or AwaitingFeedback. A very powerful command.
The system recognises staff as a player with the following permission node:
admin360.admin. interact
New Permission Nodes
admin360.*
admin360.player.*
admin360.player.helpme
admin360.player.status
admin360.player.count
admin360.admin.*
admin360.admin. interact
admin360.admin.purge
admin360.admin.remove
admin360.admin.stats
admin360.admin.leaderboard
admin360.admin.reload
Major Bug Fixed
After testing Admin360-Reloaded 7 on a server with more than 200 players online simultaneously, we have spotted a few bugs that might have affected you as well. We would like to address them immediately in this new update:
1. NullPointerException
This error is triggered when someone has left the server unexpectedly and the feedback reminder scheduler is still running for a null-pointed player, causing the error. This is a rare issue, but it is addressed in this update.
Code (Text):
[Admin360] Task #7313135 for Admin360 v7.0.0 generated an exception
java.lang.NullPointerException
2. Internal Exception: players are trapped inside a loop of endless feedback reminders even after they have submitted their feedback.
This error is triggered when a staff leaves the server after closing a ticket, and right before the player has submitted his/her feedback.
This issue is, however, addressed in this update.
It is believed that these errors will not crash your server, but you are suggested to update immediately so as to ensure the overall stability of the system and your service.
Optimizing Config
Changed a few default message options in terms of language, grammar, tone, and formatting.
Compatible with 1.7 - 1.14
Admin360-Reloaded 7.0.1 has undergone some testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Tested on Big Server
Admin360-Reloaded 7.0.1 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
New Config
Added a few new options and changed some messages to support multiple-line layouts.
Code (Text):
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.2
#Whenever there is an update available, read the upgrade procedures as instructed on our spigot project page.
#If there are any changes made to this file, for instance an addition of new settings, then you might have to
#delete the old config file and retrieve a new one to ensure proper functioning of the updated version.
#Should you have any problems, please let us know. by kay.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/admin360 help &7to display a list of commands.'
is_player: '&6Admin360 &f» &7Unsupported command sender. This is a player-only command.'
reload: '&6Admin360 &f» &7You have successfully reloaded the config file.'
#This option support multiple lines.
commands_player:
- ''
- '&6Usage&f:'
- ''
- '&6/helpme &e[details] &fSubmit a support request.'
- '&6/request &ecreate [details] &fSubmit a support request.'
- '&6/request &estatus &fCheck your request status.'
- '&6/request &ecount &fCheck overall request status.'
- '&6/request &ecancel &fCancel your request.'
- '&6/admin360 &einfo &fAbout admin360.'
- ''
#This option support multiple lines.
commands_staff:
- ''
- '&cUsage&f:'
- ''
- '&c/request &enext &fProceed to the next request.'
- '&c/request &eclose &fMark a request as completed.'
- '&c/request &epurge &fPurge all the requests.'
- '&c/request &eremove <name> &fRemove a specific request.'
- '&c/request &estats [name] &fHonor points statistics.'
- '&c/request &eleaderboard [#] &fHonor points leaderboard.'
- '&c/admin360 &ereload &fReload the config file.'
- ''
############################################################
# +------------------------------------------------------+ #
# | Creating Requests (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a support request.
#In this section, you can modify messages that are related to /helpme.
#This is a player command with permission node admin360.player.helpme.
# 5 Cases:
# 1 (helpme_status_inqueue) : You have already submitted a ticket. No new tickets will be created.
# 2 (helpme_status_inprocess) : A staff is handling your case right now. No new tickets will be created.
# 3 (helpme_status_feedback) : You still have not provided a valid feedback. No new tickets will be created.
# 4 (no_admin_online) : There are no staff available at the moment. No new tickets will be created.
# 5 (new_ticket) : Not 1 - 4. A new ticket is created and is put in the next position of the queue.
#After a ticket is created, staff_online (with permission admin360.admin.interact) will be notified.
#If there is a reason specified by the user who opened the ticket, more details will be provided in the notification section.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a request.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is now handling your request.'
helpme_status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
#If it is set to true, players will not be allowed to open any requests if there are no staff available online.
admin_online_required: false
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try again later.'
new_ticket: '&6Admin360 &f» &7You have just submitted a request (Position: &c<queue>&7).'
#Use command? Default example using title manager.
new_ticket_usecommand: true
new_ticket_command: 'tm msg <player> &6\n&6Case Created (Position: &c<queue>&6).'
#This option support multiple lines.
notify_staff_new_ticket:
- ''
- '&a<player> &bhas created a new case &b(&a<queue> &brequests remaining).'
- ''
#This option support multiple lines.
notify_staff_new_ticket_with_reason:
- ''
- '&a<player> &bhas created a new case &b(&a<queue> &brequests remaining).'
- '&bFurther details: &f<reason>'
- ''
############################################################
# +------------------------------------------------------+ #
# | Cases Handling (/request next) | #
# +------------------------------------------------------+ #
############################################################
#/request next: Proceed to the next case.
#In this section, you can modify messages that are related to /request next.
#This is a staff command with permission node admin360.admin.interact.
# 3 Cases:
# 1 (next_no_tick et) : There are no tickets in the queue to be handled right now.
# 2 (next_attending) : The ticket is still not closed yet. Proceeding to the next case is not possible.
# 3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the case opening permission for staff: -admin360.player.helpme
#so that they would not be able to exploit the loopholes.
#Since 7.0.2, the plugin itself will not allowed staff with permission admin360.admin.interact
#to do /helpme.
#Staff_online (with permission admin360.admin.interact) will be notified when a ticket status is changed
#from pending to processing.
#The user who opened the ticket will be notified as well.
next_no_ticket: '&6Admin360 &f» &7There are no other cases in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the current case first before proceeding to the next one.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to process your own case.'
#This option support multiple lines.
ticket_user_notify:
- '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Default example using title manager.
ticket_user_notify_usecommand: true
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
#This option support multiple lines.
ticket_staff_notify:
- ''
- '&e<staff> &dis now handling &e<player>&d''s case &d(&e<tickets> &drequests remaining).'
- ''
############################################################
# +------------------------------------------------------+ #
# | Closing Cases (/request close) | #
# +------------------------------------------------------+ #
############################################################
#/request close: Mark a request as completed.
#In this section, you can modify messages that are related to /ticket close.
#This is a staff command with permission node admin360.admin.interact.
# 2 Cases:
# 1 (close_not_attending) : No tickets would be closed because there are no cases currently in progress.
# 2 (close_ticket_closed) : There is a case in progress and it is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully marked this case as completed.'
############################################################
# +------------------------------------------------------+ #
# | Cases Feedback (/request yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/request yes, /request no: Providing service feedback
#In this section, you can modify messages and settings that are related to /request yes and /request no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded to give
#a feedback right after their requests were marked as Completed.
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for your players if the frequency is set to a lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or he/she has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your case is now closed. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to submit a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Your support is our motivation to work better.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Default example using chestcommand: Opening a feedback gui with buttons triggering /request yes and /request no.
feedback_required_usecommand: true
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Requests Status (/request status) | #
# +------------------------------------------------------+ #
############################################################
#/request status: Display your request status.
#In this section, you can modify messages that are related to /request status.
#This is a player command with permission node admin360.player.status.
# 4 Cases:
# 1 (status_no_ticket) : You have not submitted any requests yet.
# 2 (status_inqueue) : You have already submitted a request, which is in the queue now.
# 3 (status_inprogress) : A staff is handling your case right now.
# 4 (status_feedback) : Your case is closed but you still have not submitted any feedback.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any requests. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your case is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is now processing your case.'
status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Requests (/request cancel) | #
# +------------------------------------------------------+ #
############################################################
#/request cancel: Cancel your submitted request.
#In this section, you can modify messages that are related to /request cancel.
#This is a player command with permission node admin360.player.helpme.
# 4 Cases:
# 1 (cancel_no_ticket) : You have no opened requests. There are no requests for you to cancel.
# 2 (cancel_cancelled) : You have cancelled your submitted request successfully.
# 3 (cancel_inprogress) : You cannot cancel your request because a staff is now processing it.
# 4 (cancel_feedback) : You cannot cancel your request because you still have not submitted a feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any requests. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&6Admin360 &f» &7You have successfully cancelled your submitted request.'
cancel_inprogress: '&6Admin360 &f» &7A staff is now processing your case. Request cancelling is not possible.'
cancel_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/request yes&7, &c/request no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Requests (/request count) | #
# +------------------------------------------------------+ #
############################################################
#/request count: Display the number of requests.
#In this section, you can modify messages that are related to /request count.
#This is a player command with permission node admin360.player.count.
#This option support multiple lines.
count_message:
- ''
- '&7&m--------------&r &6Counting Requests &7&m--------------'
- ''
- ' &c<inQueue> &frequest(s) in the queue.'
- ' &e<inProgress> &frequest(s) in progress.'
- ' &a<completed> &frequest(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Removing Requests (/request purge, remove) | #
# +------------------------------------------------------+ #
############################################################
#/request purge, /request remove: Purge all or remove part the requests from the database.
#In this section, you can modify messages that are related to /request purge and /request remove.
#This is a staff command with permission node admin360.admin.purge and admin360.admin.remove.
#Purging Requests: Remove all tickets.
#Removing Request: Remove a particular ticket. Only for ticket in queue.
#This option support multiple lines.
purge_message:
- ''
- '&7&m--------------&r &6Purging Requests &7&m--------------'
- ''
- ' &fPurged &c<purged> &fpending requests.'
- ''
- '&7&m--------------------------------------------'
- ''
remove_message: '&6Admin360 &f» &7You have successfully removed <player>''s case.'
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/request leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/request leaderboard, /request stats: Honor points leaderboard and statistics.
#In this section, you can modify messages and settings that are related to /request leaderboard and /request stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
#default_leaderboard_output: Set the number of records shown.
default_leaderboard_output: 5
#This option support multiple lines.
leaderboard_title:
- ''
- '&7&m-------------&r &6Staff Leaderboard &7&m-------------'
- ''
leaderboard_message: ' &6<name>: &f<points> &7honor points'
#This option support multiple lines.
leaderboard_footer:
- ''
- '&7&m--------------------------------------------'
- ''
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
# End of file. You're done with the configuration.
7.0.1 - Minor Release
Hey, an update again!
Upgrade Reminders
The config file has undergone major changes. My suggestion here is to delete your old config.yml and let it regenerate a new one for you when you are trying to upgrade from an older version to 7.0.1. Don't forget to backup your old one if you have already changed a lot of settings there.
Configurable "List of Commands"
You can now fully edit the command list /admin360 help. That means, nearly all messages in the plugin can be altered, except the one in /admin360 info.
Now Support Multiple-Line Messages
We have finally added multiple-line support for a few essential message options, including /admin360 help, /ticket purge, /ticket leaderboard, /ticket count, staff notification on new ticket creation (with details or without details), user notification on ticket progression
Leaderboard Output Option
Added an option in the config.yml to control the number of records to be displayed for the staff honour points leaderboard.
Compatible with 1.7 - 1.14
Admin360-Reloaded 7.0.1 has undergone some testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Tested on Big Server
Admin360-Reloaded 7.0.1 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
Minor Bug Fixed
Fixed /admin360 and /ticket Incorrect Syntax + Insufficient Permission Redundancy.
Fixed /ticket leaderboard output limit.
Fixed minor typing errors in the config file.
New Config
Added a few new options and changed some messages to support multiple-line layouts.
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.1
#Whenever there is an new update available, read the upgrade procedures as instructed on our spigot project page.
#If there is any changes made to this file, like an addition of new variables, then you might have to regenerate
#a new config.yml so that admin360 could function properly. Should you have any problems, please let us know.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/admin360 help &7to display a list of commands.'
is_player: '&6Admin360 &f» &7This is a player-only command.'
reload: '&6Admin360 &f» &7The config file has been reloaded successfully.'
commands_player:
- ''
- '&7&m------------&r &6Admin360 Players Commands &7&m------------'
- ''
- '&6/helpme &e[details] &fCreate a ticket.'
- '&6/ticket &estatus &fDisplay your ticket status.'
- '&6/ticket &ecount &fDisplay number of tickets.'
- '&6/ticket &ecancel &fCancel your ticket.'
- '&6/admin360 &einfo &fAbout admin360.'
- ''
commands_staff:
- ''
- '&7&m-------------&r &cAdmin360 Staff Commands &7&m-------------'
- ''
- '&c/ticket &enext &fProceed to the next ticket.'
- '&c/ticket &eclose &fMark a ticket as completed.'
- '&c/ticket &estats [name] &fHonor points statistics.'
- '&c/ticket &eleaderboard [#] &fHonor points leaderboard.'
- '&c/ticket &epurge &fRemove all the tickets.'
- '&c/admin360 &ereload &fReload the config file.'
- ''
############################################################
# +------------------------------------------------------+ #
# | Creating Tickets (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a ticket.
#In this section, you can modify messages that are related to /helpme.
#This is a player command with permission node admin360.player.helpme.
# 5 Cases:
# 1 (helpme_status_inqueue) : You have already submitted a ticket. No new tickets will be created.
# 2 (helpme_status_inprocess) : A staff is handling your case right now. No new tickets will be created.
# 3 (helpme_status_feedback) : You still have not provided a valid feedback. No new tickets will be created.
# 4 (no_admin_online) : There are no staff available at the moment. No new tickets will be created.
# 5 (new_ticket) : Not 1 - 4. A new ticket is created and is put in the next position of the queue.
#After a ticket is created, staff_online (with permission admin360.admin.respond) will be notified (notify_staff_new_ticket).
#If there is a reason specified by the user who has opened the ticket, more details will be provided in the notification for staff.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a ticket. You are not allowed to create another one at the moment.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is now processing your case. You are not allowed to create another ticket at the moment.'
helpme_status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try to open a ticket later.'
new_ticket: '&6Admin360 &f» &7You have just opened a support ticket (Position: &c<queue>&7).'
#Use command? Example using title manager.
new_ticket_usecommand: false
new_ticket_command: 'tm msg <player> &6\n&6Case created (Position: &c<queue>&6).'
notify_staff_new_ticket:
- ''
- '&a<player> &bhas opened a new ticket &b(&a<queue> &btickets remaining).'
- ''
notify_staff_new_ticket_with_reason:
- ''
- '&a<player> &bhas opened a new ticket &b(&a<queue> &btickets remaining).'
- '&bFurther details: &f<reason>'
- ''
############################################################
# +------------------------------------------------------+ #
# | Tickets Handling (/ticket next) | #
# +------------------------------------------------------+ #
############################################################
#/ticket next: Proceed to the next case.
#In this section, you can modify messages that are related to /ticket next.
#This is a staff command with permission node admin360.admin.respond.
# 3 Cases:
# 1 (next_no_ticket) : There are no tickets in the queue to be handled right now.
# 2 (next_attending) : The ticket is still not closed yet. Moving to the next case is not possible.
# 3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the tickets opening permission for staff: -admin360.player.helpme
#so that they would not be able to exploit the loopholes.
#Staff_online (with permission admin360.admin.respond) will be notified (ticket_staff_notify) when a ticket status is changed from pending to processing.
#The involved user who has opened the ticket will be notified (ticket_user_notify) as well.
next_no_ticket: '&6Admin360 &f» &7There are no tickets in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the ticket first before proceeding to the next case.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to process your own ticket.'
ticket_user_notify:
- '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Example using title manager.
ticket_user_notify_usecommand: false
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
ticket_staff_notify:
- ''
- '&e<staff> &dis now handling &e<player>&d''s case &d(&e<tickets> &dtickets remaining).'
- ''
############################################################
# +------------------------------------------------------+ #
# | Closing Tickets (/ticket close) | #
# +------------------------------------------------------+ #
############################################################
#/ticket close: Mark a ticket as completed.
#In this section, you can modify messages that are related to /ticket close.
#This is a staff command with permission node admin360.admin.respond.
# 2 Cases:
# 1 (close_not_attending) : No tickets would be closed because there are no cases currently in progress.
# 2 (close_ticket_closed) : There is a case in progress and it is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully closed this case.'
############################################################
# +------------------------------------------------------+ #
# | Tickets Feedback (/ticket yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/ticket yes, /ticket no: Providing service feedback
#In this section, you can modify messages and settings that are related to /ticket yes and /ticket no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded to give
#a feedback right after their tickets were marked as Completed.
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for your players if the frequency is set to a lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or he/she has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your case is now closed. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to give a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Good luck and have a nice day.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Example using chestcommand.
feedback_required_usecommand: false
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Status (/ticket status) | #
# +------------------------------------------------------+ #
############################################################
#/ticket status: Display your ticket status.
#In this section, you can modify messages that are related to /ticket status.
#This is a player command with permission node admin360.player.status.
# 4 Cases:
# 1 (status_no_ticket) : You have not submitted any tickets yet.
# 2 (status_inqueue) : You have already submitted a ticket, which is on the queue now.
# 3 (status_inprogress) : A staff is handling your case right now.
# 4 (status_feedback) : Your case is closed but you still have not submitted any feedback.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your ticket is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is now processing your case.'
status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Tickets (/ticket cancel) | #
# +------------------------------------------------------+ #
############################################################
#/ticket cancel: Cancel your ticket.
#In this section, you can modify messages that are related to /ticket cancel.
#This is a player command with permission node admin360.player.helpme.
# 4 Cases:
# 1 (cancel_no_ticket) : You have no opened tickets. There are no tickets for you to cancel.
# 2 (cancel_cancelled) : You have cancelled your ticket successfully.
# 3 (cancel_inprogress) : You cannot cancel your ticket because a staff is now processing it.
# 4 (cancel_feedback) : You cannot cancel your ticket because you still have not submitted a feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&6Admin360 &f» &7Your ticket has been cancelled successfully.'
cancel_inprogress: '&6Admin360 &f» &7A staff is now processing your case. You cannot cancel your ticket.'
cancel_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Tickets (/ticket count) | #
# +------------------------------------------------------+ #
############################################################
#/ticket count: Display the number of tickets.
#In this section, you can modify messages that are related to /ticket count.
#This is a player command with permission node admin360.player.count.
count_message:
- ''
- '&7&m---------------&r &6Counting Tickets &7&m---------------'
- ''
- ' &c<inQueue> &7ticket(s) in the queue.'
- ' &e<inProgress> &7ticket(s) in progress.'
- ' &a<completed> &7ticket(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Purging Tickets (/ticket purge) | #
# +------------------------------------------------------+ #
############################################################
#/ticket purge: Remove all the tickets from the database.
#In this section, you can modify messages that are related to /ticket purge.
#This is a staff command with permission node admin360.admin.purge.
purge_message:
- ''
- '&7&m---------------&r &6Purging Tickets &7&m---------------'
- ''
- '&7Purged &c<purged> &7tickets.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/ticket leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/ticket leaderboard, /ticket stats: Honor points leaderboard and statistics.
#In this section, you can modify messages and settings that are related to /ticket leaderboard and /ticket stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
#default_leaderboard_output: Set the number of records shown.
default_leaderboard_output: 5
leaderboard_title:
- ''
- '&7&m-------------&r &6Staff Leaderboard &7&m-------------'
- ''
leaderboard_message: ' &6<name>: &f<points> &7honor points'
leaderboard_footer:
- ''
- '&7&m--------------------------------------------'
- ''
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
# End of file. You're done with the configuration.
Hey, an update again!
Upgrade Reminders
The config file has undergone major changes. My suggestion here is to delete your old config.yml and let it regenerate a new one for you when you are trying to upgrade from an older version to 7.0.1. Don't forget to backup your old one if you have already changed a lot of settings there.
Configurable "List of Commands"
You can now fully edit the command list /admin360 help. That means, nearly all messages in the plugin can be altered, except the one in /admin360 info.
Now Support Multiple-Line Messages
We have finally added multiple-line support for a few essential message options, including /admin360 help, /ticket purge, /ticket leaderboard, /ticket count, staff notification on new ticket creation (with details or without details), user notification on ticket progression
Leaderboard Output Option
Added an option in the config.yml to control the number of records to be displayed for the staff honour points leaderboard.
Compatible with 1.7 - 1.14
Admin360-Reloaded 7.0.1 has undergone some testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Tested on Big Server
Admin360-Reloaded 7.0.1 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
Minor Bug Fixed
Fixed /admin360 and /ticket Incorrect Syntax + Insufficient Permission Redundancy.
Fixed /ticket leaderboard output limit.
Fixed minor typing errors in the config file.
New Config
Added a few new options and changed some messages to support multiple-line layouts.
Code (Text):
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.1
#Whenever there is an new update available, read the upgrade procedures as instructed on our spigot project page.
#If there is any changes made to this file, like an addition of new variables, then you might have to regenerate
#a new config.yml so that admin360 could function properly. Should you have any problems, please let us know.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/admin360 help &7to display a list of commands.'
is_player: '&6Admin360 &f» &7This is a player-only command.'
reload: '&6Admin360 &f» &7The config file has been reloaded successfully.'
commands_player:
- ''
- '&7&m------------&r &6Admin360 Players Commands &7&m------------'
- ''
- '&6/helpme &e[details] &fCreate a ticket.'
- '&6/ticket &estatus &fDisplay your ticket status.'
- '&6/ticket &ecount &fDisplay number of tickets.'
- '&6/ticket &ecancel &fCancel your ticket.'
- '&6/admin360 &einfo &fAbout admin360.'
- ''
commands_staff:
- ''
- '&7&m-------------&r &cAdmin360 Staff Commands &7&m-------------'
- ''
- '&c/ticket &enext &fProceed to the next ticket.'
- '&c/ticket &eclose &fMark a ticket as completed.'
- '&c/ticket &estats [name] &fHonor points statistics.'
- '&c/ticket &eleaderboard [#] &fHonor points leaderboard.'
- '&c/ticket &epurge &fRemove all the tickets.'
- '&c/admin360 &ereload &fReload the config file.'
- ''
############################################################
# +------------------------------------------------------+ #
# | Creating Tickets (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a ticket.
#In this section, you can modify messages that are related to /helpme.
#This is a player command with permission node admin360.player.helpme.
# 5 Cases:
# 1 (helpme_status_inqueue) : You have already submitted a ticket. No new tickets will be created.
# 2 (helpme_status_inprocess) : A staff is handling your case right now. No new tickets will be created.
# 3 (helpme_status_feedback) : You still have not provided a valid feedback. No new tickets will be created.
# 4 (no_admin_online) : There are no staff available at the moment. No new tickets will be created.
# 5 (new_ticket) : Not 1 - 4. A new ticket is created and is put in the next position of the queue.
#After a ticket is created, staff_online (with permission admin360.admin.respond) will be notified (notify_staff_new_ticket).
#If there is a reason specified by the user who has opened the ticket, more details will be provided in the notification for staff.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a ticket. You are not allowed to create another one at the moment.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is now processing your case. You are not allowed to create another ticket at the moment.'
helpme_status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try to open a ticket later.'
new_ticket: '&6Admin360 &f» &7You have just opened a support ticket (Position: &c<queue>&7).'
#Use command? Example using title manager.
new_ticket_usecommand: false
new_ticket_command: 'tm msg <player> &6\n&6Case created (Position: &c<queue>&6).'
notify_staff_new_ticket:
- ''
- '&a<player> &bhas opened a new ticket &b(&a<queue> &btickets remaining).'
- ''
notify_staff_new_ticket_with_reason:
- ''
- '&a<player> &bhas opened a new ticket &b(&a<queue> &btickets remaining).'
- '&bFurther details: &f<reason>'
- ''
############################################################
# +------------------------------------------------------+ #
# | Tickets Handling (/ticket next) | #
# +------------------------------------------------------+ #
############################################################
#/ticket next: Proceed to the next case.
#In this section, you can modify messages that are related to /ticket next.
#This is a staff command with permission node admin360.admin.respond.
# 3 Cases:
# 1 (next_no_ticket) : There are no tickets in the queue to be handled right now.
# 2 (next_attending) : The ticket is still not closed yet. Moving to the next case is not possible.
# 3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the tickets opening permission for staff: -admin360.player.helpme
#so that they would not be able to exploit the loopholes.
#Staff_online (with permission admin360.admin.respond) will be notified (ticket_staff_notify) when a ticket status is changed from pending to processing.
#The involved user who has opened the ticket will be notified (ticket_user_notify) as well.
next_no_ticket: '&6Admin360 &f» &7There are no tickets in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the ticket first before proceeding to the next case.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to process your own ticket.'
ticket_user_notify:
- '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Example using title manager.
ticket_user_notify_usecommand: false
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
ticket_staff_notify:
- ''
- '&e<staff> &dis now handling &e<player>&d''s case &d(&e<tickets> &dtickets remaining).'
- ''
############################################################
# +------------------------------------------------------+ #
# | Closing Tickets (/ticket close) | #
# +------------------------------------------------------+ #
############################################################
#/ticket close: Mark a ticket as completed.
#In this section, you can modify messages that are related to /ticket close.
#This is a staff command with permission node admin360.admin.respond.
# 2 Cases:
# 1 (close_not_attending) : No tickets would be closed because there are no cases currently in progress.
# 2 (close_ticket_closed) : There is a case in progress and it is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully closed this case.'
############################################################
# +------------------------------------------------------+ #
# | Tickets Feedback (/ticket yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/ticket yes, /ticket no: Providing service feedback
#In this section, you can modify messages and settings that are related to /ticket yes and /ticket no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded to give
#a feedback right after their tickets were marked as Completed.
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for your players if the frequency is set to a lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or he/she has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your case is now closed. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to give a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Good luck and have a nice day.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Example using chestcommand.
feedback_required_usecommand: false
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Status (/ticket status) | #
# +------------------------------------------------------+ #
############################################################
#/ticket status: Display your ticket status.
#In this section, you can modify messages that are related to /ticket status.
#This is a player command with permission node admin360.player.status.
# 4 Cases:
# 1 (status_no_ticket) : You have not submitted any tickets yet.
# 2 (status_inqueue) : You have already submitted a ticket, which is on the queue now.
# 3 (status_inprogress) : A staff is handling your case right now.
# 4 (status_feedback) : Your case is closed but you still have not submitted any feedback.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your ticket is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is now processing your case.'
status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Tickets (/ticket cancel) | #
# +------------------------------------------------------+ #
############################################################
#/ticket cancel: Cancel your ticket.
#In this section, you can modify messages that are related to /ticket cancel.
#This is a player command with permission node admin360.player.helpme.
# 4 Cases:
# 1 (cancel_no_ticket) : You have no opened tickets. There are no tickets for you to cancel.
# 2 (cancel_cancelled) : You have cancelled your ticket successfully.
# 3 (cancel_inprogress) : You cannot cancel your ticket because a staff is now processing it.
# 4 (cancel_feedback) : You cannot cancel your ticket because you still have not submitted a feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&6Admin360 &f» &7Your ticket has been cancelled successfully.'
cancel_inprogress: '&6Admin360 &f» &7A staff is now processing your case. You cannot cancel your ticket.'
cancel_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Tickets (/ticket count) | #
# +------------------------------------------------------+ #
############################################################
#/ticket count: Display the number of tickets.
#In this section, you can modify messages that are related to /ticket count.
#This is a player command with permission node admin360.player.count.
count_message:
- ''
- '&7&m---------------&r &6Counting Tickets &7&m---------------'
- ''
- ' &c<inQueue> &7ticket(s) in the queue.'
- ' &e<inProgress> &7ticket(s) in progress.'
- ' &a<completed> &7ticket(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Purging Tickets (/ticket purge) | #
# +------------------------------------------------------+ #
############################################################
#/ticket purge: Remove all the tickets from the database.
#In this section, you can modify messages that are related to /ticket purge.
#This is a staff command with permission node admin360.admin.purge.
purge_message:
- ''
- '&7&m---------------&r &6Purging Tickets &7&m---------------'
- ''
- '&7Purged &c<purged> &7tickets.'
- ''
- '&7&m--------------------------------------------'
- ''
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/ticket leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/ticket leaderboard, /ticket stats: Honor points leaderboard and statistics.
#In this section, you can modify messages and settings that are related to /ticket leaderboard and /ticket stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
#default_leaderboard_output: Set the number of records shown.
default_leaderboard_output: 5
leaderboard_title:
- ''
- '&7&m-------------&r &6Staff Leaderboard &7&m-------------'
- ''
leaderboard_message: ' &6<name>: &f<points> &7honor points'
leaderboard_footer:
- ''
- '&7&m--------------------------------------------'
- ''
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
# End of file. You're done with the configuration.
7.0.0 - Major Release
Finally, there is an update.
Upgrade Reminders
There is a huge difference between 6.0.0 and 7.0.0. My suggestion here is to delete your old config.yml and let it regenerate a new one for you. Don't forget to backup your old one if you have already changed a lot of settings there.
Added 1.13 - 1.14 Support
Added general support for 1.13.x and 1.14.x. Admin360-Reloaded 7.0.0 has undergone some comprehensive testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Dropped GUI modules
We have fully dropped support for the internal GUI in order to make things more simple and lightweight. In some of our previous updates, we have been adding a lot of GUI elements to the system, which makes Admin360 a bit buggy. Maybe a command line-based system would be far more efficient and clean, and we have removed all of them now. However, if you insist to use the internal GUI, you can either build a new one with the help of other major menu plugins such as chestcommand (which I am also using) and deluxemenu, or you can continue to use Admin360-Reloaded 6.0.0 (no more support for older versions). I highly recommend using chestcommand for making a simple GUI for your players.
More Configurable Messages
Messages are now 99% configurable. This's not a joke, it's finally a real thing. We did not try to hide any unconfigurable messages this time, which should be a piece of good news for you. We have actually managed to put most of the messages into the config file, except the lengthy command list (/admin360 help) and the little plugin info section (/admin360 info). We might, however, consider adding multiple-line support for a few message options in our future updates (maybe that will come with a configurable command list as well). Stay tuned.
Configurable Console Command Options
This is an experimental feature. Configurable console command is included in a few essentially used message options, which provides a way to trigger console commands apart from conventional text messages. They can be easily integrated with some of the trending title (e.g. Title Manager) and menu (Chestcommand) plugins to construct a better support experience. More and more options like this will be added to different parts of the config.yml in our future updates.
New Comand Syntaxes
/ticket, /ticket help, /admin360, /admin360 help (default)
/helpme [details], /ticket helpme [details] (admin360.player.helpme)
/ticket status (admin360.player.status)
/ticket count (admin360.player.count)
/ticket cancel (admin360.player.helpme)
/ticket yes (admin360.player.helpme)
/ticket no (admin360.player.helpme)
/ticker next (admin360.admin.respond)
/ticket close (admin360.admin.respond)
/ticket purge (admin360.admin.purge)
/ticket stats <player> (admin360.admin.stats)
/ticket leaderboard (admin360.admin.leaderboard)
/admin360 reload (admin360.admin.reload)
New Permission Nodes
admin360.*
admin360.player.*
admin360.player.helpme
admin360.player.status
admin360.player.count
admin360.admin.*
admin360.admin.respond (Old: admin360.admin.aid)
admin360.admin.purge
admin360.admin.stats (Old: admin360.admin.adminstats)
admin360.admin.leaderboard (Old: admin360.admin.adminstats)
admin360.admin.reload (Old: admin360.reload)
Ultimate Performance
Admin360-Reloaded 7.0.0 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
Major Bug Fixed
/helpme [details] - The details will now be shown clearly and correctly.
Rewriting a large part of the code
The title has told you everything. We are rewriting a large part of the code, so you may consider this as a new plugin. You will need to delete your old config file when trying to upgrade from an older version.
Author Shift
Yes, you will have a more active developer now for this plugin.
UTF-8 Issue
If you are having issues with UTF-8 characters (i.e. special characters, chinese words etc...) in the config file, then you might try to use the following startup parameter for your server:
java -Dfile.encoding=UTF-8 -jar server.jar
Most likely, this issue will only happen for Windows users. If you still encounter similar problems even after you have tried the above method, please inform us. We will try to see if we can fix the issue with some codings.
New Config
The whole config file is re-written with a refined use of language and grammar. We have also renamed all the settings identifiers, and that means you might really need to delete your old config.yml when trying to upgrade from an older version.
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.0
#Whenever there is an new update available, read the update procedures as instructed on our spigot project page.
#If there is any changes made to this file, like an addition of new variables, then you might have to regenerate
#a new config.yml so that this plugin could function properly. Should you have any problems, please let us know.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/ticket help &7for more commands.'
is_player: '&6Admin360 &f» &7Only player is able to execute this command.'
reload: '&6Admin360 &f» &7The config file has been reloaded successfully.'
header: '&7&m---------------&r <title> &7&m---------------'
footer: '&7&m--------------------------------------------'
############################################################
# +------------------------------------------------------+ #
# | Creating Tickets (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a ticket.
#In this section, you can modify the messages that are related to the command /helpme.
#This is a player command with permission node admin360.player.helpme.
#5 Cases:
#Case1 (helpme_status_inqueue) : The player has already submitted a ticket, which is pending in the queue. No new tickets will be created.
#Case2 (helpme_status_inprocess) : A staff is handling the case right now. No new tickets will be created.
#Case3 (helpme_status_feedback) : The player has not provided a valid feedback. No new tickets will be created.
#Case4 (no_admin_online) : There is no staff available at the moment. No new tickets will be created.
#Case5 (new_ticket) : Neither Case 1 to Case 4. A new ticket is created and is put in the next position of the queue .
#After a ticket is created, staff_online (with permission admin360.admin.respond) will be notified (notify_staff_new_ticket).
#If there is a reason specified by the user who opened the ticket, more details (notify_further_details) will be provided in the notification.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a ticket. You are not allowed to create another ticket at the moment.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is handling your case right now. You are not allowed to create another ticket at the moment.'
helpme_status_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try again later.'
new_ticket: '&6Admin360 &f» &7You have just created a ticket (Position: &c<queue>&7).'
#Use command? Example using title manager.
new_ticket_usecommand: true
new_ticket_command: 'tm msg <player> &6\n&6Ticket created (Position: &c<queue>&6).'
notify_staff_new_ticket: '&bA new ticket has been created by &a<player> &b(&a<queue> &btickets remaining).'
notify_further_details: '&bFurther details: &f<reason>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Handling (/ticket next) | #
# +------------------------------------------------------+ #
############################################################
#/ticket next: Proceed to the next ticket.
#In this section, you can modify the messages that are related to the command /ticket next.
#This is a staff command with permission node admin360.admin.respond.
#3 Cases:
#Case1 (next_no_ticket) : There are no tickets in the queue to be handled right now.
#Case2 (next_attending) : The ticket is not closed yet. Moving to the next case is not possible.
#Case3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the tickets creating permission for staff: -admin360.player.helpme
#so that they would not be able to open any tickets.
#Staff_online (with permission admin360.admin.respond) will be notified (ticket_staff_notify) when a ticket status is changed from pending to processing.
#The involved user who opened the ticket will be notified (ticket_user_notify) as well.
next_no_ticket: '&6Admin360 &f» &7There are no tickets in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the ticket first before handling the next case.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to handle your own ticket.'
ticket_user_notify: '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Example using title manager.
ticket_user_notify_usecommand: true
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
ticket_staff_notify: '&e<staff> &dis now handling the ticket submitted by &e<player> &d(&e<tickets> &dtickets remaining).'
############################################################
# +------------------------------------------------------+ #
# | Closing Tickets (/ticket close) | #
# +------------------------------------------------------+ #
############################################################
#/ticket close: Mark a ticket as completed.
#In this section, you can modify the messages that are related to the command /ticket close.
#This is a staff command with permission node admin360.admin.respond.
#2 Cases:
#Case1 (close_not_attending) : No tickets would be closed because there is no ticket in progress.
#Case2 (close_ticket_closed) : There is a ticket in progress and the ticket is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully closed this ticket.'
############################################################
# +------------------------------------------------------+ #
# | Tickets Feedback (/ticket yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/ticket yes, /ticket no: Providing service feedback
#In this section, you can modify the messages and settings that are related to the command /ticket yes and /ticket no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their tickets were marked as Completed (closed).
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for players if the frequency is set to a relatively lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or that player has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your ticket is now closed. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to give a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Good luck and have a nice day.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Example using chestcommand.
feedback_required_usecommand: true
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Status (/ticket status) | #
# +------------------------------------------------------+ #
############################################################
#/ticket status: Display your ticket status.
#In this section, you can modify the messages that are related to the command /ticket status.
#This is a player command with permission node admin360.player.status.
#4 Cases:
#Case1 (status_no_ticket) : You have not submitted any tickets yet.
#Case2 (status_inqueue) : You have already submitted a ticket, which now is on the queue.
#Case3 (status_inprogress) : A staff is handling your case right now.
#Case4 (status_feedback) : Your case is closed but you have not submitted any feedback yet.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets yet. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your ticket is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is handling your case right now.'
status_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Tickets (/ticket cancel) | #
# +------------------------------------------------------+ #
############################################################
#/ticket cancel: Cancel your ticket.
#In this section, you can modify the messages that are related to the command /ticket cancel.
#This is a player command with permission node admin360.player.helpme.
#4 Cases:
#Case1 (cancel_no_ticket) : You have no tickets opened. There is no tickets for you to cancel.
#Case2 (cancel_cancelled) : You have cancelled the ticket successfully.
#Case3 (cancel_inprogress) : You cannot cancel the ticket because a staff is handling it right now.
#Case4 (cancel_feedback) : You cannot cancel the ticket because you have not answered the feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets yet. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&&6Admin360 &f» &7Your ticket has been cancelled successfully.'
cancel_inprogress: '&6Admin360 &f» &7A staff is handling your case right now. You cannot cancel your ticket.'
cancel_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Tickets (/ticket count) | #
# +------------------------------------------------------+ #
############################################################
#/ticket count: Display the number of tickets.
#In this section, you can modify the messages that are related to the command /ticket count.
#This is a player command with permission node admin360.player.count.
count_title: '&6Counting Tickets'
count_message_inqueue: ' &c<inQueue> &7ticket(s) in the queue.'
count_message_inprogress: ' &e<inProgress> &7ticket(s) in progress.'
count_message_completed: ' &a<completed> &7ticket(s) awaiting feedback.'
############################################################
# +------------------------------------------------------+ #
# | Purging Tickets (/ticket purge) | #
# +------------------------------------------------------+ #
############################################################
#/ticket purge: Remove all the tickets from the database.
#In this section, you can modify the messages that are related to the command /ticket purge.
#This is a staff command with permission node admin360.admin.purge.
purge_title: '&6Purging Tickets'
purge_message: '&7Purged &c<purged> &7tickets.'
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/ticket leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/ticket leaderboard, /ticket stats: Honor points leaderboard and statistics.
#In this section, you can modify the messages that are related to the command /ticket leaderboard and /ticket stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
leaderboard_title: '&6Staff Leaderboard'
leaderboard_message: ' &6<name>: &f<points> &7honor points'
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
#Admin360-Reloaded is now maintained by PPT_T, KaytlynJay and tortoise_32 from Hong Kong.
#If you have any problems or suggestions, please let us know. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. Thank you for choosing us.
# End of file <-- You're done with the configuration.
Finally, there is an update.
Upgrade Reminders
There is a huge difference between 6.0.0 and 7.0.0. My suggestion here is to delete your old config.yml and let it regenerate a new one for you. Don't forget to backup your old one if you have already changed a lot of settings there.
Added 1.13 - 1.14 Support
Added general support for 1.13.x and 1.14.x. Admin360-Reloaded 7.0.0 has undergone some comprehensive testing in spigot 1.7.9, 1.8.8, 1.12.2, 1.13 and 1.14. It, therefore, should be able to run without major problems in spigot 1.7.x, 1.8.x, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x and of course the latest version 1.14.x as well. Feel free to submit a report in the discussion section of the project page if you have found any technical issues.
Dropped GUI modules
We have fully dropped support for the internal GUI in order to make things more simple and lightweight. In some of our previous updates, we have been adding a lot of GUI elements to the system, which makes Admin360 a bit buggy. Maybe a command line-based system would be far more efficient and clean, and we have removed all of them now. However, if you insist to use the internal GUI, you can either build a new one with the help of other major menu plugins such as chestcommand (which I am also using) and deluxemenu, or you can continue to use Admin360-Reloaded 6.0.0 (no more support for older versions). I highly recommend using chestcommand for making a simple GUI for your players.
More Configurable Messages
Messages are now 99% configurable. This's not a joke, it's finally a real thing. We did not try to hide any unconfigurable messages this time, which should be a piece of good news for you. We have actually managed to put most of the messages into the config file, except the lengthy command list (/admin360 help) and the little plugin info section (/admin360 info). We might, however, consider adding multiple-line support for a few message options in our future updates (maybe that will come with a configurable command list as well). Stay tuned.
Configurable Console Command Options
This is an experimental feature. Configurable console command is included in a few essentially used message options, which provides a way to trigger console commands apart from conventional text messages. They can be easily integrated with some of the trending title (e.g. Title Manager) and menu (Chestcommand) plugins to construct a better support experience. More and more options like this will be added to different parts of the config.yml in our future updates.
New Comand Syntaxes
/ticket, /ticket help, /admin360, /admin360 help (default)
/helpme [details], /ticket helpme [details] (admin360.player.helpme)
/ticket status (admin360.player.status)
/ticket count (admin360.player.count)
/ticket cancel (admin360.player.helpme)
/ticket yes (admin360.player.helpme)
/ticket no (admin360.player.helpme)
/ticker next (admin360.admin.respond)
/ticket close (admin360.admin.respond)
/ticket purge (admin360.admin.purge)
/ticket stats <player> (admin360.admin.stats)
/ticket leaderboard (admin360.admin.leaderboard)
/admin360 reload (admin360.admin.reload)
New Permission Nodes
admin360.*
admin360.player.*
admin360.player.helpme
admin360.player.status
admin360.player.count
admin360.admin.*
admin360.admin.respond (Old: admin360.admin.aid)
admin360.admin.purge
admin360.admin.stats (Old: admin360.admin.adminstats)
admin360.admin.leaderboard (Old: admin360.admin.adminstats)
admin360.admin.reload (Old: admin360.reload)
Ultimate Performance
Admin360-Reloaded 7.0.0 has been tested thoroughly on a server with 100+ concurrent players without triggering a single performance and technical issue. The plugin, therefore, works flawlessly and efficiently on servers of any size.
Major Bug Fixed
/helpme [details] - The details will now be shown clearly and correctly.
Rewriting a large part of the code
The title has told you everything. We are rewriting a large part of the code, so you may consider this as a new plugin. You will need to delete your old config file when trying to upgrade from an older version.
Author Shift
Yes, you will have a more active developer now for this plugin.
UTF-8 Issue
If you are having issues with UTF-8 characters (i.e. special characters, chinese words etc...) in the config file, then you might try to use the following startup parameter for your server:
java -Dfile.encoding=UTF-8 -jar server.jar
Most likely, this issue will only happen for Windows users. If you still encounter similar problems even after you have tried the above method, please inform us. We will try to see if we can fix the issue with some codings.
New Config
The whole config file is re-written with a refined use of language and grammar. We have also renamed all the settings identifiers, and that means you might really need to delete your old config.yml when trying to upgrade from an older version.
Code (Text):
############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
#Version 7.0.0
#Whenever there is an new update available, read the update procedures as instructed on our spigot project page.
#If there is any changes made to this file, like an addition of new variables, then you might have to regenerate
#a new config.yml so that this plugin could function properly. Should you have any problems, please let us know.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
############################################################
# +------------------------------------------------------+ #
# | Basic | #
# +------------------------------------------------------+ #
############################################################
permission_denied: '&6Admin360 &f» &7Insufficient permission. You do not have access to this command.'
incorrect_syntax: '&6Admin360 &f» &7Incorrect command syntax. Type &6/ticket help &7for more commands.'
is_player: '&6Admin360 &f» &7Only player is able to execute this command.'
reload: '&6Admin360 &f» &7The config file has been reloaded successfully.'
header: '&7&m---------------&r <title> &7&m---------------'
footer: '&7&m--------------------------------------------'
############################################################
# +------------------------------------------------------+ #
# | Creating Tickets (/helpme) | #
# +------------------------------------------------------+ #
############################################################
#/helpme: Create a ticket.
#In this section, you can modify the messages that are related to the command /helpme.
#This is a player command with permission node admin360.player.helpme.
#5 Cases:
#Case1 (helpme_status_inqueue) : The player has already submitted a ticket, which is pending in the queue. No new tickets will be created.
#Case2 (helpme_status_inprocess) : A staff is handling the case right now. No new tickets will be created.
#Case3 (helpme_status_feedback) : The player has not provided a valid feedback. No new tickets will be created.
#Case4 (no_admin_online) : There is no staff available at the moment. No new tickets will be created.
#Case5 (new_ticket) : Neither Case 1 to Case 4. A new ticket is created and is put in the next position of the queue .
#After a ticket is created, staff_online (with permission admin360.admin.respond) will be notified (notify_staff_new_ticket).
#If there is a reason specified by the user who opened the ticket, more details (notify_further_details) will be provided in the notification.
helpme_status_inqueue: '&6Admin360 &f» &7You have already submitted a ticket. You are not allowed to create another ticket at the moment.'
helpme_status_inprocess: '&6Admin360 &f» &7A staff is handling your case right now. You are not allowed to create another ticket at the moment.'
helpme_status_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
no_admin_online: '&6Admin360 &f» &7There are no staff available at the moment. Please try again later.'
new_ticket: '&6Admin360 &f» &7You have just created a ticket (Position: &c<queue>&7).'
#Use command? Example using title manager.
new_ticket_usecommand: true
new_ticket_command: 'tm msg <player> &6\n&6Ticket created (Position: &c<queue>&6).'
notify_staff_new_ticket: '&bA new ticket has been created by &a<player> &b(&a<queue> &btickets remaining).'
notify_further_details: '&bFurther details: &f<reason>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Handling (/ticket next) | #
# +------------------------------------------------------+ #
############################################################
#/ticket next: Proceed to the next ticket.
#In this section, you can modify the messages that are related to the command /ticket next.
#This is a staff command with permission node admin360.admin.respond.
#3 Cases:
#Case1 (next_no_ticket) : There are no tickets in the queue to be handled right now.
#Case2 (next_attending) : The ticket is not closed yet. Moving to the next case is not possible.
#Case3 (next_anti_staff_abuse) : A staff has opened a ticket and is trying to attend it himself.
#Please note that staff should not be allowed to farm tickets.
#You can negate the tickets creating permission for staff: -admin360.player.helpme
#so that they would not be able to open any tickets.
#Staff_online (with permission admin360.admin.respond) will be notified (ticket_staff_notify) when a ticket status is changed from pending to processing.
#The involved user who opened the ticket will be notified (ticket_user_notify) as well.
next_no_ticket: '&6Admin360 &f» &7There are no tickets in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the ticket first before handling the next case.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to handle your own ticket.'
ticket_user_notify: '&6Admin360 &f» &c<staff> &7is now handling your case.'
#Use command? Example using title manager.
ticket_user_notify_usecommand: true
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'
ticket_staff_notify: '&e<staff> &dis now handling the ticket submitted by &e<player> &d(&e<tickets> &dtickets remaining).'
############################################################
# +------------------------------------------------------+ #
# | Closing Tickets (/ticket close) | #
# +------------------------------------------------------+ #
############################################################
#/ticket close: Mark a ticket as completed.
#In this section, you can modify the messages that are related to the command /ticket close.
#This is a staff command with permission node admin360.admin.respond.
#2 Cases:
#Case1 (close_not_attending) : No tickets would be closed because there is no ticket in progress.
#Case2 (close_ticket_closed) : There is a ticket in progress and the ticket is closed now.
close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully closed this ticket.'
############################################################
# +------------------------------------------------------+ #
# | Tickets Feedback (/ticket yes or no) | #
# +------------------------------------------------------+ #
############################################################
#/ticket yes, /ticket no: Providing service feedback
#In this section, you can modify the messages and settings that are related to the command /ticket yes and /ticket no.
#This is a player command with permission node admin360.player.helpme.
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their tickets were marked as Completed (closed).
showReminder: true
#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for players if the frequency is set to a relatively lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20
#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or that player has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.
feedback_required: '&6Admin360 &f» &7Your ticket is now closed. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to give a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Good luck and have a nice day.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'
#Use command? Example using chestcommand.
feedback_required_usecommand: true
feedback_required_command: 'chestcommands open feedback.yml <player>'
############################################################
# +------------------------------------------------------+ #
# | Tickets Status (/ticket status) | #
# +------------------------------------------------------+ #
############################################################
#/ticket status: Display your ticket status.
#In this section, you can modify the messages that are related to the command /ticket status.
#This is a player command with permission node admin360.player.status.
#4 Cases:
#Case1 (status_no_ticket) : You have not submitted any tickets yet.
#Case2 (status_inqueue) : You have already submitted a ticket, which now is on the queue.
#Case3 (status_inprogress) : A staff is handling your case right now.
#Case4 (status_feedback) : Your case is closed but you have not submitted any feedback yet.
status_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets yet. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your ticket is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is handling your case right now.'
status_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Cancel Tickets (/ticket cancel) | #
# +------------------------------------------------------+ #
############################################################
#/ticket cancel: Cancel your ticket.
#In this section, you can modify the messages that are related to the command /ticket cancel.
#This is a player command with permission node admin360.player.helpme.
#4 Cases:
#Case1 (cancel_no_ticket) : You have no tickets opened. There is no tickets for you to cancel.
#Case2 (cancel_cancelled) : You have cancelled the ticket successfully.
#Case3 (cancel_inprogress) : You cannot cancel the ticket because a staff is handling it right now.
#Case4 (cancel_feedback) : You cannot cancel the ticket because you have not answered the feedback.
cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets yet. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&&6Admin360 &f» &7Your ticket has been cancelled successfully.'
cancel_inprogress: '&6Admin360 &f» &7A staff is handling your case right now. You cannot cancel your ticket.'
cancel_feedback: '&6Admin360 &f» &7You have not submitted your feedback yet. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
############################################################
# +------------------------------------------------------+ #
# | Counting Tickets (/ticket count) | #
# +------------------------------------------------------+ #
############################################################
#/ticket count: Display the number of tickets.
#In this section, you can modify the messages that are related to the command /ticket count.
#This is a player command with permission node admin360.player.count.
count_title: '&6Counting Tickets'
count_message_inqueue: ' &c<inQueue> &7ticket(s) in the queue.'
count_message_inprogress: ' &e<inProgress> &7ticket(s) in progress.'
count_message_completed: ' &a<completed> &7ticket(s) awaiting feedback.'
############################################################
# +------------------------------------------------------+ #
# | Purging Tickets (/ticket purge) | #
# +------------------------------------------------------+ #
############################################################
#/ticket purge: Remove all the tickets from the database.
#In this section, you can modify the messages that are related to the command /ticket purge.
#This is a staff command with permission node admin360.admin.purge.
purge_title: '&6Purging Tickets'
purge_message: '&7Purged &c<purged> &7tickets.'
############################################################
# +------------------------------------------------------+ #
# | Leaderboard and Stats (/ticket leaderboard, stats) | #
# +------------------------------------------------------+ #
############################################################
#/ticket leaderboard, /ticket stats: Honor points leaderboard and statistics.
#In this section, you can modify the messages that are related to the command /ticket leaderboard and /ticket stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.
leaderboard_title: '&6Staff Leaderboard'
leaderboard_message: ' &6<name>: &f<points> &7honor points'
stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'
############################################################
# +------------------------------------------------------+ #
# | Final Notes | #
# +------------------------------------------------------+ #
############################################################
#Admin360-Reloaded is now maintained by PPT_T, KaytlynJay and tortoise_32 from Hong Kong.
#If you have any problems or suggestions, please let us know. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. Thank you for choosing us.
# End of file <-- You're done with the configuration.
Please
UPDATE IMMEDIATELY!
. Serious Bugs Fixed
After working for a couples of hours, The Admin360 6.0.0 is out, finally..... after endless waiting....... I am terribly sorry for my poor responsibility on maintaining this plugin for the past few months....
But anyway, I am very pleased that more and more servers were actually using this plugin! Please update immediately to fix the critical Bugs:
(Again,Sorry for the late updates.)
***Important Note: A huge change of the config.yml..... I have altered the description of different sections (comments), as well as to reorganize different sections in a better and understandable order.....together with a bunch of new messages added ....... which would require much patience if you have already made huge changes with the config.yml in the previous version!***
What items have been fixed or added in this update?
1. Now, with 99.9% of messages are configurable
We are very glad to inform you that, it is more than happy to receive such a good suggestion from our beloved clients. And the suggestion made by SucceededKiller has been put into this update! All the messages used in the Admin360-Reloaded are now all available for configuration!!! Cheers! But it also means a huge change in the config.yml structure.......
2. Redesign of the messages
![[IMG]](/proxy/image?url=https%3A%2F%2Fi.imgur.com%2FuNZeC5A.png)
![[IMG]](/proxy/image?url=https%3A%2F%2Fi.imgur.com%2F0TUmqSj.png)
![[IMG]](/proxy/image?url=https%3A%2F%2Fi.imgur.com%2FnjGCcNd.png)
![[IMG]](/proxy/image?url=https%3A%2F%2Fi.imgur.com%2FMY9PxNc.png)
3. Fixed Critical Bugs
A. I have been testing the plugins on all the minecraft versions, from 1.8.7 to 1.12.2 personally, and everything seems working flawlessly.....The only problem I have discovered is all related to the newly adopted GUI system since version 4.0.0, of which items from the GUI could be glitched in many different ways.....
The problem shall be addressed in the last urgent bug fix patch 5.0.0...However, after running the plugin on a 200 + players server for a while, we have spotted a serious bug, which is going to be explained in detail:
To replicate the bug:
Step 1: Version 4.0.0 to 5.0.0 or below....
Step 2: Wear a full set of armor and put random items in your inventory first.
Step 3: Use the command /request admingui for Staff......
Step 4: Press the "Diamond" (Leaderboard) button or the "Shovel" (Purge) button.....
Step 5: Open the admingui quickly by using the command /request admingui............
Step 6: press the same button again, or any other button...
Step 7: you will find your armors glitched out...............
Which is disappointing....... and finally, after hours of research and huge adjustment of the code, the issue is finally solved. That is why, you shall update to this version without hesitation.........It has fixed a serious bug...
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......Once again, Please update the plugins so that these kinds of bugs would not happen again.
2. No Changes for the Permission Nodes
3. Huge Changes for the Config.yml
Please update your config.yml by the following ways:
A. Delete the old config.yml and restart the server
OR
B. Add all the updated section to the old config.yml of version 4.5.0 or 5.0.0 manually (requires much effort)
For Method A (The easiest method):
1. Stop your server
2. Delete the old admin360 jar and upload the new one
3. Delete the old config.yml in the admin360 folder
4. Restart the server and you are good to go
For Method B (Time consuming):
1. Make sure your OLD config file is compatible with version 4.5.0 to 5.0.0
2. Stop your server
3. Delete the old admin360 jar and upload the new one
4. Follow the following guide and add the updated part to the old config.yml manually
The New config.yml in version 6.0.0 looks like this:
#Version 6.0.0
#Admin360-Reloaded is now maintained by LuxannaBB from Hong Kong.
#Whenever there is an new update available, please read the instructions carefully stated on the spigot page.
#You might have to update the config file for new variables and features, most likely, for most of the time.
#It could be done by either deleting the config.yml (and restart the server) to regenerate
#a new one, or by adding several new parts to the old config according to the instructions
#stated and specified on our spigot official page. Thank you for your attention and Good luck to yoru server.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#Should you have any questions, please do not hesitate to approach me.
#Best Regards, LuxannaBB
#=======================================
#Global Prefix
#Set the global prefix of the plugin, which would appear in all the messages.
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#Incorrect Commands
incorrectcmd: "&7Incorrect Commands. Type &c/request help &7for more commands."
#=======================================
#Staff Notification
#Set the messages that could be viewed only by your staff.
newrequestreminder: "&7A new request has been created by &c<player>&7! There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#Admin360 GUI for Players (/request gui)
#A simple GUI to facilitate tickets opening, tracking mechanism for all players.
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Displayname (title)
guiitem1name: "&6&lHelpme"
guiitem2name: "&b&lStatus"
guiitem3name: "&f&lCount"
guiitem4name: "&c&lCancel"
guiitem5name: "&a&lHelp"
#GUI Items Description (lore)
guiitem1lore: "&fRequest for help"
guiitem2lore: "&fView the status of your ticket"
guiitem3lore: "&fGlobal Statistics of the System"
guiitem4lore: "&fCancel the request"
guiitem5lore: "&fCommands List"
#=======================================
#Admin360 GUI for Staff (/request admingui)
#A simple GUI to facilitate tickets managing mechanism for staff.
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Displayname (title)
adminguiitem1name: "&6&lNext"
adminguiitem2name: "&b&lClose"
adminguiitem3name: "&f&lHP Stats"
adminguiitem4name: "&c&lLeaderboard"
adminguiitem5name: "&a&lPurge"
#GUI Items Description (lore)
adminguiitem1lore: "&fDeal with next request"
adminguiitem2lore: "&fClose the current ticket"
adminguiitem3lore: "&fHonor Points Statistics"
adminguiitem4lore: "&fAdmin HP Leaderboard"
adminguiitem5lore: "&fRemove all requests in queue"
#=======================================
#Request/Ticket Creating (/helpme or /request helpme)
#Commands Performed by: Players
#Adjust the messages right after a player has used the command /helpme......
#When players use the command /helpme, it would show 5 different messages under 5 different occasions...
#Case1 (helpme_status_waiting) : The player has a pending request. The command takes no effect.
#Case2 (helpme_status_inprocess) : A staff is currently handling the case of that player. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : A staff has just marked a ticket as closed, but that player have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket and your queue number is displayed.
#Case5 (noadmin) : There is No Staff currently online lol.... (Worst Case Scenario)
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7A staff should be helping with your request right now. Thank you."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7You have just submitted a request successfully and you are currently Number &c<queueno> &7in the queue! Please be patient and our staff is going to approach you soon!"
noadmin: "&7We are terribly sorry for the inconvenience, &c<player>. &7There are no staff currently online... Please try again a few minutes later."
#=======================================
#Request/Ticket Handling (/request next)
#Commands Performed by : Staff
#Adjust the messages right after a staff has used the command /request next......
#When a staff used the command /request next, it would show 2 types of messages under 2 kinds of situation.
#admin_norequestinqueue: There are no tickets/requests in the queue currently. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not been marked as closed.
#admin_nohelpingyourself: The staff has opened a ticket and is attempting to attend it himself... which
#would be stopped kindly by the system with a warning message...
#proceedtonextrequest_messageall: There are still pending requests that you are going to handle. A global message
#would be sent to all the players on the server.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. We deeply appreciate your effort."
admin_alreadyattend: "&cSir <player>, &7You have still handling a request! Use the command &c/request close &7to close the current ticket!"
admin_nohelpingyourself: "&cSir <player>, &7As a member of the staff team, You are not allowed to farm tickets for your own interest!"
proceedtonextrequest_title: "&b&lAdmin360"
proceedtonextrequest_messageall: "&c<staff> &7is now handling the request made by &c<player>&7! There are now &c<nooftickets> &7tickets remaining."
proceedtonextrequest_remind: "&f&oPlease do not hesitate if you need help! &c/helpme&f&o!"
#=======================================
#Closing a Ticket/Request (/request close)
#Commands Performed by : Staff
#Adjust the messages right after a staff has used the command /request close......
#When a staff used the command /request close, it would show 2 types of messages under 2 conditions...
#admin_notattending: You are not attending any tickets. No tickets would be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not handling any requests at this moment. No tickets could be closed."
admin_closedticket: "&cSir <player>, &7You have marked a request as closed! Use the command &c/request next &7to handle the next request!"
#=======================================
#Feedback System (/request yes or /request no)
#Commands Performed by : Players
#Allow users to give feedback to your services with a beautiful designed GUI...
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their requests were marked as Closed.
showReminder: true
#The timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly ignore. (This could be
#annoying if and only if the reminder frequency is set to a relatively lower number.)
reminderFrequency: 20
#Feedback GUI
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Name and Description
fbguiitem1name: "&a&lEXCELLENT"
fbguiitem2name: "&c&lPOOR"
fbguiitem1lore: "&7It was a satisfied experience!"
fbguiitem2lore: "&7It was disappointing!"
#Feedback Message
#Adjust the messages asking players to give a generous feedback.
#giveafeedback: when players are invited to give a feedback after a staff has just closed the ticket.
#noneedtofeedback: There is no need for that player to give a feedback because that player did not open
#a ticket or that player have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
giveafeedback: "&c<player>, &7Your request has been marked as closed. Was the staff helpful? Your generous feedback would be very meaningful to us! Please let us know!"
noneedtofeedback: "&c<player>, &7You are not required to give a feedback at the moment."
thanksforthefeedback: "&7Thank you for your generous feedback, &c<player>. &7Have fun and Have a nice day!"
#=======================================
#Ticket/Request Status (/request status)
#Commands Performed by : Players
#When a player used the command /request status, There are 3 types of messages under 3 different situation...
#status_norequestyet: You have not submitted any tickets yet...
#status_hasrequest: You have a pending ticket submitted, waiting in a queue for a staff to handle it.
#status_adminisattending: A staff is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You have not submitted any request yet. You could open a ticket by &c/helpme&7!"
status_hasrequest: "&c<player>, &7Your request is now in position &c<position>&7. Please be patient and our staff is going to approach you soon!"
status_adminisattending: "&c<player>, &7A staff is handling your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Ticket/Request Cancellation (/request cancel)
#Commands Performed by : Players
#When a player used the command /request cancel, There are 4 types of messages under 4 different situation...
#cancel_norequest: You have no tickets or requests opened, thus you could cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because a staff is handling it currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You have not submitted any request yet. You could open a ticket by &c/helpme&7!"
cancel_cancancel: "&c<player>, &7Your request has been removed from the queue successfully. We are more than happy to offer help if you have further questions!"
cancel_toolate_adminattend: "&7We are terribly sorry, &c<player>. &7It would be too late to cancel your ticket now. A Staff is handling it now."
cancel_toolate_waitingfeedback: "&7We are terribly sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Request Count (/request count)
#Statistics of the system
#Commands Performed by : Players
count_title: "&b&lPending Tickets"
count_message1: "&7There are:"
count_message2: "&7Tickets currently In Queue."
count_message3: "&7Tickets In Progress."
count_message4: "&7Tickets awaiting for Feedbacks."
#=======================================
#Purge Tickets (/request purge)
#Delete all the requets from the database
#Commands Performed by : Staff
purgeticket_title: "&b&lPurge Tickets"
purgeticket_message: "All &b<ammountPurged> &7pending requests have been all purged successfully!"
#=======================================
#PlayersControl GUI (/playerscontrol)
#Commands Performed by : Players
#An useful GUI for Staff to monitor the players at ease...
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
pc_level: "&fLevel:&6 "
pc_hunger: "&fHunger:&6 "
pc_exp: "&fEXP:&6 "
pc_health: "&fHealth:&6 "
pc_gamemode: "&fGamemode:&6 "
pc_flyspeed: "&fFlySpeed:&6 "
pc_leftclick: "&cLeft-Click to Teleport"
pc_shiftleftclick: "&cShift Left-Click to Ban"
pc_rightclick: "&cRight-Click to Kick"
pc_shiftrightclick: "&cShift Right-Click to Mute"
leftclick_cmd: "tp <player>"
shiftleftclick_cmd: "ban <player>"
rightclick_cmd: "kick <player>"
shiftrightclick_cmd: "mute <player>"
#=======================================
#Admin360-Reloaded is now maintained by LuxannaBB from Hong Kong.
#If you have any problems, or any wonderful suggestions, feel free to talk to us. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. We sincerely wish that you would manage to build your first
#successful minecraft server with this simple system! Thank you for choosing us!
#Best Regards, LuxannaBB
========================================================
Admin360 Outlook:
These items might be available in the future:
1. Issue Tracker (Tags like [Hacking Report], [Request], [Closed], [Suspended].......I dk xd
2. Chinese support (And other languages)
3. MySQL support
4. PlayersControl: gui buttons execute a custom command
5. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Have a nice day and good luck to your server and your lovely players!!!!!
Best regards,
LuxannaBB
After working for a couples of hours, The Admin360 6.0.0 is out, finally..... after endless waiting....... I am terribly sorry for my poor responsibility on maintaining this plugin for the past few months....
But anyway, I am very pleased that more and more servers were actually using this plugin! Please update immediately to fix the critical Bugs:
(Again,Sorry for the late updates.)
***Important Note: A huge change of the config.yml..... I have altered the description of different sections (comments), as well as to reorganize different sections in a better and understandable order.....together with a bunch of new messages added ....... which would require much patience if you have already made huge changes with the config.yml in the previous version!***
What items have been fixed or added in this update?
1. Now, with 99.9% of messages are configurable
We are very glad to inform you that, it is more than happy to receive such a good suggestion from our beloved clients. And the suggestion made by SucceededKiller has been put into this update! All the messages used in the Admin360-Reloaded are now all available for configuration!!! Cheers! But it also means a huge change in the config.yml structure.......
2. Redesign of the messages
3. Fixed Critical Bugs
A. I have been testing the plugins on all the minecraft versions, from 1.8.7 to 1.12.2 personally, and everything seems working flawlessly.....The only problem I have discovered is all related to the newly adopted GUI system since version 4.0.0, of which items from the GUI could be glitched in many different ways.....
The problem shall be addressed in the last urgent bug fix patch 5.0.0...However, after running the plugin on a 200 + players server for a while, we have spotted a serious bug, which is going to be explained in detail:
To replicate the bug:
Step 1: Version 4.0.0 to 5.0.0 or below....
Step 2: Wear a full set of armor and put random items in your inventory first.
Step 3: Use the command /request admingui for Staff......
Step 4: Press the "Diamond" (Leaderboard) button or the "Shovel" (Purge) button.....
Step 5: Open the admingui quickly by using the command /request admingui............
Step 6: press the same button again, or any other button...
Step 7: you will find your armors glitched out...............
Which is disappointing....... and finally, after hours of research and huge adjustment of the code, the issue is finally solved. That is why, you shall update to this version without hesitation.........It has fixed a serious bug...
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
Once again, Please update the plugins so that these kinds of bugs would not happen again.2. No Changes for the Permission Nodes
3. Huge Changes for the Config.yml
Please update your config.yml by the following ways:
A. Delete the old config.yml and restart the server
OR
B. Add all the updated section to the old config.yml of version 4.5.0 or 5.0.0 manually (requires much effort)
For Method A (The easiest method):
1. Stop your server
2. Delete the old admin360 jar and upload the new one
3. Delete the old config.yml in the admin360 folder
4. Restart the server and you are good to go
For Method B (Time consuming):
1. Make sure your OLD config file is compatible with version 4.5.0 to 5.0.0
2. Stop your server
3. Delete the old admin360 jar and upload the new one
4. Follow the following guide and add the updated part to the old config.yml manually
The New config.yml in version 6.0.0 looks like this:
Code (Text):
#Version 6.0.0
#Admin360-Reloaded is now maintained by LuxannaBB from Hong Kong.
#Whenever there is an new update available, please read the instructions carefully stated on the spigot page.
#You might have to update the config file for new variables and features, most likely, for most of the time.
#It could be done by either deleting the config.yml (and restart the server) to regenerate
#a new one, or by adding several new parts to the old config according to the instructions
#stated and specified on our spigot official page. Thank you for your attention and Good luck to yoru server.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#Should you have any questions, please do not hesitate to approach me.
#Best Regards, LuxannaBB
#=======================================
#Global Prefix
#Set the global prefix of the plugin, which would appear in all the messages.
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#Incorrect Commands
incorrectcmd: "&7Incorrect Commands. Type &c/request help &7for more commands."
#=======================================
#Staff Notification
#Set the messages that could be viewed only by your staff.
newrequestreminder: "&7A new request has been created by &c<player>&7! There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#Admin360 GUI for Players (/request gui)
#A simple GUI to facilitate tickets opening, tracking mechanism for all players.
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Displayname (title)
guiitem1name: "&6&lHelpme"
guiitem2name: "&b&lStatus"
guiitem3name: "&f&lCount"
guiitem4name: "&c&lCancel"
guiitem5name: "&a&lHelp"
#GUI Items Description (lore)
guiitem1lore: "&fRequest for help"
guiitem2lore: "&fView the status of your ticket"
guiitem3lore: "&fGlobal Statistics of the System"
guiitem4lore: "&fCancel the request"
guiitem5lore: "&fCommands List"
#=======================================
#Admin360 GUI for Staff (/request admingui)
#A simple GUI to facilitate tickets managing mechanism for staff.
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Displayname (title)
adminguiitem1name: "&6&lNext"
adminguiitem2name: "&b&lClose"
adminguiitem3name: "&f&lHP Stats"
adminguiitem4name: "&c&lLeaderboard"
adminguiitem5name: "&a&lPurge"
#GUI Items Description (lore)
adminguiitem1lore: "&fDeal with next request"
adminguiitem2lore: "&fClose the current ticket"
adminguiitem3lore: "&fHonor Points Statistics"
adminguiitem4lore: "&fAdmin HP Leaderboard"
adminguiitem5lore: "&fRemove all requests in queue"
#=======================================
#Request/Ticket Creating (/helpme or /request helpme)
#Commands Performed by: Players
#Adjust the messages right after a player has used the command /helpme......
#When players use the command /helpme, it would show 5 different messages under 5 different occasions...
#Case1 (helpme_status_waiting) : The player has a pending request. The command takes no effect.
#Case2 (helpme_status_inprocess) : A staff is currently handling the case of that player. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : A staff has just marked a ticket as closed, but that player have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket and your queue number is displayed.
#Case5 (noadmin) : There is No Staff currently online lol.... (Worst Case Scenario)
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7A staff should be helping with your request right now. Thank you."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7You have just submitted a request successfully and you are currently Number &c<queueno> &7in the queue! Please be patient and our staff is going to approach you soon!"
noadmin: "&7We are terribly sorry for the inconvenience, &c<player>. &7There are no staff currently online... Please try again a few minutes later."
#=======================================
#Request/Ticket Handling (/request next)
#Commands Performed by : Staff
#Adjust the messages right after a staff has used the command /request next......
#When a staff used the command /request next, it would show 2 types of messages under 2 kinds of situation.
#admin_norequestinqueue: There are no tickets/requests in the queue currently. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not been marked as closed.
#admin_nohelpingyourself: The staff has opened a ticket and is attempting to attend it himself... which
#would be stopped kindly by the system with a warning message...
#proceedtonextrequest_messageall: There are still pending requests that you are going to handle. A global message
#would be sent to all the players on the server.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. We deeply appreciate your effort."
admin_alreadyattend: "&cSir <player>, &7You have still handling a request! Use the command &c/request close &7to close the current ticket!"
admin_nohelpingyourself: "&cSir <player>, &7As a member of the staff team, You are not allowed to farm tickets for your own interest!"
proceedtonextrequest_title: "&b&lAdmin360"
proceedtonextrequest_messageall: "&c<staff> &7is now handling the request made by &c<player>&7! There are now &c<nooftickets> &7tickets remaining."
proceedtonextrequest_remind: "&f&oPlease do not hesitate if you need help! &c/helpme&f&o!"
#=======================================
#Closing a Ticket/Request (/request close)
#Commands Performed by : Staff
#Adjust the messages right after a staff has used the command /request close......
#When a staff used the command /request close, it would show 2 types of messages under 2 conditions...
#admin_notattending: You are not attending any tickets. No tickets would be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not handling any requests at this moment. No tickets could be closed."
admin_closedticket: "&cSir <player>, &7You have marked a request as closed! Use the command &c/request next &7to handle the next request!"
#=======================================
#Feedback System (/request yes or /request no)
#Commands Performed by : Players
#Allow users to give feedback to your services with a beautiful designed GUI...
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their requests were marked as Closed.
showReminder: true
#The timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly ignore. (This could be
#annoying if and only if the reminder frequency is set to a relatively lower number.)
reminderFrequency: 20
#Feedback GUI
#GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#GUI Items Name and Description
fbguiitem1name: "&a&lEXCELLENT"
fbguiitem2name: "&c&lPOOR"
fbguiitem1lore: "&7It was a satisfied experience!"
fbguiitem2lore: "&7It was disappointing!"
#Feedback Message
#Adjust the messages asking players to give a generous feedback.
#giveafeedback: when players are invited to give a feedback after a staff has just closed the ticket.
#noneedtofeedback: There is no need for that player to give a feedback because that player did not open
#a ticket or that player have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
giveafeedback: "&c<player>, &7Your request has been marked as closed. Was the staff helpful? Your generous feedback would be very meaningful to us! Please let us know!"
noneedtofeedback: "&c<player>, &7You are not required to give a feedback at the moment."
thanksforthefeedback: "&7Thank you for your generous feedback, &c<player>. &7Have fun and Have a nice day!"
#=======================================
#Ticket/Request Status (/request status)
#Commands Performed by : Players
#When a player used the command /request status, There are 3 types of messages under 3 different situation...
#status_norequestyet: You have not submitted any tickets yet...
#status_hasrequest: You have a pending ticket submitted, waiting in a queue for a staff to handle it.
#status_adminisattending: A staff is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You have not submitted any request yet. You could open a ticket by &c/helpme&7!"
status_hasrequest: "&c<player>, &7Your request is now in position &c<position>&7. Please be patient and our staff is going to approach you soon!"
status_adminisattending: "&c<player>, &7A staff is handling your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Ticket/Request Cancellation (/request cancel)
#Commands Performed by : Players
#When a player used the command /request cancel, There are 4 types of messages under 4 different situation...
#cancel_norequest: You have no tickets or requests opened, thus you could cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because a staff is handling it currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You have not submitted any request yet. You could open a ticket by &c/helpme&7!"
cancel_cancancel: "&c<player>, &7Your request has been removed from the queue successfully. We are more than happy to offer help if you have further questions!"
cancel_toolate_adminattend: "&7We are terribly sorry, &c<player>. &7It would be too late to cancel your ticket now. A Staff is handling it now."
cancel_toolate_waitingfeedback: "&7We are terribly sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Request Count (/request count)
#Statistics of the system
#Commands Performed by : Players
count_title: "&b&lPending Tickets"
count_message1: "&7There are:"
count_message2: "&7Tickets currently In Queue."
count_message3: "&7Tickets In Progress."
count_message4: "&7Tickets awaiting for Feedbacks."
#=======================================
#Purge Tickets (/request purge)
#Delete all the requets from the database
#Commands Performed by : Staff
purgeticket_title: "&b&lPurge Tickets"
purgeticket_message: "All &b<ammountPurged> &7pending requests have been all purged successfully!"
#=======================================
#PlayersControl GUI (/playerscontrol)
#Commands Performed by : Players
#An useful GUI for Staff to monitor the players at ease...
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
pc_level: "&fLevel:&6 "
pc_hunger: "&fHunger:&6 "
pc_exp: "&fEXP:&6 "
pc_health: "&fHealth:&6 "
pc_gamemode: "&fGamemode:&6 "
pc_flyspeed: "&fFlySpeed:&6 "
pc_leftclick: "&cLeft-Click to Teleport"
pc_shiftleftclick: "&cShift Left-Click to Ban"
pc_rightclick: "&cRight-Click to Kick"
pc_shiftrightclick: "&cShift Right-Click to Mute"
leftclick_cmd: "tp <player>"
shiftleftclick_cmd: "ban <player>"
rightclick_cmd: "kick <player>"
shiftrightclick_cmd: "mute <player>"
#=======================================
#Admin360-Reloaded is now maintained by LuxannaBB from Hong Kong.
#If you have any problems, or any wonderful suggestions, feel free to talk to us. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. We sincerely wish that you would manage to build your first
#successful minecraft server with this simple system! Thank you for choosing us!
#Best Regards, LuxannaBB
Admin360 Outlook:
These items might be available in the future:
1. Issue Tracker (Tags like [Hacking Report], [Request], [Closed], [Suspended].......I dk xd
2. Chinese support (And other languages)
3. MySQL support
4. PlayersControl: gui buttons execute a custom command
5. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Have a nice day and good luck to your server and your lovely players!!!!!
Best regards,
LuxannaBB
Please
UPDATE IMMEDIATELY!
. Serious Bugs Fixed
After working for a couples of hours, The Urgent fix patch 6.0.0 is out, finally..... after endless waiting....... I am terribly sorry for my poor responsibility on maintaining this plugin for the past few months....
But anyway, I am very pleased that more and more servers were actually using this plugin! Please update immediately to fix the critical Bugs:
(Again,Sorry for the late updates.)
***Old Users Concern: Don't worry, nothing is changed for the config.yml for now from the previous version. Keep the old one. But you are reminded that there would be an big update soon......which requires changes to the config file.... Get prepared LOL***
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved critical bugs that have been reported by sir Silver750 and sir RaikenJenova which is much or less about the notorious glitching issus of the newly adopted GUI system in the previous versions. And guess what, it is all fixed......
We have been testing the latest ultimate solution for this glitching with the latest version of Admin360-Reloaded and not a single item from the GUI could be pulled out or even duplicated by a normal player or even a staff. (for example, The trick of using number pad or any other keys to get the apples from the feedback gui would no longer work. Thanks for your concern)
We have worked out to fix the problem of "Tickets Farming".... In the past, a staff could open a ticket, and to attend it by himself, giving himself a good feedback to earn honor points in an illegal way. This is dissatisfying....
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the staff.
But it is not a compulsory, because now, even the staff has opened a ticket, he or she is not allowed to attend it by himself/herself. (Fixed)
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......Once again, Please update the plugins so that these kinds of bugs would not happen again.
B. Frequently Asked Questions and its Answers
Haha that is really nice of you xd. I would be very glad if you could help with the Chinese translation of this plugin. I could only type chinese at a very slow pace and I am not very used to it lol. I am very very sorry hahaha...
The problem you have mentioned might be fixed in this urgent update patch. Please try to update first and see whether the situation is improved. If not, please provide more details and I would be more than happy to make an makeup updates for you. Thank you.... And, if you think that the feedback system is so annoying, you could always nerf it by reducing the reminding frequency or even to stop the reminder from working.
showReminder:true ----> false
reminderFrequency:20 -----> somthing higher, may be 40, or even 100...
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the admins.
2. No Changes for the Permission Nodes
3. No Changes for the Config.yml
The config.yml is completely the same with the one in the version of 4.4.0. But please be reminded that there would be a "relatively" big update "soon"...probably with changes required for the config.yml! Please be prepared!
========================================================
Version 6.0.0 or 7.0.0 Outlook:
These items would be added in the next update:
1. Issue Tracker (Tags like [Hacking Report], [Request], [Closed], [Suspended].......I dk xd
2. Chinese support (And other languages)
3. MySQL support
4. PlayersControl: gui buttons execute a custom command
5. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Have a nice day and good luck to your server and your lovely players!!!!!
Best regards,
LuxannaBB
After working for a couples of hours, The Urgent fix patch 6.0.0 is out, finally..... after endless waiting....... I am terribly sorry for my poor responsibility on maintaining this plugin for the past few months....
But anyway, I am very pleased that more and more servers were actually using this plugin! Please update immediately to fix the critical Bugs:
(Again,Sorry for the late updates.)
***Old Users Concern: Don't worry, nothing is changed for the config.yml for now from the previous version. Keep the old one. But you are reminded that there would be an big update soon......which requires changes to the config file.... Get prepared LOL***
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved critical bugs that have been reported by sir Silver750 and sir RaikenJenova which is much or less about the notorious glitching issus of the newly adopted GUI system in the previous versions. And guess what, it is all fixed......
We have been testing the latest ultimate solution for this glitching with the latest version of Admin360-Reloaded and not a single item from the GUI could be pulled out or even duplicated by a normal player or even a staff. (for example, The trick of using number pad or any other keys to get the apples from the feedback gui would no longer work. Thanks for your concern)
We have worked out to fix the problem of "Tickets Farming".... In the past, a staff could open a ticket, and to attend it by himself, giving himself a good feedback to earn honor points in an illegal way. This is dissatisfying....
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the staff.
But it is not a compulsory, because now, even the staff has opened a ticket, he or she is not allowed to attend it by himself/herself. (Fixed)
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
Once again, Please update the plugins so that these kinds of bugs would not happen again.B. Frequently Asked Questions and its Answers
showReminder:true ----> false
reminderFrequency:20 -----> somthing higher, may be 40, or even 100...
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the admins.
2. No Changes for the Permission Nodes
3. No Changes for the Config.yml
The config.yml is completely the same with the one in the version of 4.4.0. But please be reminded that there would be a "relatively" big update "soon"...probably with changes required for the config.yml! Please be prepared!
========================================================
Version 6.0.0 or 7.0.0 Outlook:
These items would be added in the next update:
1. Issue Tracker (Tags like [Hacking Report], [Request], [Closed], [Suspended].......I dk xd
2. Chinese support (And other languages)
3. MySQL support
4. PlayersControl: gui buttons execute a custom command
5. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Have a nice day and good luck to your server and your lovely players!!!!!
Best regards,
LuxannaBB
Admin360-Reloaded Version 4.4.0. Regular Update
After working for a couple of hours, regular update version 4.4.0 is out.
You are encouraged to update
(Sorry for the late updates. We have already tried our best to publish this update pack.)
What items have been added in this update?
1. More Freedom, More messages allowed to be configured.
We are very glad to inform you that, it is more than happy to receive such a good suggestion from our beloved clients. And the suggestion made by SucceededKiller has been put into this update! More messages are now able to be edited within the config.yml.
2. New Feedback GUI instead of the conventional clumsy and annoying messages.
We have also found that the traditional feedback system, which tends to spam a lot of text to force players to make a feedback, is not as effective as we expect. Many replies that players tend to ignore those feedback reminder and no one is making any feedbacks. To solve this problem, we now introduce a completely new feedback GUI system. Whenever an admin has closed a ticket, An inventory-like GUI would be opened automatically to the player you have just helped! Eventually, your players would be encouraged to make a constructive feedback, since the GUI is blocking their way xd. Apart from this, they just have to simply click "Yes" or "No" and no more clumsy and complicated /request yes and /request no is required. Thanks god XD.
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2FgP41FLR.png)
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2Fy8gYUDB.png)
Since there are changed made to the Config.yml in this update, config file has to be updated as well.
This could be done by either
1. Delete the old config.yml, and restart the server. A new config file would be generated
OR
2. But if you have made a lot of changes to the old config file, and is not planned/willing to deleted your hard work (I understand that xd), you shall follow the instructions CAREFULLY BELOW:
a. Make sure your OLD config file is in version 4.3.0
b. Copy the following Updated Parts to your old config file. Reload the config file by /admin360 reload or Restart the server (recommended)
Updated Parts (Only applicable for updating config.yml from 4.3.0 to 4.4.0 MANUALLY
#=======================================
#Feedback GUI (New Part)
#A simple GUI to facilitate the feedback mechanism.
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiitem1title: "&a&lEXCELLENT"
fbguiitem2title: "&c&lPOOR"
#=======================================
#AdminMessage: Set messages that could be viewed only by Admins. (New Part)
newrequestreminder: "&7A new request has been created by &c<player>&7!"
remainingrequestreminder: "&7There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#Helpme Section (Existing Part)
currentqueuestatus: "&7You are currently Number &c<queueno> &7in the queue! Please be patient!"
#=======================================
The New config.yml in version 4.4.0 looks like this:
#Version 4.4.0
#Admin360-Reloaded is maintained by Dennie, Jerryui and Thomas Tang from Hong Kong.
#Whenever there is a new update, please read the instructions carefully.
#You may have to update the config file for new variables and features.
#It could be done by either deleting the config.yml (and restart the server) to regenerate
#a new one, or by adding several new parts to the old config according to the instructions
#stated and specified on our spigot official page. Thank you for your attention.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#=======================================
#Feedback Reminder
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their tickets were closed.
showReminder: true
#The timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they forget. (This would be a bit annoying
#if the reminder frequency is set to a relatively lower number.)
reminderFrequency: 20
#=======================================
#Global Prefix: Set the global prefix of the plugin
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#AdminMessage: Set messages that could be viewed only by Admins.
newrequestreminder: "&7A new request has been created by &c<player>&7!"
remainingrequestreminder: "&7There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#PlayersControl GUI (/playerscontrol)
#A useful gui for admins to teleport, kick, ban and banip at ease.
#ItemName: The font format for the name of the skull of a player
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked a player
#BanMessage: Message after you have banned a player
#BanIPMessage: Message after you have banned a player's IP
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
TpMessage: "&7You have been teleported to &c<player>&7 !"
KickMessage: "&7You have kicked &c<player>&7 !"
BanMessage: "&7You have banned &c<player>&7 !"
BanIPMessage: "&7You have banned &c<player>&7's IP!"
#=======================================
#Player Request GUI (/request gui)
#A simple GUI to facilitate tickets opening mechanism.
#Player GUI Title and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Player GUI Items Displayname
guiitem1text: "&6&lHelpme"
guiitem2text: "&b&lStatus"
guiitem3text: "&f&lCount"
guiitem4text: "&c&lCancel"
guiitem5text: "&a&lHelp"
#=======================================
#Admin Request GUI (/request admingui)
#A simple GUI to facilitate tickets managing mechanism.
#Admin GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Admin GUI Items Displayname
adminguiitem1text: "&6&lNext"
adminguiitem2text: "&b&lClose"
adminguiitem3text: "&f&lHP Stats"
adminguiitem4text: "&c&lLeaderboard"
adminguiitem5text: "&a&lPurge"
#=======================================
#Helpme Section (/helpme or /request helpme)
#Messages right after a player has performed the /helpme command......
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage & currentqueuestatus) : Neither Case 1 to Case 3. You are allowed to open a ticket and your queue number is displayed.
#Case5 (noadmin) : There is no admin currently online lol....
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7An admin should be helping with your ticket right now."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !"
currentqueuestatus: "&7You are currently Number &c<queueno> &7in the queue! Please be patient!"
noadmin: "&7Sorry, &c<player>. &7There are no online staff at the moment."
#=======================================
#Next Request Section (/request next)
#Messages right after an admin has performed the /request next command......
#When an admin performs /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in the queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~"
admin_alreadyattend: "&cSir <player>, &7You have already attended to help a player!"
#=======================================
#Close Ticket Section (/request close)
#Messages right after an admin has performed the /request close command......
#When an admin performs /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not attending any requests!"
admin_closedticket: "&cSir <player>, &7You have closed a ticket successfully! "
#=======================================
#Feedback Section (/request yes or /request no)
#Allow users to give feedback to your services.
#Feedback GUI
#A simple GUI to facilitate the feedback mechanism.
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiitem1title: "&a&lEXCELLENT"
fbguiitem2title: "&c&lPOOR"
#Feedback Message
#Messages asking players to give constructive feedbacks.
#giveafeedback: when players are asked to give a feedback after the Admin has closed the ticket.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
giveafeedback: "&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! "
noneedtofeedback: "&c<player>, &7There are no tickets that are awaiting for your feedback at the moment."
thanksforthefeedback: "&7Thank you for your feedback, &c<player>. &7Have a nice day!"
#=======================================
#Request Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You do not have any requests yet."
status_adminisattending: "&c<player>, &7An admin is attending your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Request Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have canceled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You do not have any ticket currently. "
cancel_cancancel: "&c<player>, &7Your ticket has been successfully canceled. Thanks for using the system!"
cancel_toolate_adminattend: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now."
cancel_toolate_waitingfeedback: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Admin360-Reloaded is maintained by Dennie , Jerryui and Thomas Tang from Hong Kong.
#If you have any problems, or any wonderful suggestions, feel free to talk to us. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. We sincerely wish that you would manage to build your first
#successful Minecraft server with this simple system! Thank you for choosing us!
========================================================
Version 5.0 Outlook:
These items would be added in the next update:
1. Report GUI
2. Chinese support (And other languages)
3. MySQL support
4. Allow to change the primary command (Command Aliases)
5. PlayersControl: gui buttons execute a custom command
6. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, feel free to contact us so that we would be able to make an urgent update as fast as we could. Thank you for using this plugin and Have a nice day!
After working for a couple of hours, regular update version 4.4.0 is out.
You are encouraged to update
(Sorry for the late updates. We have already tried our best to publish this update pack.)
What items have been added in this update?
1. More Freedom, More messages allowed to be configured.
2. New Feedback GUI instead of the conventional clumsy and annoying messages.
We have also found that the traditional feedback system, which tends to spam a lot of text to force players to make a feedback, is not as effective as we expect. Many replies that players tend to ignore those feedback reminder and no one is making any feedbacks. To solve this problem, we now introduce a completely new feedback GUI system. Whenever an admin has closed a ticket, An inventory-like GUI would be opened automatically to the player you have just helped! Eventually, your players would be encouraged to make a constructive feedback, since the GUI is blocking their way xd. Apart from this, they just have to simply click "Yes" or "No" and no more clumsy and complicated /request yes and /request no is required. Thanks god XD.
Since there are changed made to the Config.yml in this update, config file has to be updated as well.
This could be done by either
1. Delete the old config.yml, and restart the server. A new config file would be generated
OR
2. But if you have made a lot of changes to the old config file, and is not planned/willing to deleted your hard work (I understand that xd), you shall follow the instructions CAREFULLY BELOW:
a. Make sure your OLD config file is in version 4.3.0
b. Copy the following Updated Parts to your old config file. Reload the config file by /admin360 reload or Restart the server (recommended)
Updated Parts (Only applicable for updating config.yml from 4.3.0 to 4.4.0 MANUALLY
Code (Text):
#=======================================
#Feedback GUI (New Part)
#A simple GUI to facilitate the feedback mechanism.
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiitem1title: "&a&lEXCELLENT"
fbguiitem2title: "&c&lPOOR"
#=======================================
#AdminMessage: Set messages that could be viewed only by Admins. (New Part)
newrequestreminder: "&7A new request has been created by &c<player>&7!"
remainingrequestreminder: "&7There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#Helpme Section (Existing Part)
currentqueuestatus: "&7You are currently Number &c<queueno> &7in the queue! Please be patient!"
#=======================================
The New config.yml in version 4.4.0 looks like this:
Code (Text):
#Version 4.4.0
#Admin360-Reloaded is maintained by Dennie, Jerryui and Thomas Tang from Hong Kong.
#Whenever there is a new update, please read the instructions carefully.
#You may have to update the config file for new variables and features.
#It could be done by either deleting the config.yml (and restart the server) to regenerate
#a new one, or by adding several new parts to the old config according to the instructions
#stated and specified on our spigot official page. Thank you for your attention.
#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#=======================================
#Feedback Reminder
#Set it to true if you would like your players to be reminded for
#giving a feedback right after their tickets were closed.
showReminder: true
#The timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they forget. (This would be a bit annoying
#if the reminder frequency is set to a relatively lower number.)
reminderFrequency: 20
#=======================================
#Global Prefix: Set the global prefix of the plugin
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#AdminMessage: Set messages that could be viewed only by Admins.
newrequestreminder: "&7A new request has been created by &c<player>&7!"
remainingrequestreminder: "&7There are now &c<queuenumber> &7tickets remaining!"
#=======================================
#PlayersControl GUI (/playerscontrol)
#A useful gui for admins to teleport, kick, ban and banip at ease.
#ItemName: The font format for the name of the skull of a player
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked a player
#BanMessage: Message after you have banned a player
#BanIPMessage: Message after you have banned a player's IP
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
TpMessage: "&7You have been teleported to &c<player>&7 !"
KickMessage: "&7You have kicked &c<player>&7 !"
BanMessage: "&7You have banned &c<player>&7 !"
BanIPMessage: "&7You have banned &c<player>&7's IP!"
#=======================================
#Player Request GUI (/request gui)
#A simple GUI to facilitate tickets opening mechanism.
#Player GUI Title and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Player GUI Items Displayname
guiitem1text: "&6&lHelpme"
guiitem2text: "&b&lStatus"
guiitem3text: "&f&lCount"
guiitem4text: "&c&lCancel"
guiitem5text: "&a&lHelp"
#=======================================
#Admin Request GUI (/request admingui)
#A simple GUI to facilitate tickets managing mechanism.
#Admin GUI Name and Items ID
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Admin GUI Items Displayname
adminguiitem1text: "&6&lNext"
adminguiitem2text: "&b&lClose"
adminguiitem3text: "&f&lHP Stats"
adminguiitem4text: "&c&lLeaderboard"
adminguiitem5text: "&a&lPurge"
#=======================================
#Helpme Section (/helpme or /request helpme)
#Messages right after a player has performed the /helpme command......
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage & currentqueuestatus) : Neither Case 1 to Case 3. You are allowed to open a ticket and your queue number is displayed.
#Case5 (noadmin) : There is no admin currently online lol....
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7An admin should be helping with your ticket right now."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !"
currentqueuestatus: "&7You are currently Number &c<queueno> &7in the queue! Please be patient!"
noadmin: "&7Sorry, &c<player>. &7There are no online staff at the moment."
#=======================================
#Next Request Section (/request next)
#Messages right after an admin has performed the /request next command......
#When an admin performs /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in the queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~"
admin_alreadyattend: "&cSir <player>, &7You have already attended to help a player!"
#=======================================
#Close Ticket Section (/request close)
#Messages right after an admin has performed the /request close command......
#When an admin performs /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not attending any requests!"
admin_closedticket: "&cSir <player>, &7You have closed a ticket successfully! "
#=======================================
#Feedback Section (/request yes or /request no)
#Allow users to give feedback to your services.
#Feedback GUI
#A simple GUI to facilitate the feedback mechanism.
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiname: "&6Rate Our Service!"
fbguiitem1: "GOLDEN_APPLE"
fbguiitem2: "BARRIER"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
fbguiitem1title: "&a&lEXCELLENT"
fbguiitem2title: "&c&lPOOR"
#Feedback Message
#Messages asking players to give constructive feedbacks.
#giveafeedback: when players are asked to give a feedback after the Admin has closed the ticket.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
giveafeedback: "&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! "
noneedtofeedback: "&c<player>, &7There are no tickets that are awaiting for your feedback at the moment."
thanksforthefeedback: "&7Thank you for your feedback, &c<player>. &7Have a nice day!"
#=======================================
#Request Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You do not have any requests yet."
status_adminisattending: "&c<player>, &7An admin is attending your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Request Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have canceled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You do not have any ticket currently. "
cancel_cancancel: "&c<player>, &7Your ticket has been successfully canceled. Thanks for using the system!"
cancel_toolate_adminattend: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now."
cancel_toolate_waitingfeedback: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Admin360-Reloaded is maintained by Dennie , Jerryui and Thomas Tang from Hong Kong.
#If you have any problems, or any wonderful suggestions, feel free to talk to us. We are more than happy to know your situation!
#Have a nice day with this plugin, and good luck to your server. We sincerely wish that you would manage to build your first
#successful Minecraft server with this simple system! Thank you for choosing us!
========================================================
Version 5.0 Outlook:
These items would be added in the next update:
1. Report GUI
2. Chinese support (And other languages)
3. MySQL support
4. Allow to change the primary command (Command Aliases)
5. PlayersControl: gui buttons execute a custom command
6. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, feel free to contact us so that we would be able to make an urgent update as fast as we could. Thank you for using this plugin and Have a nice day!
Admin360-Reloaded Version 4.3.0. Urgent Fix
Please UPDATE IMMEDIATELY!. Serious Bugs Fixed
After working for a couples of hours, Urgent fix version 4.3.0 is out.
Please update immediately to fix the critical Bugs:
(Sorry for the late updates. We have already tried our best to publish this urgent update pack)
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved critical bugs that have been reported by sir Xx_Cyborg_xX and sir SuperRonanCraft.
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
B.
Admin360 is not designed for admin to open a ticket on their own and to attend the ticket by themselves at the same time. We are going to solve this problem in the next update.
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the admins.
These are the critical bugs fixed in this update. We are really sorry to cause these kinds of issues. Please update the plugins so that these kinds of bugs would not happen again.
2. New Permissions (Important)
We have changed the old permission nodes and at the same time, we have added some new permission nodes that are suggested by our users.
The following is a list of the permission nodes in version 4.3.0:
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2F7XMyy3l.png)
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2FONfuH1h.png)
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2FeNpQotQ.png)
You are required to delete the old config.yml to recreate a new one.
You shall save the old one if you have made changes to it.
The New config.yml in version 4.3.0 looks like this:
#Version 4.3.0
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked a player
#BanMessage: Message after you have banned a player
#BanIPMessage: Message after you have banned a player's IP
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
TpMessage: "&7You have been teleported to &c<player>&7 !"
KickMessage: "&7You have kicked &c<player>&7 !"
BanMessage: "&7You have banned &c<player>&7 !"
BanIPMessage: "&7You have banned &c<player>&7's IP!"
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Player GUI Items Displayname (/request gui)
guiitem1text: "&6&lHelpme"
guiitem2text: "&b&lStatus"
guiitem3text: "&f&lCount"
guiitem4text: "&c&lCancel"
guiitem5text: "&a&lHelp"
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: "&6&lNext"
adminguiitem2text: "&b&lClose"
adminguiitem3text: "&f&lHP Stats"
adminguiitem4text: "&c&lLeaderboard"
adminguiitem5text: "&a&lPurge"
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7An admin should be helping with your ticket right now."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !"
noadmin: "&7Sorry, &c<player>. &7There are no online staff at the the moment."
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~"
admin_alreadyattend: "&cSir <player>, &7You have already attended to help a player!"
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not attending any requests!"
admin_closedticket: "&cSir <player>, &7You have closed a ticket successfully! "
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: "&c<player>, &7There are no tickets that are awaiting for your feedback at the moment."
thanksforthefeedback: "&7Thank you for your feedback, &c<player>. &7Have a nice day!"
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: "&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! "
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You do not have any requests yet."
status_adminisattending: "&c<player>, &7An admin is attending your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You do not have any ticket currently. "
cancel_cancancel: "&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!"
cancel_toolate_adminattend: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now."
cancel_toolate_waitingfeedback: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
========================================================
Version 5.0.0 Outlook:
These items would be added in the next update:
1. Report GUI
2. Chinese support (And other languages)
3. MySQL support
4. Allow to change the primary command (Command Aliases)
5. PlayersControl: gui buttons execute a custom command
6. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Again, Sorry for making these critical issues.
Please UPDATE IMMEDIATELY!. Serious Bugs Fixed
After working for a couples of hours, Urgent fix version 4.3.0 is out.
Please update immediately to fix the critical Bugs:
(Sorry for the late updates. We have already tried our best to publish this urgent update pack)
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved critical bugs that have been reported by sir Xx_Cyborg_xX and sir SuperRonanCraft.
This critical problem has been solved. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
B.
Quick fix: To neglect the permission "-admin360.player.helpme" in the permission plugin for all the admins.
These are the critical bugs fixed in this update. We are really sorry to cause these kinds of issues. Please update the plugins so that these kinds of bugs would not happen again.
2. New Permissions (Important)
The following is a list of the permission nodes in version 4.3.0:
You are required to delete the old config.yml to recreate a new one.
You shall save the old one if you have made changes to it.
The New config.yml in version 4.3.0 looks like this:
Code (Text):
#Version 4.3.0
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: "&b&lAdmin360 &f&l>&7 "
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked a player
#BanMessage: Message after you have banned a player
#BanIPMessage: Message after you have banned a player's IP
ItemName: "&a&l<player>"
InventoryName: "&bAdmin360 &fPlayersControl"
TpMessage: "&7You have been teleported to &c<player>&7 !"
KickMessage: "&7You have kicked &c<player>&7 !"
BanMessage: "&7You have banned &c<player>&7 !"
BanIPMessage: "&7You have banned &c<player>&7's IP!"
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
guiname: "&9&lAdmin360 &fPlayers Panel"
guiitem1: "DIAMOND_HELMET"
guiitem2: "PAPER"
guiitem3: "BOOKSHELF"
guiitem4: "BARRIER"
guiitem5: "WRITTEN_BOOK"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Player GUI Items Displayname (/request gui)
guiitem1text: "&6&lHelpme"
guiitem2text: "&b&lStatus"
guiitem3text: "&f&lCount"
guiitem4text: "&c&lCancel"
guiitem5text: "&a&lHelp"
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
adminguiname: "&9&lAdmin360 &fAdmins Panel"
adminguiitem1: "GOLD_HELMET"
adminguiitem2: "DIAMOND_PICKAXE"
adminguiitem3: "GOLD_INGOT"
adminguiitem4: "DIAMOND"
adminguiitem5: "IRON_SPADE"
#DO NOT USE THE SAME ITEM ID WITHIN THE SAME GUI!
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: "&6&lNext"
adminguiitem2text: "&b&lClose"
adminguiitem3text: "&f&lHP Stats"
adminguiitem4text: "&c&lLeaderboard"
adminguiitem5text: "&a&lPurge"
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: "&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!"
helpme_status_inprocess: "&c<player>, &7An admin should be helping with your ticket right now."
helpme_status_waitfeedback: "&c<player>, &7We are awaiting for your generous feedback!"
requestmessage: "&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !"
noadmin: "&7Sorry, &c<player>. &7There are no online staff at the the moment."
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: "&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~"
admin_alreadyattend: "&cSir <player>, &7You have already attended to help a player!"
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: "&cSir <player>, &7You are not attending any requests!"
admin_closedticket: "&cSir <player>, &7You have closed a ticket successfully! "
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: "&c<player>, &7There are no tickets that are awaiting for your feedback at the moment."
thanksforthefeedback: "&7Thank you for your feedback, &c<player>. &7Have a nice day!"
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: "&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! "
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: "&c<player>, &7You do not have any requests yet."
status_adminisattending: "&c<player>, &7An admin is attending your request right now."
status_waitingforfeedback: "&c<player>, &7We are still awaiting for your generous feedback."
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: "&c<player>, &7You do not have any ticket currently. "
cancel_cancancel: "&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!"
cancel_toolate_adminattend: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now."
cancel_toolate_waitingfeedback: "&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!"
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
========================================================
Version 5.0.0 Outlook:
These items would be added in the next update:
1. Report GUI
2. Chinese support (And other languages)
3. MySQL support
4. Allow to change the primary command (Command Aliases)
5. PlayersControl: gui buttons execute a custom command
6. PlayersControl: add a confirm GUI with reasons
(Suggested by sir TheIntelloBox and SuperRonanCraft)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Again, Sorry for making these critical issues.
Admin360-Reloaded Version 4.0.0. Regular Updates
After working for a couples of hours, Reular fix version 4.0.0 is out.
What items have been fixed or added in this update?
1. PlayersControl GUI
This new GUI will list all the online players with their corresponding heads. By hovering the heads, you can be able to view their basic information like Levels, EXP, Food Levels, Health, Gamemode and Flyspeed etc.... (More properties will be added in version 4.5.0. You can suggest some of them xd). And of course, we also allow admins to teleport, kick and ban using this GUI. (I would add BanIP in v4.5.0)
Limitation: It only supports up to 54 players. (That means it can only show up to 54 players online). I am not quite sure what will happen after 54 players, may be some errors occurred or simply the heads are not shown. (I will add multiple pages in v4.5.0)
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2FVUl4Tcp.gif)
2. Permission Nodes Renewal
Because now, Admin360 includes two systems, The Request system and the Players Control System. And we also added /admin360 commands, so we are going to rename some of the permissions. The changes are as following:
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2FLAXaNVw.png)
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2F2GjNGJd.png)
Commands that are related to the Request system (/request) will be longer:
Admin360.admin.request.XXX
Admin360.player.request.XXX
Core commands (/admin360) will be shorter
Admin360.admin.XXX
Admin360.player.XXX
Playercontrols Permission:
Admin360.admin.playerscontrol
We rename come permission nodes and commands just because to make it more structured. We would like to separate the Request System, The Player Control System, and the Core part (System side) to prepare for more feature updates in the future.
3. New Commands
/request info ----> /admin360 info
/request help ----> /admin360 help
/request reload ----> /admin360 reload
Some commands Aliases:
/request help = /admin360 help
/request gui = /ticketgui
/helpme = /request helpme
Commands Aliases would be configurable in the next update v4.5.0
You have to delete the old config.yml and restart the server.
OR, you can simply add the following lines in the version 3.5.0 config file.
The New config.yml in version 4.0.0 looks like this:
========================================================
Version 4.5.0 Outlook:
These items would be added in the next update:
1. Chinese support
2. MySQL support
3. Commands Aliases
(Suggested by sir TheIntelloBox)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update.
After working for a couples of hours, Reular fix version 4.0.0 is out.
What items have been fixed or added in this update?
1. PlayersControl GUI
This new GUI will list all the online players with their corresponding heads. By hovering the heads, you can be able to view their basic information like Levels, EXP, Food Levels, Health, Gamemode and Flyspeed etc.... (More properties will be added in version 4.5.0. You can suggest some of them xd). And of course, we also allow admins to teleport, kick and ban using this GUI. (I would add BanIP in v4.5.0)
Limitation: It only supports up to 54 players. (That means it can only show up to 54 players online). I am not quite sure what will happen after 54 players, may be some errors occurred or simply the heads are not shown. (I will add multiple pages in v4.5.0)
2. Permission Nodes Renewal
Because now, Admin360 includes two systems, The Request system and the Players Control System. And we also added /admin360 commands, so we are going to rename some of the permissions. The changes are as following:
Commands that are related to the Request system (/request) will be longer:
Admin360.admin.request.XXX
Admin360.player.request.XXX
Core commands (/admin360) will be shorter
Admin360.admin.XXX
Admin360.player.XXX
Playercontrols Permission:
Admin360.admin.playerscontrol
We rename come permission nodes and commands just because to make it more structured. We would like to separate the Request System, The Player Control System, and the Core part (System side) to prepare for more feature updates in the future.
3. New Commands
/request info ----> /admin360 info
/request help ----> /admin360 help
/request reload ----> /admin360 reload
Some commands Aliases:
/request help = /admin360 help
/request gui = /ticketgui
/helpme = /request helpme
Commands Aliases would be configurable in the next update v4.5.0
You have to delete the old config.yml and restart the server.
OR, you can simply add the following lines in the version 3.5.0 config file.
Code (Text):
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked to a player
#BanMessage: Message after you have banned to a player
ItemName: '&6&l<player>'
InventoryName: '&bAdmin360 &fPlayersControl'
TpMessage: '&7You have been teleported to &c<player>&7!'
KickMessage: '&7You have kicked &c<player>&7!'
BanMessage: '&7You have banned &c<player>&7!'
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked to a player
#BanMessage: Message after you have banned to a player
ItemName: '&6&l<player>'
InventoryName: '&bAdmin360 &fPlayersControl'
TpMessage: '&7You have been teleported to &c<player>&7!'
KickMessage: '&7You have kicked &c<player>&7!'
BanMessage: '&7You have banned &c<player>&7!'
#=======================================
The New config.yml in version 4.0.0 looks like this:
Code (Text):
#Version 4.0.0
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked to a player
#BanMessage: Message after you have banned to a player
ItemName: '&6&l<player>'
InventoryName: '&bAdmin360 &fPlayersControl'
TpMessage: '&7You have been teleported to &c<player>&7!'
KickMessage: '&7You have kicked &c<player>&7!'
BanMessage: '&7You have banned &c<player>&7!'
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme'
guiitem2text: '&b&lStatus'
guiitem3text: '&f&lCount'
guiitem4text: '&c&lCancel'
guiitem5text: '&a&lHelp'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext'
adminguiitem2text: '&b&lClose'
adminguiitem3text: '&f&lHP Stats'
adminguiitem4text: '&c&lLeaderboard'
adminguiitem5text: '&a&lPurge'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&c<player>, &7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&c<player>, &7We are awaiting for your generous feedback!'
requestmessage: '&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, &c<player>. &7There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&cSir <player>, &7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&cSir <player>, &7You are not attending any requests!'
admin_closedticket: '&cSir <player>, &7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&c<player>, &7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, &c<player>. &7Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&c<player>, &7You do not have any requests yet.'
status_adminisattending: '&c<player>, &7An admin is attending your request right now.'
status_waitingforfeedback: '&c<player>, &7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&c<player>, &7You do not have any ticket currently. '
cancel_cancancel: '&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#PlayersControl GUI (/playerscontrol)
#ItemName: Format for the name of the skull
#TpMessage: Message after you have teleported to a player
#KickMessage: Message after you have kicked to a player
#BanMessage: Message after you have banned to a player
ItemName: '&6&l<player>'
InventoryName: '&bAdmin360 &fPlayersControl'
TpMessage: '&7You have been teleported to &c<player>&7!'
KickMessage: '&7You have kicked &c<player>&7!'
BanMessage: '&7You have banned &c<player>&7!'
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme'
guiitem2text: '&b&lStatus'
guiitem3text: '&f&lCount'
guiitem4text: '&c&lCancel'
guiitem5text: '&a&lHelp'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext'
adminguiitem2text: '&b&lClose'
adminguiitem3text: '&f&lHP Stats'
adminguiitem4text: '&c&lLeaderboard'
adminguiitem5text: '&a&lPurge'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&c<player>, &7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&c<player>, &7We are awaiting for your generous feedback!'
requestmessage: '&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, &c<player>. &7There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&cSir <player>, &7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&cSir <player>, &7You are not attending any requests!'
admin_closedticket: '&cSir <player>, &7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&c<player>, &7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, &c<player>. &7Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&c<player>, &7You do not have any requests yet.'
status_adminisattending: '&c<player>, &7An admin is attending your request right now.'
status_waitingforfeedback: '&c<player>, &7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&c<player>, &7You do not have any ticket currently. '
cancel_cancancel: '&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
========================================================
Version 4.5.0 Outlook:
These items would be added in the next update:
1. Chinese support
2. MySQL support
3. Commands Aliases
(Suggested by sir TheIntelloBox)
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update.
Admin360-Reloaded Version 3.5.0. Urgent Fix
Please UPDATE IMMEDIATELY!. Serious Bugs Fixed
After working for a couples of hours, Urgent fix version 3.5.0 is out.
Please update immediately to fix the critical Bugs:
(Sorry for the late updates. We have already tried our best to publish this urgent update pack)
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved problems that all players cannot get anything from the chest with the "Fail1" error message. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
B. Status Cases Error. The Status message doesn't show up in some cases. It has been fixed as well.
C. Resolved problems that players cannot click the items in /request gui or /request admingui.
These are the critical bugs that we have found. We are really sorry to cause these kinds of issues. Please update the plugins so that these kinds of bugs would not happen again.
2. Reload commands added (/request reload)
To reload the config files
Permission Node: Admin360.admin.reload
Global Permission: Admin360.admin.*
3. As you wish, The "<player>" placeholder
Add the <player> placeholder anywhere in the message section of the config file would show up the name of the players.
It is optional to recreate the new config file as nothing is changed about the structure of the file.
If you recreate the config file, you would see some new placeholder "<player>"
The New config.yml in version 3.5.0 looks like this:
========================================================
Version 4.0.0 Outlook:
These items would be added in the next update:
1. PlayersControl GUI
2. Permissions and Command Renewal
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Again, Sorry for making these critical issues.
Please UPDATE IMMEDIATELY!. Serious Bugs Fixed
After working for a couples of hours, Urgent fix version 3.5.0 is out.
Please update immediately to fix the critical Bugs:
(Sorry for the late updates. We have already tried our best to publish this urgent update pack)
What items have been fixed or added in this update?
1. Fixed Critical Bugs
A. Resolved problems that all players cannot get anything from the chest with the "Fail1" error message. We are very sorry for that. It is all our fault. We have just realized this problem and we are very sorry to bother you and your players.......
B. Status Cases Error. The Status message doesn't show up in some cases. It has been fixed as well.
C. Resolved problems that players cannot click the items in /request gui or /request admingui.
These are the critical bugs that we have found. We are really sorry to cause these kinds of issues. Please update the plugins so that these kinds of bugs would not happen again.
2. Reload commands added (/request reload)
To reload the config files
Permission Node: Admin360.admin.reload
Global Permission: Admin360.admin.*
3. As you wish, The "<player>" placeholder
Add the <player> placeholder anywhere in the message section of the config file would show up the name of the players.
It is optional to recreate the new config file as nothing is changed about the structure of the file.
If you recreate the config file, you would see some new placeholder "<player>"
The New config.yml in version 3.5.0 looks like this:
Code (Text):
#Version 3.5.0
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&c<player>, &7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&c<player>, &7We are awaiting for your generous feedback!'
requestmessage: '&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, &c<player>. &7There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&cSir <player>, &7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&cSir <player>, &7You are not attending any requests!'
admin_closedticket: '&cSir <player>, &7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&c<player>, &7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, &c<player>. &7Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&c<player>, &7You do not have any requests yet.'
status_adminisattending: '&c<player>, &7An admin is attending your request right now.'
status_waitingforfeedback: '&c<player>, &7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&c<player>, &7You do not have any ticket currently. '
cancel_cancancel: '&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&c<player>, &7We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&c<player>, &7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&c<player>, &7We are awaiting for your generous feedback!'
requestmessage: '&c<player>, &7Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, &c<player>. &7There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&cSir <player>, &7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&cSir <player>, &7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&cSir <player>, &7You are not attending any requests!'
admin_closedticket: '&cSir <player>, &7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to give a feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&c<player>, &7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, &c<player>. &7Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&c<player>, &7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&c<player>, &7You do not have any requests yet.'
status_adminisattending: '&c<player>, &7An admin is attending your request right now.'
status_waitingforfeedback: '&c<player>, &7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&c<player>, &7You do not have any ticket currently. '
cancel_cancancel: '&c<player>, &7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, &c<player>. &7It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
========================================================
Version 4.0.0 Outlook:
These items would be added in the next update:
1. PlayersControl GUI
2. Permissions and Command Renewal
If you have encountered any kinds of problems, Please contact us immediately and we would immediately make an urgent update. Again, Sorry for making these critical issues.
Before updating, Please delete the old config.yml first!!!!!!!
I have to reupload this resources because i set the version wrongly in the thread. Sorry to bother you. It is my fault
Features:
1. New GUI with new options in config.yml
2. Bug fixed (Including permission nodes and /request help wrong messages)
If you have set something in the old config.yml file, please save a copy so that you can copy part of them back to the new config file.
The new config.yml in version 3.0.0 looks like this: (Added section for GUI)
If you insist to keep the old config.yml file, Add the following lines in the old config file: (ONLY FOR VERSION 2.0.0 upgrading to VERSION 3.0.0)
And of course, here are some screenshots about the GUI. You can set the Items, DisplayName and the GUI Name in the config file.
![[IMG]](/proxy/image?url=http%3A%2F%2Fi.imgur.com%2Fdd977pq.gif)
I have to reupload this resources because i set the version wrongly in the thread. Sorry to bother you. It is my fault
Features:
1. New GUI with new options in config.yml
2. Bug fixed (Including permission nodes and /request help wrong messages)
If you have set something in the old config.yml file, please save a copy so that you can copy part of them back to the new config file.
The new config.yml in version 3.0.0 looks like this: (Added section for GUI)
Code (Text):
#Version 3.0.0
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&7Sir/Madam, We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&7We are awaiting for your generous feedback!'
requestmessage: '&7Sir/Madam, Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, Sir/Madam. There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&7You are not attending any requests!'
admin_closedticket: '&7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, Sir/Madam. Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&7You do not have any requests yet.'
status_adminisattending: '&7Sir/Madam, An admin is attending your request right now.'
status_waitingforfeedback: '&7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&7Sir/Madam, You do not have any ticket currently. '
cancel_cancancel: '&7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
#Admin360-Reloaded is maintained by Dennie, Jerry and Thomas from Hong Kong.
#=======================================
#Feedback Reminder
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#=======================================
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 5 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
#Case5 (noadmin) : There is no online admin lol....
helpme_status_waiting: '&7Sir/Madam, We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&7We are awaiting for your generous feedback!'
requestmessage: '&7Sir/Madam, Thanks for opening a ticket. We are more than happy to help you soon :) !'
noadmin: '&7Sorry, Sir/Madam. There are no online staff at the the moment.'
#=======================================
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&7You have already attended to help a player!'
#=======================================
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&7You are not attending any requests!'
admin_closedticket: '&7You have closed a ticket successfully! '
#=======================================
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, Sir/Madam. Have a nice day!'
#=======================================
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&7Your constructive feedbacks would be our motivation to make a better server! '
#=======================================
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&7You do not have any requests yet.'
status_adminisattending: '&7Sir/Madam, An admin is attending your request right now.'
status_waitingforfeedback: '&7We are still awaiting for your generous feedback.'
#=======================================
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&7Sir/Madam, You do not have any ticket currently. '
cancel_cancancel: '&7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#=======================================
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
If you insist to keep the old config.yml file, Add the following lines in the old config file: (ONLY FOR VERSION 2.0.0 upgrading to VERSION 3.0.0)
Code (Text):
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
#Player GUI Name and Items ID (/request gui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
guiname: '&9&lAdmin360 &fPlayers Panel'
guiitem1: 'DIAMOND_HELMET'
guiitem2: 'PAPER'
guiitem3: 'BOOKSHELF'
guiitem4: 'BARRIER'
guiitem5: 'WRITTEN_BOOK'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Player GUI Items Displayname (/request gui)
guiitem1text: '&6&lHelpme&7: Open a Ticket'
guiitem2text: '&b&lStatus&7: Ticket Status'
guiitem3text: '&f&lCount&7: Global Stats'
guiitem4text: '&c&lCancel&7: Cancel Request'
guiitem5text: '&a&lHelp&7: Commands List'
#=======================================
#Admin GUI Name and Items ID (/request admingui)
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
adminguiname: '&9&lAdmin360 &fAdmins Panel'
adminguiitem1: 'GOLD_HELMET'
adminguiitem2: 'DIAMOND_PICKAXE'
adminguiitem3: 'GOLD_INGOT'
adminguiitem4: 'DIAMOND'
adminguiitem5: 'IRON_SPADE'
#DO NOT USE THE SAME ITEM ID FOR BOTH PLAYER AND ADMIN GUI!
#THIS WILL BE FIXED IN THE NEXT UPDATE
#Admin GUI Items Displayname (/request admingui)
adminguiitem1text: '&6&lNext&7: Next Request'
adminguiitem2text: '&b&lClose&7: Close a Ticket'
adminguiitem3text: '&f&lHP Stats&7: Honor Points Stats'
adminguiitem4text: '&c&lLeaderboard&7: Top Admin List'
adminguiitem5text: '&a&lPurge&7: Remove all Tickets'
#=======================================
And of course, here are some screenshots about the GUI. You can set the Items, DisplayName and the GUI Name in the config file.
As you wish xd, 98% of the messages are now configurable in the config.yml. Please delete the old config.yml before updating.
Procedures to update:
1. Delete the old config.yml
2. delete the old .jar
3. Add the new .jar
4. Restart the server
5. Edit the config.yml to your desirable settings (OPTIONAL)
6. Restart the server (Highly recommended) or Reload the server (It is risky)
This is how the new config file looks like:
Procedures to update:
1. Delete the old config.yml
2. delete the old .jar
3. Add the new .jar
4. Restart the server
5. Edit the config.yml to your desirable settings (OPTIONAL)
6. Restart the server (Highly recommended) or Reload the server (It is risky)
This is how the new config file looks like:
Code (Text):
#Version 2.0.0
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#Message when no admin is online
noadmin: '&7Sorry, Sir/Madam. There are no staff onlining at the the moment.'
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 4 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
helpme_status_waiting: '&7Sir/Madam, We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&7We are awaiting for your generous feedback!'
requestmessage: '&7Sir/Madam, Thanks for opening a ticket. We are more than happy to help you soon :) !'
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&7You have already attended to help a player!'
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&7You are not attending any requests!'
admin_closedticket: '&7You have closed a ticket successfully! '
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, Sir/Madam. Have a nice day!'
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&7Your constructive feedbacks would be our motivation to make a better server! '
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&7You do not have any requests yet.'
status_adminisattending: '&7Sir/Madam, An admin is attending your request right now.'
status_waitingforfeedback: '&7We are still awaiting for your generous feedback.'
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&7Sir/Madam, You do not have any ticket currently. '
cancel_cancancel: '&7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
#Set it to true if you would like the players to be reminded to
#give a feedback right after the ticket was closed.
showReminder: true
#The time interval in seconds to remind the players to do a
#feedback in case they forget. (This would be a bit annoying)
reminderFrequency: 20
#Prefix: Set the prefix of the message
prefix: '&b&lAdmin360 &f&l>&7 '
#Message when no admin is online
noadmin: '&7Sorry, Sir/Madam. There are no staff onlining at the the moment.'
#Helpme Section (/helpme or /request helpme)
#When players do /helpme, it would show 4 types of messages.
#Case1 (helpme_status_waiting) : You have already opened a ticket. The command takes no effect.
#Case2 (helpme_status_inprocess) : An Admin is helping you. The command takes no effect.
#Case3 (helpme_status_waitfeedback) : An Admin has just closed the ticket, but you have not given a feedback yet. The command takes no effect.
#Case4 (requestmessage) : Neither Case 1 to Case 3. You are allowed to open a ticket.
helpme_status_waiting: '&7Sir/Madam, We already have a pending ticket from you. Please be patient and our staff is going to approach you soon!'
helpme_status_inprocess: '&7An admin should be helping with your ticket right now.'
helpme_status_waitfeedback: '&7We are awaiting for your generous feedback!'
requestmessage: '&7Sir/Madam, Thanks for opening a ticket. We are more than happy to help you soon :) !'
#Next Request Section (/request next)
#When an admin do /request next, it would show 2 types of messages.
#admin_norequestinqueue: No tickets or requests in queue. You can take a rest xd.
#admin_alreadyattend: You are helping a player, but the ticket has not closed yet.
admin_norequestinqueue: '&7There are no tickets remaining at the moment. Take a rest~~'
admin_alreadyattend: '&7You have already attended to help a player!'
#Close Ticket Section (/request close)
#When an admin do /request close, it would show 2 types of messages.
#admin_notattending: You are not attending any tickets. No tickets to be closed.
#admin_closedticket: You have successfully closed the ticket.
admin_notattending: '&7You are not attending any requests!'
admin_closedticket: '&7You have closed a ticket successfully! '
#Feedback Reply Message Section (/request yes or /request no)
#When players do /request yes or /request no in feedback, it would show 2 types of messages.
#noneedtofeedback: There is no need for you to feedback because you did not open a ticket or you have already made a feedback.
#thanksforthefeedback: Thanks for the feedback.
noneedtofeedback: '&7There are no tickets that are awaiting for your feedback at the moment.'
thanksforthefeedback: '&7Thank you for your feedback, Sir/Madam. Have a nice day!'
#Feedback Message Section
#Message when players are asked to give a feedback after the admin has closed the ticket.
giveafeedback: '&7Your constructive feedbacks would be our motivation to make a better server! '
#Status Section (/request status)
#When players do /request status, There are 3 types of messages
#status_norequestyet: You have no tickets or requests opened.
#status_adminisattending: An Admin is helping you currently.
#status_waitingforfeedback: You have not answered the feedback yet.
status_norequestyet: '&7You do not have any requests yet.'
status_adminisattending: '&7Sir/Madam, An admin is attending your request right now.'
status_waitingforfeedback: '&7We are still awaiting for your generous feedback.'
#Cancel Section (/request cancel)
#When players do /request cancel, There are 4 types of messages
#cancel_norequest: You have no tickets or requests opened, thus you can cancel nothing.
#cancel_cancancel: You have cancelled the ticket successfully.
#cancel_toolate_adminattend: You cannot cancel the ticket because an admin is helping you currently.
#cancel_toolate_waitingfeedback: You cannot cancel the ticket because you have to answer the feedback first.
cancel_norequest: '&7Sir/Madam, You do not have any ticket currently. '
cancel_cancancel: '&7Your ticket has been successfully cancelled. Thanks for using the system!'
cancel_toolate_adminattend: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. An admin is going to attend it now.'
cancel_toolate_waitingfeedback: '&7Sorry, Sir/Madam. It would be too late to cancel your ticket now. We are awaiting for your generous feedback!'
#Admin360-Reloaded is maintained by Dennie and Thomas from Hong Kong.
Resource Information
Author:
----------
Total Downloads:
49,501
First Release:
Aug 23, 2016
Last Update:
Jun 22, 2024
Category:
---------------
All-Time Rating:
Find more info at github.com...
22 ratings
Version
-----
Released:
--------------------
Downloads:
------
Version Rating:
----------------------
-- ratings