⚡Admin360-Reloaded⚡Manage Real-Time Help Requests! ✅ HEX ✅ Ratings ✅ Statistics -----
Redefines Player-Staff Interaction; Fosters Disciplined & Quality Service![Admin360] Now officially compatible with MC 1.11 & New Feedback GUI
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!
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