⚡Admin360-Reloaded⚡Manage Real-Time Help Requests! ✅ HEX ✅ Ratings ✅ Statistics -----
Redefines Player-Staff Interaction; Fosters Disciplined & Quality Service![Admin360] New Inventory GUI for both Players and Admins!
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.
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