[Admin360] Added PlayersControl GUI! Renew Permisison nodes and some of the commands.
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)
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!'
#=======================================
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.
========================================================
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.