Sueta

⚡Admin360-Reloaded⚡Manage Real-Time Help Requests! ✅ HEX ✅ R

9.3.0

Redefines Player-Staff Interaction; Fosters Disciplined & Quality Service!

·Plugin
  1. 9.3.0latest9.3.0 - Notification of pending requests for staff on join by @DartanboyJun 22, 2024
    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 · 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/
    9 downloads
  2. 9.2.09.2.0 - Invulnerability support for staff attending tickets by @DartanboyJun 19, 2024
    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 · 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/
    19 downloads
  3. 9.1.0b9.1.0b - Bug fixesMay 6, 2024
    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 · Fixed the error "java.lang.IllegalArgumentException: Illegal group reference: group index is missing" when there is a regex keyword in chat message, e.g., $, \. This release is compatible with any 1.8+ versions and has been tested on servers of 2 different versions: 1.8.8, and 1.20.2. Configurations There are no changes made to config.yml relative to release 9.1.0.
    30 downloads
  4. 9.1.09.1.0 - Major Release (BETA) - A complete overhaul!Sep 4, 2023
    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 · 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. This release is compatible with any 1.8+ versions and has been dry-tested on servers of 2 different versions: 1.8.8, and 1.19.3. 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! Both might suit your needs as well if you also feel the same for Admin360! 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.
    1303 downloads
  5. 8.1.2b8.1.2b - Sub-Release - Fixed forward compatability from 1.8 and onwardsJun 26, 2023
    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.
    135 downloads
  6. 8.1.2Admin360-Reloaded v8.1.2-API17JAVA16 - 1.17 EditionSep 3, 2021
    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! Code (Text): Conversion: #96c3eb → &x&9&6&c&3&e&b Code (Text): e.g. '&x&9&6&c&3&e&bPermission Denied!'
    1695 downloads
  7. 8.1.2-API16JAVA16Admin360-Reloaded v8.1.2-API16JAVA16 - 1.16 EditionSep 3, 2021
    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! Code (Text): Conversion: #96c3eb → &x&9&6&c&3&e&b Code (Text): e.g. '&x&9&6&c&3&e&bPermission Denied!'
    22 downloads
  8. 8.1.1 DEV8.1.1 - Minor Release - MySQL support, redirect / pick / drop ticketsJan 10, 2021
    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
    166 downloads
  9. 8.0.08.0.0 - Major Release - Many new featurresJan 3, 2021
    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
    174 downloads
  10. 7.1.07.1.0 - Minor Release - Config revision, bug fixes, code cleanupMay 12, 2020
    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/
    1606 downloads
  11. 7.0.17.0.1 - Minor Release - Multiple-line messages, minor bug fixed, polished config.ymlMay 31, 2019
    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. 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:
    231 downloads
  12. 7.0.07.0.0 - Major Release - A lot of changesMay 29, 2019
    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. 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
    295 downloads
  13. 5.0.0[Admin360] 1.12.2 Compatability and Urgent fix for Critical BugsNov 6, 2017
    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...... i found a bug that where some staff do /request close there will be a gui for player and then player can take the apple. By sir Silver750 Click to expand... Based on player sides, when the player can't get the apple (I mean, [rarely] the apple cannot be stored into inventory after the case mentioned above), after they press ESC, the dialogue box will be shown in less than a minute (still no apple in inventory, tho), kind of annoying but after several times that happened, it worked normally.By sir RaikenJenova Click to expand... 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 Do this plugin have Chinese lang if not can i translate it? By sir jqsonwang8855 Click to expand... 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... I have bug from Admin360 new update. GUI feedback cant closed. Please fix it .. By sir xHamstersSX Click to expand... 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
    1124 downloads
  14. 4.4.0[Admin360] Now officially compatible with MC 1.11 & New Feedback GUIFeb 26, 2017
    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. I was wondering if it's possible to allow us to change the messages made when people make helpme from the config? The ones that say: "Admin360 > A new request has been created by {player} Admin360 > There are now {number of requests} requests remaining"? I'd like to change some of the text color so it stands out a little more. Suggested by Sir SucceededKiller. Click to expand... 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. 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....
    4391 downloads
  15. 4.3.0[Admin360] Urgent fix for Critical BugsAug 30, 2016
    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. Trying in the most recent update, it turns out for the player's panel, if they do not have a ticket open they can steal the cancel request (barrier) & ticket status (paper) items as much as they want. By sir Xx_Cyborg_xX Click to expand... it would seem my admins are able to remove the items from the gui, they drop when you click the "next" ticket item when there are no tickets pending. and also the "/request next" give an internal error, BUT this only happens when there has never been a ticket made before.By sir SuperRonanCraft Click to expand... 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. i bugged out the plugin by making a ticket my self, not being able to do "/request status" while helping my own ticket, then opening another ticket while i'm helping my ticket, then closing the current ticket, making feedback with "/request no" but showed me "no tickets are awaiting your feedback" and then it just kept spamming to give feedback. By sir SuperRonanCraft Click to expand... 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) could there be a permission to not let my admins kick each other? Cause i'm able to kick and ban my self, and i don't want my admins doing that to other staff members . By sir SuperRonanCraft Click to expand... 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: 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>, &7Y
    1162 downloads
  16. 4.0.0[Admin360] Added PlayersControl GUI! Renew Permisison nodes and some of the commands.Aug 26, 2016
    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 i
    896 downloads
  17. 3.5.0[Admin360] UPDATE IMMEDIATELY! Fixed Critical Bug (Cannot Grab items from Inventory)! Added reload!Aug 25, 2016
    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: 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>,
    966 downloads
  18. 3.0.0 for 1.8, 1.9, 1.10[Admin360] New Inventory GUI for both Players and Admins!Aug 24, 2016
    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) 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. 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
    3787 downloads
  19. 1.8, 1.9, 1.10[Admin360-Reloaded] Added configurable messages in the config file! More screenshotsAug 24, 2016
    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: 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.
    645 downloads
  20. 1.8,1.9,1.10Aug 23, 2016
    294 downloads

Similar projects

Plugin →