टेक्स्ट की तुलना करें

दो टेक्स्ट फ़ाइलों के बीच अंतर ढूंढें

Real-time diff

Unified diff

Collapse lines

Highlight change

Syntax highlighting

टूल्स

Diffchecker Desktop The most secure way to run Diffchecker. Get the Diffchecker Desktop app: your diffs never leave your computer!Get Desktop

Admin360-Reloaded 7.1.0 VS 8.0.0

Created 4 years agoDiff never expires

353 removals

402 lines

424 additions

472 lines

############################################################

# +------------------------------------------------------+ #

# | Notes | #

# +------------------------------------------------------+ #

############################################################

#Version 7.1.0

# Version 8.0.0

#Tested on Spigot 1.8.8, 1.12.2, 1.13.2, 1.14.4, 1.15.2.

# Tested on Spigot 1.8.8, 1.12.2, 1.13.2, 1.14.4, 1.15.2, 1.16.4.

#Config and Plugin version.

# Config version = Plugin version.

#Do not change this unless you know what you are doing.

# Do not change this unless you know what you're doing.

version: '7.1.0'

# This is for the plugin to check whether we should generate a new config for you.

version: '8.0.0'

#Whenever there is an update available, read the upgrade procedures as instructed on our spigot project page.

# Whenever there's an update available, read the upgrade procedures as instructed on our spigot project page.

#If there are any changes made to this config, for example, an addition of several configurable parameters,

# If there're any changes made to this config, for example, if we've added several new settings or messages,

#then you may have to manually delete this file and let a new one regenerate. This would be the quickest way

# you may have to compare the changes of the new and old config. And, it takes time to apply your old settings

#to ensure proper functioning of the plugin.

# especially when the update is big.

#Since version 7.1.0, we will auto-rename the old config file into "config_old.yml" on server restart.

# Since version 7.1.0, the plugin will auto-rename the old config file into "config_old.yml" on server restart.

#You can then spend some time to compare the changes and apply your old settings bit by bit.

# This is to make sure that everything works even if we reworked the config file (which is something I always do).

#Should you have any problems, please let us know. by Dennie.

# But remember to delete the "config_old.yml" after you've migrated all the changes.

# If not, it may break this auto-rename feature on future updates.

#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/

# As you can see, the comments can be lengthy because we want to explain everything to you.

#Contributors: Dennie, PPT_T, vidhu1911

# If you really spend time read through this, then you will know how the plugin works.

# If you want to disable some messages, simply make it an empty line using ''.

# All default messages contain all the placeholders that can be used. You can remove it or dupliciate it.

# However, placeholders will only work in that particular message.

# We welcome users to make translation of this config. Contact us so that we can put your translation official.

# Project: https://www.spigotmc.org/resources/admin360-reloaded.28285/

# Support: https://www.spigotmc.org/members/jerryui.139798/

# Authors: Dennie, PPT_T, vidhu1911

############################################################

# +------------------------------------------------------+ #

# | Basic (perms, syntax, help, reload) | #

# +------------------------------------------------------+ #

############################################################

insufficient-permission: '&b&lAdmin360 &3» &7Access denied. You do not have permission to use this command.'

no-permission: '&f[&6ADMIN360&f] &c&nAccess Denied&7 You do not have permission to use this command.'

incorrect-syntax: '&b&lAdmin360 &3» &7Incorrect syntax. Type &b/admin360 &7to display a list of commands.'

incorrect-syntax: '&f[&6ADMIN360&f] &c&nIncorrect Syntax&7 Use &6/admin360 &7to display a list of commands.'

not-player-warning: '&b&lAdmin360 &3» &7Commands of Admin360 are all player-only commands.'

is-player-check: '&f[&6ADMIN360&f] &c&nAccess Denied&7 This is a player-only command.'

reload-message: '&b&lAdmin360 &3» &7The config file has been reloaded successfully.'

reload-message: '&f[&6ADMIN360&f] &7The config file has been reloaded successfully.'

#Help Section: Player Commands

# Help Section: Player Commands

#This option supports multiple lines.

# This message supports multiple lines.

#[]: Optional <>: Compulsory

command-list-player:

commands-player:

- ''

- '&7&m------------&r &6ADMIN360 &7&m------------'

- '&6Usage&f:'

- '&6/ticket create [details] &f- &7Open a ticket.'

- ''

- '&6/ticket cancel &f- &7Cancel your ticket.'

- '&b/ticket &ecreate [details] &fOpen a support ticket.'

- '&6/ticket status &f- &7Query ticket status.'

- '&b/ticket &ecancel &7Cancel your ticket.'

- '&6/ticket stats &f- &7View ticket statistics.'

- '&b/ticket &estatus &fView your ticket status.'

- '&6/ticket help &f- &7Print command list.'

- '&b/ticket &estats &7Display ticket statistics.'

- '&6/admin360 &f- &7Display plugin info.'

- '&b/admin360 &einfo &fKnow more about Admin360.'

- '&7*&fParameters: [Optional] <Compulsory>'

- ''

- '&7&m---------------------------------'

- ''

#Help Section: Staff Commands

# Help Section: Staff Commands

#This option supports multiple lines.

# This message supports multiple lines.

#[]: Optional <>: Compulsory

command-list-staff:

commands-staff:

- ''

- '&7&m------------&r &6ADMIN360 &7&m------------'

- '&cUsage&f:'

- '&6/ticket next &f- &7Proceed to the next ticket.'

- ''

- '&6/ticket tp &f- &7Teleport to target player.'

- '&b/ticket &enext &fProceed to the next ticket.'

- '&6/ticket info &f- &7View the ticket details.'

- '&b/ticket &eclose &7Declare completion of a ticket.'

- '&6/ticket close &f- &7Close/complete a ticket.'

- '&b/ticket &epurge &fPurge all pending tickets.'

- '&6/ticket purge &f- &7Purge all queuing tickets.'

- '&b/ticket &edelete <name> &7Forcibly delete a ticket.'

- '&6/ticket delete <name> &f- &7Delete a ticket.'

- '&b/ticket &ehpstats [name] &fDisplay honor points statistics.'

- '&6/ticket history [#] &f- &7View ticket history.'

- '&b/ticket &ehptop [#] &7Display honor points leaderboard.'

- '&6/ticket hpstats [name] &f- &7View staff stats.'

- '&b/ticket &ehpreset <name> &fReset honor points of a staff.'

- '&6/ticket hptop [#] &f- &7View staff leaderboard.'

- '&b/admin360 &ereload &7Reload the plugin config file.'

- '&6/ticket hpreset <name> &f- &7Reset staff stats.'

- ''

- '&6/admin360 reload &f- &7Reload the config file.'

- '&7*&fParameters: [Optional] <Compulsory>'

- '&7&m---------------------------------'

- ''

############################################################

# +------------------------------------------------------+ #

# | Creating Tickets (/ticket create) | #

# +------------------------------------------------------+ #

############################################################

#/ticket create [details] : Open a ticket with or without a description.

# /ticket create [details] : Open a ticket with or without a description (optional) of the case.

#In this section, you can modify settings and configure messages that are related to tickets creation (/ticket create).

# In this section, you can modify the settings and messages that are related to "/ticket create".

#This is a player command which requires the permission node "admin360.player.basic" to function.

# This is a player command which requires the permission "admin360.player.basic".

# 5 Circumstances:

# create-failed-no-staff : Creation aborted because there are no staff online.

# 1 (create-failed-in-queue) : You have already submitted a request. You cannot create a new ticket.

# create-failed-in-queue : Creation aborted because you already have a ticket opened.

# 2 (create-failed-in-progress) : There is a staff member handling your case at the moment. You cannot create a new ticket.

# create-failed-in-progress : Creation aborted because a staff is attending your help-request.

# 3 (create-failed-require-feedback) : You still haven't provided a valid feedback. You cannot create a new ticket.

# create-failed-require-feedback : Creation aborted because you still haven't submitted a feedback for your previous ticket.

# 4 (create-failed-staff-ticket) : You are a staff member. You are not allowed to create a ticket to prevent boosting.

# create-failed-anti-exploit : Creation aborted because you are a staff member. Staff is banned from ticket creation to prevent boosting.

# 5 (new-ticket-created) : A new ticket is created and is immediately put in the next position of the queue by default.

#*boosting: self-ticketing exploit.

# create-succeeded : Creation succeeded. Your ticket has been put in the next position of the queue.

#After a ticket is created, available staff members (with permission node "admin360.staff.basic") will be notified.

# After a ticket is opened, your staff (with permission "admin360.staff.basic") will be notified.

#If there is a description (i.e. reason) specified by the user who opened the ticket, staff will be able to see that.

# Command cooldown to avoid spammming issues.

# The unit of cooldown-timer is seconds.

use-cooldown: true

cooldown-timer: 60

cooldown-message: '&f[&6ADMIN360&f] &7Please wait for &6<SECONDSLEFT>s&7 before opening another ticket.'

#Preliminary fail-safe check: Can be turned off. Check if any staff members are currently available.

# Check if any staff members are currently available.

#If this is set to true, players will not be allowed to create any new tickets if there are no staff in the server.

# If this is set to true, players will not be allowed to open a new ticket if there are no staff in the server.

#How do we determine between players and staff? Staff are those who have the permission "admin360.staff.basic".

# How do we determine between a player and a staff? Staff are those who have the permission "admin360.staff.basic".

staff-online-required: true

no-staff-online: '&b&lAdmin360 &3» &7You cannot open a ticket when there are no staff members available.'

create-failed-no-staff: '&f[&6ADMIN360&f] &c&nCreate Failed&7 There are no staff currently available.'

create-failed-in-queue: '&b&lAdmin360 &3» &7You have already opened a ticket.'

create-failed-in-queue: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You already have a ticket opened. (&fTips: &6/ticket status&7)'

create-failed-in-progress: '&b&lAdmin360 &3» &7A staff member is now reviewing your request.'

create-failed-in-progress: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You have another ticket in progress.(&fTips: &6/ticket status&7)'

create-failed-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

create-failed-require-feedback: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'

create-failed-staff-ticket: '&b&lAdmin360 &3» &7To prevent boosting, staff members are not allowed to open a ticket.'

create-failed-anti-exploit: '&f[&6ADMIN360&f] &c&nCreate Failed&7 Members of the staff team are not allowed to open a ticket to avoid exploits.'

new-ticket-created: '&b&lAdmin360 &3» &7You have opened a ticket (Position: &c<queue>&7). Use &b/ticket status &7to check your progress.'

#Additional feature: Trigger custom command? Default example using title-manager.

# This message supports multiple lines.

#Change this to true if you want to use this option.

create-succeeded:

new-ticket-use-command: false

- '&f[&6ADMIN360&f] &7You have opened a ticket (&fPosition: &c<POSITION>&7). Use &6/ticket status &7to check your progress.'

new-ticket-command: 'tm msg <player> &b\n&bTicket Created &7(&fPosition: &c<queue>&7)'

# Do you want to run a custom command right after a ticket is opened? Default example using title-manager.

# Change this to true if you want to use this option.

ticket-created-trigger-custom-command: false

ticket-created-custom-command: 'tm msg <PLAYERNAME> &b\n&6Ticket Created &7(&fPosition: &6<POSITION>&7)'

#This option supports multiple lines.

# Notify your staff when there is a ticket created.

notify-staff-new-ticket:

# This message supports multiple lines.

- ''

ticket-created-notify-staff:

- '&7&m-----------&b &aNew Ticket &7&m-----------'

- ''

- '&f[&6ADMIN360&f] &6<PLAYERNAME> &copened a &a&lNEW &cticket.'

- ' &a<player> &fopened a ticket.'

- '&f[&6ADMIN360&f] &cDetails: &f<DETAILS>'

- ' &7(&e<queue> &fticket(s) remaining&7)'

- '&f[&6ADMIN360&f] &7(&e<TICKETSREMAIN> &fticket(s) remaining&7)'

- ''

- '&7&m--------------------------------'

- ''

#This option supports multiple lines.

notify-staff-new-ticket-with-reason:

- ''

############################################################

- '&7&m-----------&b &aNew Ticket &7&m-----------'

# +------------------------------------------------------+ #

- ''

# | Cancelling Tickets (/ticket cancel) | #

- ' &a<player> &fopened a ticket.'

# +------------------------------------------------------+ #

- ' &aDetails: &f<reason>'

############################################################

- ' &7(&e<queue> &fticket(s) remaining&7)'

- ''

# /ticket cancel: Cancel your submitted request.

- '&7&m--------------------------------'

# In this section, you can modify the messages that are related to "/ticket cancel".

- ''

# This is a player command which requires the permission "admin360.player.basic".

# cancel-failed-no-ticket : You didn't opened any request. There are no request for you to cancel.

# cancel-failed-in-progress : You can't cancel your request because a staff is now attending it.

# cancel-failed-attending : You are a staff and you are processing a ticket. You cannot cancel any tickets.

# cancel-failed-require-feedback : You cannot cancel your request because you still haven't submitted a feedback for your previous ticket.

# cancel-succeeded : You have cancelled your submitted request successfully.

cancel-failed-no-ticket: '&f[&6ADMIN360&f] &c&nCancel Failed&7 Do you need help? (&fTips: &6/ticket create [details]&7)'

cancel-failed-in-progress: '&f[&6ADMIN360&f] &c&nCancel Failed&7 A staff is attending your help-request. (&fTips: &6/ticket status&7)'

cancel-failed-attending: '&f[&6ADMIN360&f] &c&nCancel Failed&7 Members of the staff team do not need this function.'

cancel-failed-require-feedback: '&f[&6ADMIN360&f] &c&nCancel Failed&7 You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'

cancel-succeeded: '&f[&6ADMIN360&f] &7You have removed your ticket from the queue successfully.'

############################################################

# +------------------------------------------------------+ #

# | Processing Tickets (/ticket next) | #

# | Tickets Status (/ticket status) | #

# +------------------------------------------------------+ #

############################################################

#/ticket next: Proceed to the next help-request.

# /ticket status: Query the current status of your ticket.

#In this section, you can modify settings and configure messages that are related to tickets processing (/ticket next).

# In this section, you can modify the messages that are related to "/ticket status".

#This is a staff command which requires the permission node "admin360.staff.basic" to function.

# This is a player command which requires the permission "admin360.player.status".

# 4 Circumstances:

# status-no-ticket : You didn't submit any help-requests. You can open one.

# 1 (next-failed-no-ticket) : There are no tickets in the queue. You cannot process the next ticket.

# status-in-queue : You already have a ticket opened, which is still in the queue at the moment.

# 2 (next-failed-attending) : You are still processing an unclosed case. You cannot process the next ticket.

# status-in-progress : A staff is attending your request at the moment.

# 3 (next-failed-self-ticket) : You are a staff member and you are not allowed to process your own requests.

# status-attending : You are a staff and you are currently attending a case.

# 4 succeeded : You will be teleported to the target player by Admin360. The user and staff will be notified.

# status-require-feedback : Your ticket is closed but you still haven't give us a feedback.

#Please note that staff members should not be allowed to boost tickets.

status-no-ticket: '&f[&6ADMIN360&f] &7Do you need help? (&fTips: &6/ticket create [details]&7)'

#You may negate the permission for /ticket create "-admin360.player.basic" for your staff permission group(s),

status-in-queue: '&f[&6ADMIN360&f] &7Your ticket is now in position &6<POSITION> &7of the queue.'

#so that they will not be able to exploit any potential loopholes.

status-in-progress: '&f[&6ADMIN360&f] &7Your ticket is now in progress. A staff will contact you soon.'

#But it is fine if you do not do so. We have hard-coded these restrictions into the plugin ever since v7.0.2.

status-attending: '&f[&6ADMIN360&f] &7You are attending a help-request at the moment. (&fTips: &6/ticket info&7)'

#Now, by default, staff members are not even able to to do /ticket create in the first place,

status-require-feedback: '&f[&6ADMIN360&f] &7You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'

#which should be provided sufficient anti-exploit protection.

#Staff members in the server (with permission "admin360.staff.basic") will be notified when a ticket status is changed

#from pending (in queue) to processing (in progress).

#The user who created the ticket will be notified as well.

next-failed-no-ticket: '&b&lAdmin360 &3» &7There are no pending tickets at the moment.'

############################################################

next-failed-attending: '&b&lAdmin360 &3» &7Before proceeding to the next request, you have to complete the current one first.'

# +------------------------------------------------------+ #

next-failed-self-ticket: '&b&lAdmin360 &3» &7You are not allowed to process requests that are submitted by yourself.'

# | Attending Tickets (/ticket next) | #

# +------------------------------------------------------+ #

############################################################

#This option supports multiple lines.

# /ticket next: Proceed to the next help-request.

notify-user-ticket-handling:

# In this section, you can modify the settings and messages that are related to "/ticket next".

- '&b&lAdmin360 &3» &c<staff> &7is now reviewing your request.'

# This is a staff command which requires the permission 'admin360.staff.basic".

#Additional feature: Trigger custom command? Default example using title-manager.

# next-failed-no-ticket : Currently, there are no tickets in the queue so you cannot proceed.

#Change this to true if you want to use this option.

# next-failed-attending : You are still attending a help-request. That's why you can't proceed to the next ticket.

notify-user-ticket-handling-use-command: false

# If "/ticket next" succeeded, you will be teleported to the target player by Admin360 (which can be disabled).

notify-user-ticket-handling-command: 'tm msg <player> &b\n&c<staff> &bis now reviewing your request.'

#This option supports multiple lines.

# Your staff in the server (with permission "admin360.staff.basic") will be notified when the status of a ticket is

notify-staff-ticket-handling:

# changed from pending (in queue) to processing (in progress). The player who created the ticket will also be notified.

- ''

- '&7&m----------&b &dStaff Activity &7&m----------'

next-failed-no-ticket: '&f[&6ADMIN360&f] &c&nNext Failed&7 There are no unattended tickets at the moment.'

- ''

next-failed-attending: '&f[&6ADMIN360&f] &c&nNext Failed&7 You have to close your current ticket before attending the next one.'

- ' &d<staff> &fis now processing'

- ' &d<player>&f''s ticket.'

# Do you want Admin360 to teleport your staff to the target player by default?

- ' &7(&e<tickets> &fticket(s) remaining&7)'

# Change this to false if you want to disable this option.

- ''

use-auto-teleport: true

- '&7&m--------------------------------'

- ''

# This message supports multiple lines.

ticket-in-progress-notify-player:

- '&f[&6ADMIN360&f] &6<ADMINNAME> &7is now reviewing your help-request.'

# Do you want to run a custom command right after a ticket changed its status? Default example using title-manager.

# Change this to true if you want to use this option.

ticket-in-progress-trigger-custom-command: false

ticket-in-progress-custom-command: 'tm msg <PLAYERNAME> &b\n&6<ADMINNAME> &fis now reviewing your request.'

# This message supports multiple lines.

ticket-in-progress-notify-staff:

- ''

- '&f[&6ADMIN360&f] &6<ADMINNAME> &cis now processing &6<PLAYERNAME>&c''s ticket.'

- '&f[&6ADMIN360&f] &7(&e<TICKETSREMAIN> &fticket(s) remaining&7)'

- ''

Text moved from lines 248-256

############################################################

# +------------------------------------------------------+ #

# | Teleport (/ticket tp) | #

# +------------------------------------------------------+ #

############################################################

# /ticket tp: It allows you to teleport to the player who opened the ticket that you are processing now.

# In this section, you can modify the messages that are related to "/ticket tp".

# This is a staff command which requires the permission "admin360.staff.tp".

teleport-failed: '&f[&6ADMIN360&f] &c&nTeleport Failed&7 You cannot use this function at the moment.'

teleport-succeeded: '&f[&6ADMIN360&f] &7You have been teleported to &6<PLAYERNAME>&7.'

############################################################

# +------------------------------------------------------+ #

# | View-Info (/ticket info) | #

# +------------------------------------------------------+ #

############################################################

# /ticket info: Remember "/ticket create [details]"? This command enables you to read that details again

# if you are processing that ticket (in case you forgot).

# In this section, you can modify the messages that are related to "/ticket info".

# This is a staff command which requires the permission "admin360.staff.info".

info-failed: '&f[&6ADMIN360&f] &c&nView-Info Failed&7 You cannot use this function at the moment.'

# This message supports multiple lines.

info-message:

- ''

- '&f[&6ADMIN360&f] &6Name: &f<PLAYERNAME>'

- '&f[&6ADMIN360&f] &6Details: &f<DETAILS>'

- '&f[&6ADMIN360&f] &6Time: &f<TIME>'

- ''

############################################################

# +------------------------------------------------------+ #

# | Closing Tickets (/ticket close) | #

# +------------------------------------------------------+ #

############################################################

#/ticket close: Close a ticket and mark it as completed.

# /ticket close: Close a ticket and mark it as completed.

#In this section, you can configure messages that are related to tickets closure (/ticket close).

# In this section, you can modify the messages that are related to "/ticket close".

#This is a staff command which requires the permission node "admin360.staff.basic" to function.

# This is a staff command which requires the permission "admin360.staff.basic".

# 2 Circumstances:

# 1 (close-failed-not-attending) : You are not processing any tickets at the moment so no request can be closed.

# 2 (close-succeeded-ticket-closed) : You have closed the ticket you are handling at the moment.

close-failed-not-attending: '&b&lAdmin360 &3» &7You are not processing any requests at the moment.'

close-failed: '&f[&6ADMIN360&f] &c&nClose Failed&7 You are not attending any request at the moment.'

close-succeeded-ticket-closed: '&b&lAdmin360 &3» &7This case is now closed.'

close-succeeded: '&f[&6ADMIN360&f] &7You have closed this ticket successfully.'

############################################################

# +------------------------------------------------------+ #

# | Giving Feedback (/ticket yes or no) | #

# +------------------------------------------------------+ #

############################################################

#/ticket yes, /ticket no: Providing service feedback. /ticket yes: satisfactory; /ticket no: poor experience.

# /ticket yes, /ticket no: After a ticket is closed, your player will be asked to rate the service.

#In this section, you can modify settings and configure messages that are related to feedback (/ticket yes and /ticket no).

# They can upvote or downvote. /ticket yes: upvote; /ticket no: downvote.

#This is a player command which requires the permission node "admin360.player.basic" to function.

# In this section, you can modify the settings and messages that are related to "/ticket yes" and "/ticket no".

# This is a player command which requires the permission "admin360.player.basic".

# After a player has made a feedback, the ticket details will be stored as a record in the database.

# If not, then the database will not store anything. The details will only be kept in RAM.

#Set this to true if you want to remind your players to give

# Set this to true if you want to remind your players to give feedback after their ticket are closed.

#proper feedback right after their case completion.

show-reminder: true

#If the above option (show-reminder) is set to true,

# If the above option (show-reminder) is set to true,

#A timer with an interval measured in seconds is set to remind your players

# a timed message (feedback-required) with an interval (remidner-frequency) measured in seconds

#to complete the feedback just in case they have forgotten. This could be

# will be set to remind your players to submit a feedback. This option can be disturbing for

#somehow disturbing for your players if you try to change the frequency to

# your players if you set the frequency to some low values.

#some low values. But sometimes, more annoying = more effective :)

# But sometimes, more annoying = more effective :)

reminder-frequency: 20

feedback-required: '&f[&6ADMIN360&f] &7We have completed your request. Are you satisfied with it? [&a/ticket yes&7, &c/ticket no&7].'

#feedback-required: You are invited to give feedback after a staff member has completed your request.

# Do you want to run a custom command if the player needs to give a feedback? Default example using chest-command.

#feedback-not-required: Feedback is not required because you haven't opened a ticket or you have submitted a feedback.

# This can work really well with some plugins that opens a GUI with buttons triggering /ticket yes and /ticket no.

#feedback-received: Feedback received. Thank you very much.

# Change this to true if you want to use this option.

#notify-point-received: If you up-vote the service, the staff member handling your case will be given an honor point.

feedback-trigger-custom-command: false

feedback-custom-command: 'chestcommands open feedback.yml <PLAYERNAME>'

feedback-required: '&b&lAdmin360 &3» &7Your request has been completed. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

feedback-not-required: '&b&lAdmin360 &3» &7You are not required to submit a feedback at the moment.'

feedback-received: '&b&lAdmin360 &3» &7Thank you for your feedback. We are looking forward to serving you again.'

notify-point-received: '&b&lAdmin360 &3» &7You have received an honor point because someone loves your service.'

#Additional feature: Trigger custom command? Default example using chest-command: Opening a feedback gui

#with buttons triggering /ticket yes and /ticket no. This can work very well with other GUI menu plugins too.

#Change this to true if you want to use this option.

feedback-use-command: false

feedback-command: 'chestcommands open feedback.yml <player>'

Text moved to lines 228-236

############################################################

# +------------------------------------------------------+ #

# | Tickets Status (/ticket status) | #

# +------------------------------------------------------+ #

############################################################

#/ticket status: Display your ticket status.

#In this section, you can configure messages that are related to ticket status (/ticket status).

#This is a player command which requires the permission node "admin360.player.status" to function.

# 5 Circumstances:

# 1 (status-no-ticket) : You haven't submitted any requests yet.

# 2 (status-in-queue) : You have already submitted a request, which is still in the queue at the moment.

# 3 (status-in-progress) : A staff member is handling your case at the moment.

# 4 (status-processing-staff) : You are a staff member and you are currently handling a case.

# 5 (status-need-feedback) : Your case is closed but you still haven't submitted any valid feedback.

feedback-not-required: '&f[&6ADMIN360&f] &7You are not required to submit a feedback at the moment.'

feedback-received: '&f[&6ADMIN360&f] &7Thank you for your feedback. We are looking forward to serving you again.'

status-no-ticket: '&b&lAdmin360 &3» &7You have no pending requests. Open a ticket via &b/ticket create [details]&7.'

# If you do not want your staff to know who actually votes for them, simply remove the placeholder.

status-in-queue: '&b&lAdmin360 &3» &7Your request has been placed in position &c<position> &7of the queue.'

upvote-rating-notify-staff: '&f[&6ADMIN360&f] &6<PLAYERNAME> &elikes &7your service. [&f1&a▲&7]'

status-in-progress: '&b&lAdmin360 &3» &7A staff member is now reviewing your request.'

downvote-rating-notify-staff: '&f[&6ADMIN360&f] &6<PLAYERNAME> &cdislikes &7your service. [&f1&c▼&7]'

status-processing-staff: '&b&lAdmin360 &3» &7You are processing a request at the moment.'

status-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

############################################################

# +------------------------------------------------------+ #

# | Cancel Tickets (/ticket cancel) | #

# | Removing Tickets (/ticket purge, delete) | #

# +------------------------------------------------------+ #

############################################################

#/ticket cancel: Cancel your submitted request.

# /ticket purge, /ticket delete <name>: Purge all pending tickets or delete a particular ticket.

#In this section, you can configure messages that are related to tickets cancellation (/ticket cancel).

# In this section, you can modify the messages that are related to "/ticket purge" and "/ticket delete".

#This is a player command which requires the permission node "admin360.player.basic" to function.

# They are staff commands which require permission "admin360.staff.purge" and "admin360.staff.delete".

# 5 Circumstances:

# Difference between purge and delete:

# 1 (cancel-failed-no-ticket) : You haven't opened any requests. There are no request for you to cancel.

# Purge: Remove all pending tickets (in queue + in progress).

# 2 (cancel-succeeded-cancelled) : You have cancelled your submitted request successfully.

# Delete: Remove a particular ticket from a player regardless of status (in queue + in progress + awaiting feedback).

# 3 (cancel-failed-in-progress) : You cannot cancel your request because a staff member is now processing it.

# However, you cannot delete a completed ticket.

# 4 (cancel-failed-processing-staff) : You are a staff member and you are processing ticket. You cannot cancel any tickets.

# 5 (cancel-failed-need-feedback) : You cannot cancel your request because you still haven't submitted a valid feedback.

# This message supports multiple lines.

purge-message:

- ''

- '&f[&6ADMIN360&f] &fPurged &c<AMOUNTPURGED> &fpending ticket(s).'

- ''

cancel-failed-no-ticket: '&b&lAdmin360 &3» &7You have no pending requests. Open a ticket via &b/ticket create [details]&7.'

delete-message: '&f[&6ADMIN360&f] &6<PLAYERNAME>&7''s ticket has been removed successfully.'

cancel-succeeded-cancelled: '&b&lAdmin360 &3» &7You have removed your ticket from the queue successfully.'

cancel-failed-in-progress: '&b&lAdmin360 &3» &7You cannot do so because there is a staff member reviewing your request at the moment.'

cancel-failed-processing-staff: '&b&lAdmin360 &3» &7You are still processing a request right now. You can either close or delete it.'

cancel-failed-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

############################################################

# +------------------------------------------------------+ #

# | Tickets Statistics (/ticket stats) | #

# +------------------------------------------------------+ #

############################################################

#/ticket stats: Display tickets statistics.

# /ticket stats: Display tickets statistics.

#In this section, you can configure messages that are related to tickets statistics (/ticket stats).

# In this section, you can modify the messages that are related to "/ticket stats".

#This is a player command which requires the permission node "admin360.player.stats" to function.

# This is a player command which requires the permission "admin360.player.stats".

#This option supports multiple lines.

# <INQUEUE> <INPROGRESS> <AWAITING> <COMPLETED> are temporary counters.

count-message:

# They will be reset once the server restarts. It's because they are stored in RAM.

- ''

# <TOTAL> is a counter of records of the database. <PERCENT> is the upvote ratio.

- '&7&m--------------&r &bTickets Statistics &7&m--------------'

# They will not be reset on server restart.

- ''

- ' &c<in_queue> &fticket(s) in the queue.'

# This message supports multiple lines.

- ' &e<in_progress> &fticket(s) in progress.'

stats-message:

- ' &a<completed> &fticket(s) awaiting feedback.'

- ''

- '&f[&6ADMIN360&f] &c<INQUEUE> &fticket(s) in the queue.'

- '&7&m--------------------------------------------'

- '&f[&6ADMIN360&f] &e<INPROGRESS> &fticket(s) in progress.'

- ''

- '&f[&6ADMIN360&f] &a<AWAITING> &fticket(s) awaiting feedback.'

- '&f[&6ADMIN360&f] &b<COMPLETED> &fticket(s) completed today.'

- '&f[&6ADMIN360&f] &d<TOTAL> &ftotal ticket(s) &7(&f<PERCENT>%&a▲&7)'

- ''

############################################################

# +------------------------------------------------------+ #

# | Trimming Tickets (/ticket purge, delete) | #

# | Honor Points (/ticket hptop, hpstats, hpreset) | #

# +------------------------------------------------------+ #

############################################################

#/ticket purge, /ticket delete <name>: Purge all or remove part of the tickets from the database.

# /ticket hpstats [name]: Honor Points Statistics, /ticket hptop [#]: Honor Points Leaderboard.

#In this section, you can configure messages that are related to tickets deletion (/ticket purge and /ticket delete).

# /ticket hpreset <name>: Clear Honor points of a staff.

#They are staff commands which require permission nodes "admin360.staff.purge" and "admin360.staff.delete" to function.

# In this section, you can modify the settings and messages that are related to honor points.

# They are staff commands which require the permissions "admin360.staff.hptop", "admin360.staff.hpstats"

# and "admin360.staff.hpreset".

#Difference between purge and delete:

# Set the number of records shown in hptop.

#Purging Requests: Remove all pending tickets (in queue + in progress).

default-leaderboard-output: 5

#Delete A Request: Remove a particular ticket from a player regardless of status.

#This option supports multiple lines.

# This message supports multiple lines.

purge-message:

leaderboard-title:

- ''

- '&7&m---------------&r &bPurging Tickets &7&m---------------'

- '&7&m-------------&r &6LEADERBOARD &7&m-------------'

- ''

- ' &7[ &a▲&fUpvote &c▼&fDownvote &a▲&c▼&fTotal &7]'

- ' &fPurged &c<purged> &fpending ticket(s).'

- ''

- '&7&m--------------------------------------------'

- ''

delete-message: '&b&lAdmin360 &3» &7<player>''s ticket has been removed.'

# hptop body message

leaderboard-body: ' &6<ADMINNAME>&7: &f<UPVOTE>&a▲ &f<DOWNVOTE>&c▼ &f<TOTAL>&a▲&c▼ &f<PERCENT>%&a▲'

# This message supports multiple lines.

leaderboard-footer:

- ''

- '&7&m--------------------------------------'

- ''

# This message supports multiple lines.

hpstats-message:

- ''

- '&f[&6ADMIN360&f] &6<ADMINNAME>&f''s Statistics'

- '&f[&6ADMIN360&f] &a<UPVOTE> &fupvote(s) &a▲'

- '&f[&6ADMIN360&f] &c<DOWNVOTE> &fdownvote(s) &c▼'

- '&f[&6ADMIN360&f] &e<TOTAL> &ftotal ticket(s) &a▲&c▼'

- '&f[&6ADMIN360&f] &b<PERCENT>% &fsatisfaction &a▲'

- ''

# Names are stored in the database with case preserved. Case-sensitive for name inputs.

reset-hpstats-failed: '&f[&6ADMIN360&f] &c&nReset Failed&7 Player not found. Names are case-sensitive.'

reset-hpstats-succeeded: '&f[&6ADMIN360&f] &7You have reset &6<ADMINNAME>&7''s stats successfully.'

############################################################

# +------------------------------------------------------+ #

# | Honor Points (/ticket hptop, hpstats, hpreset) | #

# | History (/ticket history) | #

# +------------------------------------------------------+ #

############################################################

#/ticket hpstats [name]: Honor Points Statistics, /ticket hptop [#]: Honor Points Leaderboard.

# /ticket history [#]: Honor Points History.

#/ticket hpreset <name>: Clear Honor points from a staff member.

# In this section, you can modify the settings and messages that are related to "/ticket history".

#In this section, you can modify settings and configure messages that are related to honor points.

# They are staff commands which require the permissions "admin360.staff.history".

#They are staff commands which require permission nodes "admin360.staff.hptop", "admin360.staff.hpstats"

#and "admin360.staff.hpreset" to function.

#default-leaderboard-output: Set the number of records shown in hptop.

default-leaderboard-output: 5

#This option supports multiple lines.

# This command is closely related to the Honor Points system.

leaderboard-title:

# If a /ticket hpreset is executed, the records of that staff will also be removed.

- ''

# A ticket will only appear in the history as a record when it is completed. That's because tickets

- '&7&m-------------&b &bTop Honor Points &7&m-------------'

# in other stages (in queue, in progress, awaiting feedback) will not be stored in the database.

- ''

# They will only be stored temporarily in RAM.

#hptop body message

# Set the number of records shown in history.

leaderboard-message: ' &b<name>: &f<points> &7honor points'

default-history-output: 5

#This option supports multiple lines.

# This message supports multiple lines.

leaderboard-footer:

history-title:

- ''

- '&7&m------------------------------------------'

- '&7&m-----------------&r &6HISTORY &7&m-----------------'

- ''

- ' &7[ &aP: &fPlayer &cS: &fStaff &dR: &fRating &eD: &fDetails &7]'

- ''

stats-message: '&b&lAdmin360 &3» &c<name> &7has &b<points> &7honor points.'

# History body message

#<TIME> is the time that the player opened the ticket.

history-body: '&7[&f<TIME>&7] &aP:&f<PLAYERNAME> &cS:&f<ADMINNAME> &dR:&f<RATING> &eD:&f<DETAILS>'

#Names are stored in the database with case preserved.

# This message supports multiple lines.

reset-stats-succeeded: '&b&lAdmin360 &3» &7Stats reset successfully.'

history-footer:

reset-stats-failed: '&b&lAdmin360 &3» &7Player not found. Names are case-sensitive.'

- ''

- '&7&m------------------------------------------'

- ''

############################################################

# +------------------------------------------------------+ #

# | Final Notes | #

# +------------------------------------------------------+ #

############################################################

# End of file. You're done with the configuration. Congratulations!

#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/

# Project : https://www.spigotmc.org/resources/admin360-reloaded.28285/

#Contributors: Dennie, PPT_T, vidhu1911

# Support : https://www.spigotmc.org/members/jerryui.139798/

# Authors : Dennie, PPT_T, vidhu1911

सेव किए गए Diffs

ऑरिजनल टेक्स्ट

Open file

############################################################
# +------------------------------------------------------+ #
# |                       Notes                          | #
# +------------------------------------------------------+ #
############################################################

#Version 7.1.0
#Tested on Spigot 1.8.8, 1.12.2, 1.13.2, 1.14.4, 1.15.2.

#Config and Plugin version.
#Do not change this unless you know what you are doing.
version: '7.1.0'

#Whenever there is an update available, read the upgrade procedures as instructed on our spigot project page.
#If there are any changes made to this config, for example, an addition of several configurable parameters,
#then you may have to manually delete this file and let a new one regenerate. This would be the quickest way
#to ensure proper functioning of the plugin.

#Since version 7.1.0, we will auto-rename the old config file into "config_old.yml" on server restart.
#You can then spend some time to compare the changes and apply your old settings bit by bit.
#Should you have any problems, please let us know. by Dennie.

#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#Contributors: Dennie, PPT_T, vidhu1911

############################################################
# +------------------------------------------------------+ #
# |           Basic (perms, syntax, help, reload)        | #
# +------------------------------------------------------+ #
############################################################

insufficient-permission: '&b&lAdmin360 &3» &7Access denied. You do not have permission to use this command.'
incorrect-syntax: '&b&lAdmin360 &3» &7Incorrect syntax. Type &b/admin360 &7to display a list of commands.'
not-player-warning: '&b&lAdmin360 &3» &7Commands of Admin360 are all player-only commands.'
reload-message: '&b&lAdmin360 &3» &7The config file has been reloaded successfully.'

#Help Section: Player Commands
#This option supports multiple lines.
#[]: Optional <>: Compulsory
commands-player:
- ''
- '&6Usage&f:'
- ''
- '&b/ticket &ecreate [details]   &fOpen a support ticket.'
- '&b/ticket &ecancel              &7Cancel your ticket.'
- '&b/ticket &estatus              &fView your ticket status.'
- '&b/ticket &estats                &7Display ticket statistics.'
- '&b/admin360 &einfo              &fKnow more about Admin360.'
- ''

#Help Section: Staff Commands
#This option supports multiple lines.
#[]: Optional <>: Compulsory
commands-staff:
- ''
- '&cUsage&f:'
- ''
- '&b/ticket &enext                 &fProceed to the next ticket.'
- '&b/ticket &eclose                &7Declare completion of a ticket.'
- '&b/ticket &epurge               &fPurge all pending tickets.'
- '&b/ticket &edelete <name>     &7Forcibly delete a ticket.'
- '&b/ticket &ehpstats [name]    &fDisplay honor points statistics.'
- '&b/ticket &ehptop [#]           &7Display honor points leaderboard.'
- '&b/ticket &ehpreset <name>   &fReset honor points of a staff.'
- '&b/admin360 &ereload          &7Reload the plugin config file.'
- ''

############################################################
# +------------------------------------------------------+ #
# |           Creating Tickets (/ticket create)          | #
# +------------------------------------------------------+ #
############################################################

#/ticket create [details] : Open a ticket with or without a description.
#In this section, you can modify settings and configure messages that are related to tickets creation (/ticket create).
#This is a player command which requires the permission node "admin360.player.basic" to function.

# 5 Circumstances:
# 1 (create-failed-in-queue) : You have already submitted a request. You cannot create a new ticket.
# 2 (create-failed-in-progress) : There is a staff member handling your case at the moment. You cannot create a new ticket.
# 3 (create-failed-require-feedback) : You still haven't provided a valid feedback. You cannot create a new ticket.
# 4 (create-failed-staff-ticket) : You are a staff member. You are not allowed to create a ticket to prevent boosting.
# 5 (new-ticket-created) : A new ticket is created and is immediately put in the next position of the queue by default.

#After a ticket is created, available staff members (with permission node "admin360.staff.basic") will be notified.
#If there is a description (i.e. reason) specified by the user who opened the ticket, staff will be able to see that.

#Preliminary fail-safe check: Can be turned off. Check if any staff members are currently available.
#If this is set to true, players will not be allowed to create any new tickets if there are no staff in the server.
#How do we determine between players and staff? Staff are those who have the permission "admin360.staff.basic".
staff-online-required: true
no-staff-online: '&b&lAdmin360 &3» &7You cannot open a ticket when there are no staff members available.'

create-failed-in-queue: '&b&lAdmin360 &3» &7You have already opened a ticket.'
create-failed-in-progress: '&b&lAdmin360 &3» &7A staff member is now reviewing your request.'
create-failed-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'
create-failed-staff-ticket: '&b&lAdmin360 &3» &7To prevent boosting, staff members are not allowed to open a ticket.'
new-ticket-created: '&b&lAdmin360 &3» &7You have opened a ticket (Position: &c<queue>&7). Use &b/ticket status &7to check your progress.'

#Additional feature: Trigger custom command? Default example using title-manager.
#Change this to true if you want to use this option.
new-ticket-use-command: false
new-ticket-command: 'tm msg <player> &b\n&bTicket Created &7(&fPosition: &c<queue>&7)'

#This option supports multiple lines.
notify-staff-new-ticket:
- ''
- '&7&m-----------&b &aNew Ticket &7&m-----------'
- ''
- '       &a<player> &fopened a ticket.'
- '       &7(&e<queue> &fticket(s) remaining&7)'
- ''
- '&7&m--------------------------------'
- ''

#This option supports multiple lines.
notify-staff-new-ticket-with-reason:
- ''
- '&7&m-----------&b &aNew Ticket &7&m-----------'
- ''
- '       &a<player> &fopened a ticket.'
- '       &aDetails: &f<reason>'
- '       &7(&e<queue> &fticket(s) remaining&7)'
- ''
- '&7&m--------------------------------'
- ''

############################################################
# +------------------------------------------------------+ #
# |           Processing Tickets (/ticket next)          | #
# +------------------------------------------------------+ #
############################################################

#/ticket next: Proceed to the next help-request.
#In this section, you can modify settings and configure messages that are related to tickets processing (/ticket next).
#This is a staff command which requires the permission node "admin360.staff.basic" to function.

# 4 Circumstances:
# 1 (next-failed-no-ticket) : There are no tickets in the queue. You cannot process the next ticket.
# 2 (next-failed-attending) : You are still processing an unclosed case. You cannot process the next ticket.
# 3 (next-failed-self-ticket) : You are a staff member and you are not allowed to process your own requests.
# 4 succeeded : You will be teleported to the target player by Admin360. The user and staff will be notified.

#Please note that staff members should not be allowed to boost tickets.
#You may negate the permission for /ticket create "-admin360.player.basic" for your staff permission group(s),
#so that they will not be able to exploit any potential loopholes.
#But it is fine if you do not do so. We have hard-coded these restrictions into the plugin ever since v7.0.2.
#Now, by default, staff members are not even able to to do /ticket create in the first place,
#which should be provided sufficient anti-exploit protection.

#Staff members in the server (with permission "admin360.staff.basic") will be notified when a ticket status is changed
#from pending (in queue) to processing (in progress).
#The user who created the ticket will be notified as well.

next-failed-no-ticket: '&b&lAdmin360 &3» &7There are no pending tickets at the moment.'
next-failed-attending: '&b&lAdmin360 &3» &7Before proceeding to the next request, you have to complete the current one first.'
next-failed-self-ticket: '&b&lAdmin360 &3» &7You are not allowed to process requests that are submitted by yourself.'

#This option supports multiple lines.
notify-user-ticket-handling:
- '&b&lAdmin360 &3» &c<staff> &7is now reviewing your request.'

#Additional feature: Trigger custom command? Default example using title-manager.
#Change this to true if you want to use this option.
notify-user-ticket-handling-use-command: false
notify-user-ticket-handling-command: 'tm msg <player> &b\n&c<staff> &bis now reviewing your request.'

#This option supports multiple lines.
notify-staff-ticket-handling:
- ''
- '&7&m----------&b &dStaff Activity &7&m----------'
- ''
- '       &d<staff> &fis now processing'
- '       &d<player>&f''s ticket.'
- '       &7(&e<tickets> &fticket(s) remaining&7)'
- ''
- '&7&m--------------------------------'
- ''

############################################################
# +------------------------------------------------------+ #
# |            Closing Tickets (/ticket close)           | #
# +------------------------------------------------------+ #
############################################################

#/ticket close: Close a ticket and mark it as completed.
#In this section, you can configure messages that are related to tickets closure (/ticket close).
#This is a staff command which requires the permission node "admin360.staff.basic" to function.

# 2 Circumstances:
# 1 (close-failed-not-attending) : You are not processing any tickets at the moment so no request can be closed.
# 2 (close-succeeded-ticket-closed) : You have closed the ticket you are handling at the moment.

close-failed-not-attending: '&b&lAdmin360 &3» &7You are not processing any requests at the moment.'
close-succeeded-ticket-closed: '&b&lAdmin360 &3» &7This case is now closed.'

############################################################
# +------------------------------------------------------+ #
# |           Giving Feedback (/ticket yes or no)        | #
# +------------------------------------------------------+ #
############################################################

#/ticket yes, /ticket no: Providing service feedback. /ticket yes: satisfactory; /ticket no: poor experience.
#In this section, you can modify settings and configure messages that are related to feedback (/ticket yes and /ticket no).
#This is a player command which requires the permission node "admin360.player.basic" to function.

#Set this to true if you want to remind your players to give
#proper feedback right after their case completion.
show-reminder: true

#If the above option (show-reminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#to complete the feedback just in case they have forgotten. This could be
#somehow disturbing for your players if you try to change the frequency to
#some low values. But sometimes, more annoying = more effective :)
reminder-frequency: 20

#feedback-required: You are invited to give feedback after a staff member has completed your request.
#feedback-not-required: Feedback is not required because you haven't opened a ticket or you have submitted a feedback.
#feedback-received: Feedback received. Thank you very much.
#notify-point-received: If you up-vote the service, the staff member handling your case will be given an honor point.

feedback-required: '&b&lAdmin360 &3» &7Your request has been completed. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'
feedback-not-required: '&b&lAdmin360 &3» &7You are not required to submit a feedback at the moment.'
feedback-received: '&b&lAdmin360 &3» &7Thank you for your feedback. We are looking forward to serving you again.'
notify-point-received: '&b&lAdmin360 &3» &7You have received an honor point because someone loves your service.'

#Additional feature: Trigger custom command? Default example using chest-command: Opening a feedback gui
#with buttons triggering /ticket yes and /ticket no. This can work very well with other GUI menu plugins too.
#Change this to true if you want to use this option.
feedback-use-command: false
feedback-command: 'chestcommands open feedback.yml <player>'

############################################################
# +------------------------------------------------------+ #
# |             Tickets Status (/ticket status)          | #
# +------------------------------------------------------+ #
############################################################

#/ticket status: Display your ticket status.
#In this section, you can configure messages that are related to ticket status (/ticket status).
#This is a player command which requires the permission node "admin360.player.status" to function.

# 5 Circumstances:
# 1 (status-no-ticket) : You haven't submitted any requests yet.
# 2 (status-in-queue) : You have already submitted a request, which is still in the queue at the moment.
# 3 (status-in-progress) : A staff member is handling your case at the moment.
# 4 (status-processing-staff) : You are a staff member and you are currently handling a case.
# 5 (status-need-feedback) : Your case is closed but you still haven't submitted any valid feedback.

status-no-ticket: '&b&lAdmin360 &3» &7You have no pending requests. Open a ticket via &b/ticket create [details]&7.'
status-in-queue: '&b&lAdmin360 &3» &7Your request has been placed in position &c<position> &7of the queue.'
status-in-progress: '&b&lAdmin360 &3» &7A staff member is now reviewing your request.'
status-processing-staff: '&b&lAdmin360 &3» &7You are processing a request at the moment.'
status-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

############################################################
# +------------------------------------------------------+ #
# |            Cancel Tickets (/ticket cancel)           | #
# +------------------------------------------------------+ #
############################################################

#/ticket cancel: Cancel your submitted request.
#In this section, you can configure messages that are related to tickets cancellation (/ticket cancel).
#This is a player command which requires the permission node "admin360.player.basic" to function.

# 5 Circumstances:
# 1 (cancel-failed-no-ticket) : You haven't opened any requests. There are no request for you to cancel.
# 2 (cancel-succeeded-cancelled) : You have cancelled your submitted request successfully.
# 3 (cancel-failed-in-progress) : You cannot cancel your request because a staff member is now processing it.
# 4 (cancel-failed-processing-staff) : You are a staff member and you are processing ticket. You cannot cancel any tickets.
# 5 (cancel-failed-need-feedback) : You cannot cancel your request because you still haven't submitted a valid feedback.

cancel-failed-no-ticket: '&b&lAdmin360 &3» &7You have no pending requests. Open a ticket via &b/ticket create [details]&7.'
cancel-succeeded-cancelled: '&b&lAdmin360 &3» &7You have removed your ticket from the queue successfully.'
cancel-failed-in-progress: '&b&lAdmin360 &3» &7You cannot do so because there is a staff member reviewing your request at the moment.'
cancel-failed-processing-staff: '&b&lAdmin360 &3» &7You are still processing a request right now. You can either close or delete it.'
cancel-failed-require-feedback: '&b&lAdmin360 &3» &7You still haven''t submitted a feedback. Please rate our service. Satisfactory? (&a/ticket yes&7, &c/ticket no&7).'

############################################################
# +------------------------------------------------------+ #
# |           Tickets Statistics (/ticket stats)         | #
# +------------------------------------------------------+ #
############################################################

#/ticket stats: Display tickets statistics.
#In this section, you can configure messages that are related to tickets statistics (/ticket stats).
#This is a player command which requires the permission node "admin360.player.stats" to function.

#This option supports multiple lines.
count-message:
- ''
- '&7&m--------------&r &bTickets Statistics &7&m--------------'
- ''
- '               &c<in_queue> &fticket(s) in the queue.'
- '               &e<in_progress> &fticket(s) in progress.'
- '               &a<completed> &fticket(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''

############################################################
# +------------------------------------------------------+ #
# |        Trimming Tickets (/ticket purge, delete)      | #
# +------------------------------------------------------+ #
############################################################

#/ticket purge, /ticket delete <name>: Purge all or remove part of the tickets from the database.
#In this section, you can configure messages that are related to tickets deletion (/ticket purge and /ticket delete).
#They are staff commands which require permission nodes "admin360.staff.purge" and "admin360.staff.delete" to function.

#Difference between purge and delete:
#Purging Requests: Remove all pending tickets (in queue + in progress).
#Delete A Request: Remove a particular ticket from a player regardless of status.

#This option supports multiple lines.
purge-message:
- ''
- '&7&m---------------&r &bPurging Tickets &7&m---------------'
- ''
- '                &fPurged &c<purged> &fpending ticket(s).'
- ''
- '&7&m--------------------------------------------'
- ''

delete-message: '&b&lAdmin360 &3» &7<player>''s ticket has been removed.'

############################################################
# +------------------------------------------------------+ #
# |    Honor Points (/ticket hptop, hpstats, hpreset)    | #
# +------------------------------------------------------+ #
############################################################

#/ticket hpstats [name]: Honor Points Statistics, /ticket hptop [#]: Honor Points Leaderboard.
#/ticket hpreset <name>: Clear Honor points from a staff member.
#In this section, you can modify settings and configure messages that are related to honor points.
#They are staff commands which require permission nodes "admin360.staff.hptop", "admin360.staff.hpstats"
#and "admin360.staff.hpreset" to function.

#default-leaderboard-output: Set the number of records shown in hptop.
default-leaderboard-output: 5

#This option supports multiple lines.
leaderboard-title:
- ''
- '&7&m-------------&b &bTop Honor Points &7&m-------------'
- ''

#hptop body message
leaderboard-message: '    &b<name>: &f<points> &7honor points'

#This option supports multiple lines.
leaderboard-footer:
- ''
- '&7&m------------------------------------------'
- ''

stats-message: '&b&lAdmin360 &3» &c<name> &7has &b<points> &7honor points.'

#Names are stored in the database with case preserved.
reset-stats-succeeded: '&b&lAdmin360 &3» &7Stats reset successfully.'
reset-stats-failed: '&b&lAdmin360 &3» &7Player not found. Names are case-sensitive.'

############################################################
# +------------------------------------------------------+ #
# |                      Final Notes                     | #
# +------------------------------------------------------+ #
############################################################

# End of file. You're done with the configuration. Congratulations!

#Link: https://www.spigotmc.org/resources/admin360-reloaded.28285/
#Contributors: Dennie, PPT_T, vidhu1911

परिवर्तित टेक्स्ट

Open file

# Version 8.0.0
# Tested on Spigot 1.8.8, 1.12.2, 1.13.2, 1.14.4, 1.15.2, 1.16.4.

# Config version = Plugin version.
# Do not change this unless you know what you're doing.
# This is for the plugin to check whether we should generate a new config for you.
version: '8.0.0'

# Whenever there's an update available, read the upgrade procedures as instructed on our spigot project page.
# If there're any changes made to this config, for example, if we've added several new settings or messages,
# you may have to compare the changes of the new and old config. And, it takes time to apply your old settings
# especially when the update is big.

# Since version 7.1.0, the plugin will auto-rename the old config file into "config_old.yml" on server restart.
# This is to make sure that everything works even if we reworked the config file (which is something I always do).
# But remember to delete the "config_old.yml" after you've migrated all the changes.
# If not, it may break this auto-rename feature on future updates.

# As you can see, the comments can be lengthy because we want to explain everything to you.
# If you really spend time read through this, then you will know how the plugin works.
# If you want to disable some messages, simply make it an empty line using ''.
# All default messages contain all the placeholders that can be used. You can remove it or dupliciate it.
# However, placeholders will only work in that particular message.

# We welcome users to make translation of this config. Contact us so that we can put your translation official.
# Project: https://www.spigotmc.org/resources/admin360-reloaded.28285/
# Support: https://www.spigotmc.org/members/jerryui.139798/
# Authors: Dennie, PPT_T, vidhu1911

no-permission: '&f[&6ADMIN360&f] &c&nAccess Denied&7 You do not have permission to use this command.'
incorrect-syntax: '&f[&6ADMIN360&f] &c&nIncorrect Syntax&7 Use &6/admin360 &7to display a list of commands.'
is-player-check: '&f[&6ADMIN360&f] &c&nAccess Denied&7 This is a player-only command.'
reload-message: '&f[&6ADMIN360&f] &7The config file has been reloaded successfully.'

# Help Section: Player Commands
# This message supports multiple lines.
command-list-player:
  - ''
  - '&7&m------------&r &6ADMIN360 &7&m------------'
  - '&6/ticket create [details] &f- &7Open a ticket.'
  - '&6/ticket cancel &f- &7Cancel your ticket.'
  - '&6/ticket status &f- &7Query ticket status.'
  - '&6/ticket stats &f- &7View ticket statistics.'
  - '&6/ticket help &f- &7Print command list.'
  - '&6/admin360 &f- &7Display plugin info.'
  - '&7*&fParameters: [Optional] <Compulsory>'
  - '&7&m---------------------------------'
  - ''

# Help Section: Staff Commands
# This message supports multiple lines.
command-list-staff:
  - ''
  - '&7&m------------&r &6ADMIN360 &7&m------------'
  - '&6/ticket next &f- &7Proceed to the next ticket.'
  - '&6/ticket tp &f- &7Teleport to target player.'
  - '&6/ticket info &f- &7View the ticket details.'
  - '&6/ticket close &f- &7Close/complete a ticket.'
  - '&6/ticket purge &f- &7Purge all queuing tickets.'
  - '&6/ticket delete <name> &f- &7Delete a ticket.'
  - '&6/ticket history [#] &f- &7View ticket history.'
  - '&6/ticket hpstats [name] &f- &7View staff stats.'
  - '&6/ticket hptop [#] &f- &7View staff leaderboard.'
  - '&6/ticket hpreset <name> &f- &7Reset staff stats.'
  - '&6/admin360 reload &f- &7Reload the config file.'
  - '&7*&fParameters: [Optional] <Compulsory>'
  - '&7&m---------------------------------'
  - ''

# /ticket create [details] : Open a ticket with or without a description (optional) of the case.
# In this section, you can modify the settings and messages that are related to "/ticket create".
# This is a player command which requires the permission "admin360.player.basic".

# create-failed-no-staff : Creation aborted because there are no staff online.
# create-failed-in-queue : Creation aborted because you already have a ticket opened.
# create-failed-in-progress : Creation aborted because a staff is attending your help-request.
# create-failed-require-feedback : Creation aborted because you still haven't submitted a feedback for your previous ticket.
# create-failed-anti-exploit : Creation aborted because you are a staff member. Staff is banned from ticket creation to prevent boosting.
#*boosting: self-ticketing exploit.
# create-succeeded : Creation succeeded. Your ticket has been put in the next position of the queue.

# After a ticket is opened, your staff (with permission "admin360.staff.basic") will be notified.

# Command cooldown to avoid spammming issues.
# The unit of cooldown-timer is seconds.
use-cooldown: true
cooldown-timer: 60
cooldown-message: '&f[&6ADMIN360&f] &7Please wait for &6<SECONDSLEFT>s&7 before opening another ticket.'

# Check if any staff members are currently available.
# If this is set to true, players will not be allowed to open a new ticket if there are no staff in the server.
# How do we determine between a player and a staff? Staff are those who have the permission "admin360.staff.basic".
staff-online-required: true
create-failed-no-staff: '&f[&6ADMIN360&f] &c&nCreate Failed&7 There are no staff currently available.'

create-failed-in-queue: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You already have a ticket opened. (&fTips: &6/ticket status&7)'
create-failed-in-progress: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You have another ticket in progress.(&fTips: &6/ticket status&7)'
create-failed-require-feedback: '&f[&6ADMIN360&f] &c&nCreate Failed&7 You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'
create-failed-anti-exploit: '&f[&6ADMIN360&f] &c&nCreate Failed&7 Members of the staff team are not allowed to open a ticket to avoid exploits.'

# This message supports multiple lines.
create-succeeded:
  - '&f[&6ADMIN360&f] &7You have opened a ticket (&fPosition: &c<POSITION>&7). Use &6/ticket status &7to check your progress.'
# Do you want to run a custom command right after a ticket is opened? Default example using title-manager.
# Change this to true if you want to use this option.
ticket-created-trigger-custom-command: false
ticket-created-custom-command: 'tm msg <PLAYERNAME> &b\n&6Ticket Created &7(&fPosition: &6<POSITION>&7)'

# Notify your staff when there is a ticket created.
# This message supports multiple lines.
ticket-created-notify-staff:
  - ''
  - '&f[&6ADMIN360&f] &6<PLAYERNAME> &copened a &a&lNEW &cticket.'
  - '&f[&6ADMIN360&f] &cDetails: &f<DETAILS>'
  - '&f[&6ADMIN360&f] &7(&e<TICKETSREMAIN> &fticket(s) remaining&7)'
  - ''

############################################################
# +------------------------------------------------------+ #
# |           Cancelling Tickets (/ticket cancel)        | #
# +------------------------------------------------------+ #
############################################################

# /ticket cancel: Cancel your submitted request.
# In this section, you can modify the messages that are related to "/ticket cancel".
# This is a player command which requires the permission "admin360.player.basic".

# cancel-failed-no-ticket : You didn't opened any request. There are no request for you to cancel.
# cancel-failed-in-progress : You can't cancel your request because a staff is now attending it.
# cancel-failed-attending : You are a staff and you are processing a ticket. You cannot cancel any tickets.
# cancel-failed-require-feedback : You cannot cancel your request because you still haven't submitted a feedback for your previous ticket.
# cancel-succeeded : You have cancelled your submitted request successfully.

cancel-failed-no-ticket: '&f[&6ADMIN360&f] &c&nCancel Failed&7 Do you need help? (&fTips: &6/ticket create [details]&7)'
cancel-failed-in-progress: '&f[&6ADMIN360&f] &c&nCancel Failed&7 A staff is attending your help-request. (&fTips: &6/ticket status&7)'
cancel-failed-attending: '&f[&6ADMIN360&f] &c&nCancel Failed&7 Members of the staff team do not need this function.'
cancel-failed-require-feedback: '&f[&6ADMIN360&f] &c&nCancel Failed&7 You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'
cancel-succeeded: '&f[&6ADMIN360&f] &7You have removed your ticket from the queue successfully.'

# /ticket status: Query the current status of your ticket.
# In this section, you can modify the messages that are related to "/ticket status".
# This is a player command which requires the permission "admin360.player.status".

# status-no-ticket : You didn't submit any help-requests. You can open one.
# status-in-queue : You already have a ticket opened, which is still in the queue at the moment.
# status-in-progress : A staff is attending your request at the moment.
# status-attending : You are a staff and you are currently attending a case.
# status-require-feedback : Your ticket is closed but you still haven't give us a feedback.

status-no-ticket: '&f[&6ADMIN360&f] &7Do you need help? (&fTips: &6/ticket create [details]&7)'
status-in-queue: '&f[&6ADMIN360&f] &7Your ticket is now in position &6<POSITION> &7of the queue.'
status-in-progress: '&f[&6ADMIN360&f] &7Your ticket is now in progress. A staff will contact you soon.'
status-attending: '&f[&6ADMIN360&f] &7You are attending a help-request at the moment. (&fTips: &6/ticket info&7)'
status-require-feedback: '&f[&6ADMIN360&f] &7You may have forgotten to give us a feedback. (&fTips: &a/ticket yes&7, &c/ticket no&7)'

############################################################
# +------------------------------------------------------+ #
# |            Attending Tickets (/ticket next)          | #
# +------------------------------------------------------+ #
############################################################

# /ticket next: Proceed to the next help-request.
# In this section, you can modify the settings and messages that are related to "/ticket next".
# This is a staff command which requires the permission 'admin360.staff.basic".

# next-failed-no-ticket : Currently, there are no tickets in the queue so you cannot proceed.
# next-failed-attending : You are still attending a help-request. That's why you can't proceed to the next ticket.
# If "/ticket next" succeeded, you will be teleported to the target player by Admin360 (which can be disabled).

# Your staff in the server (with permission "admin360.staff.basic") will be notified when the status of a ticket is
# changed from pending (in queue) to processing (in progress). The player who created the ticket will also be notified.

next-failed-no-ticket: '&f[&6ADMIN360&f] &c&nNext Failed&7 There are no unattended tickets at the moment.'
next-failed-attending: '&f[&6ADMIN360&f] &c&nNext Failed&7 You have to close your current ticket before attending the next one.'

# Do you want Admin360 to teleport your staff to the target player by default?
# Change this to false if you want to disable this option.
use-auto-teleport: true

# This message supports multiple lines.
ticket-in-progress-notify-player:
  - '&f[&6ADMIN360&f] &6<ADMINNAME> &7is now reviewing your help-request.'
# Do you want to run a custom command right after a ticket changed its status? Default example using title-manager.
# Change this to true if you want to use this option.
ticket-in-progress-trigger-custom-command: false
ticket-in-progress-custom-command: 'tm msg <PLAYERNAME> &b\n&6<ADMINNAME> &fis now reviewing your request.'

# This message supports multiple lines.
ticket-in-progress-notify-staff:
  - ''
  - '&f[&6ADMIN360&f] &6<ADMINNAME> &cis now processing &6<PLAYERNAME>&c''s ticket.'
  - '&f[&6ADMIN360&f] &7(&e<TICKETSREMAIN> &fticket(s) remaining&7)'
  - ''

############################################################
# +------------------------------------------------------+ #
# |                 Teleport (/ticket tp)                | #
# +------------------------------------------------------+ #
############################################################

# /ticket tp: It allows you to teleport to the player who opened the ticket that you are processing now.
# In this section, you can modify the messages that are related to "/ticket tp".
# This is a staff command which requires the permission "admin360.staff.tp".

teleport-failed: '&f[&6ADMIN360&f] &c&nTeleport Failed&7 You cannot use this function at the moment.'
teleport-succeeded: '&f[&6ADMIN360&f] &7You have been teleported to &6<PLAYERNAME>&7.'

############################################################
# +------------------------------------------------------+ #
# |                View-Info (/ticket info)              | #
# +------------------------------------------------------+ #
############################################################

# /ticket info: Remember "/ticket create [details]"? This command enables you to read that details again
# if you are processing that ticket (in case you forgot).
# In this section, you can modify the messages that are related to "/ticket info".
# This is a staff command which requires the permission "admin360.staff.info".

info-failed: '&f[&6ADMIN360&f] &c&nView-Info Failed&7 You cannot use this function at the moment.'

# This message supports multiple lines.
info-message:
  - ''
  - '&f[&6ADMIN360&f]     &6Name: &f<PLAYERNAME>'
  - '&f[&6ADMIN360&f]     &6Details: &f<DETAILS>'
  - '&f[&6ADMIN360&f]     &6Time: &f<TIME>'
  - ''

# /ticket close: Close a ticket and mark it as completed.
# In this section, you can modify the messages that are related to "/ticket close".
# This is a staff command which requires the permission "admin360.staff.basic".

close-failed: '&f[&6ADMIN360&f] &c&nClose Failed&7 You are not attending any request at the moment.'
close-succeeded: '&f[&6ADMIN360&f] &7You have closed this ticket successfully.'

# /ticket yes, /ticket no: After a ticket is closed, your player will be asked to rate the service.
# They can upvote or downvote. /ticket yes: upvote; /ticket no: downvote.
# In this section, you can modify the settings and messages that are related to "/ticket yes" and "/ticket no".
# This is a player command which requires the permission "admin360.player.basic".

# After a player has made a feedback, the ticket details will be stored as a record in the database.
# If not, then the database will not store anything. The details will only be kept in RAM.

# Set this to true if you want to remind your players to give feedback after their ticket are closed.
show-reminder: true

# If the above option (show-reminder) is set to true,
# a timed message (feedback-required) with an interval (remidner-frequency) measured in seconds
# will be set to remind your players to submit a feedback. This option can be disturbing for
# your players if you set the frequency to some low values.
# But sometimes, more annoying = more effective :)
reminder-frequency: 20

feedback-required: '&f[&6ADMIN360&f] &7We have completed your request. Are you satisfied with it? [&a/ticket yes&7, &c/ticket no&7].'
# Do you want to run a custom command if the player needs to give a feedback? Default example using chest-command.
# This can work really well with some plugins that opens a GUI with buttons triggering /ticket yes and /ticket no.
# Change this to true if you want to use this option.
feedback-trigger-custom-command: false
feedback-custom-command: 'chestcommands open feedback.yml <PLAYERNAME>'

feedback-not-required: '&f[&6ADMIN360&f] &7You are not required to submit a feedback at the moment.'
feedback-received: '&f[&6ADMIN360&f] &7Thank you for your feedback. We are looking forward to serving you again.'

# If you do not want your staff to know who actually votes for them, simply remove the placeholder.
upvote-rating-notify-staff: '&f[&6ADMIN360&f] &6<PLAYERNAME> &elikes &7your service. [&f1&a▲&7]'
downvote-rating-notify-staff: '&f[&6ADMIN360&f] &6<PLAYERNAME> &cdislikes &7your service. [&f1&c▼&7]'

############################################################
# +------------------------------------------------------+ #
# |        Removing Tickets (/ticket purge, delete)      | #
# +------------------------------------------------------+ #
############################################################

# /ticket purge, /ticket delete <name>: Purge all pending tickets or delete a particular ticket.
# In this section, you can modify the messages that are related to "/ticket purge" and "/ticket delete".
# They are staff commands which require permission "admin360.staff.purge" and "admin360.staff.delete".

# Difference between purge and delete:
# Purge: Remove all pending tickets (in queue + in progress).
# Delete: Remove a particular ticket from a player regardless of status (in queue + in progress + awaiting feedback).
# However, you cannot delete a completed ticket.

# This message supports multiple lines.
purge-message:
  - ''
  - '&f[&6ADMIN360&f]     &fPurged &c<AMOUNTPURGED> &fpending ticket(s).'
  - ''

delete-message: '&f[&6ADMIN360&f] &6<PLAYERNAME>&7''s ticket has been removed successfully.'

# /ticket stats: Display tickets statistics.
# In this section, you can modify the messages that are related to "/ticket stats".
# This is a player command which requires the permission "admin360.player.stats".

# <INQUEUE> <INPROGRESS> <AWAITING> <COMPLETED> are temporary counters.
# They will be reset once the server restarts. It's because they are stored in RAM.
# <TOTAL> is a counter of records of the database. <PERCENT> is the upvote ratio.
# They will not be reset on server restart.

# This message supports multiple lines.
stats-message:
  - ''
  - '&f[&6ADMIN360&f]     &c<INQUEUE> &fticket(s) in the queue.'
  - '&f[&6ADMIN360&f]     &e<INPROGRESS> &fticket(s) in progress.'
  - '&f[&6ADMIN360&f]     &a<AWAITING> &fticket(s) awaiting feedback.'
  - '&f[&6ADMIN360&f]     &b<COMPLETED> &fticket(s) completed today.'
  - '&f[&6ADMIN360&f]     &d<TOTAL> &ftotal ticket(s) &7(&f<PERCENT>%&a▲&7)'
  - ''

############################################################
# +------------------------------------------------------+ #
# |     Honor Points (/ticket hptop, hpstats, hpreset)   | #
# +------------------------------------------------------+ #
############################################################

# /ticket hpstats [name]: Honor Points Statistics, /ticket hptop [#]: Honor Points Leaderboard.
# /ticket hpreset <name>: Clear Honor points of a staff.
# In this section, you can modify the settings and messages that are related to honor points.
# They are staff commands which require the permissions "admin360.staff.hptop", "admin360.staff.hpstats"
# and "admin360.staff.hpreset".

# Set the number of records shown in hptop.
default-leaderboard-output: 5

# This message supports multiple lines.
leaderboard-title:
  - ''
  - '&7&m-------------&r &6LEADERBOARD &7&m-------------'
  - '         &7[ &a▲&fUpvote  &c▼&fDownvote  &a▲&c▼&fTotal &7]'
  - ''

# hptop body message
leaderboard-body: '           &6<ADMINNAME>&7: &f<UPVOTE>&a▲ &f<DOWNVOTE>&c▼ &f<TOTAL>&a▲&c▼ &f<PERCENT>%&a▲'

# This message supports multiple lines.
leaderboard-footer:
  - ''
  - '&7&m--------------------------------------'
  - ''

# This message supports multiple lines.
hpstats-message:
  - ''
  - '&f[&6ADMIN360&f]     &6<ADMINNAME>&f''s Statistics'
  - '&f[&6ADMIN360&f]     &a<UPVOTE> &fupvote(s) &a▲'
  - '&f[&6ADMIN360&f]     &c<DOWNVOTE> &fdownvote(s) &c▼'
  - '&f[&6ADMIN360&f]     &e<TOTAL> &ftotal ticket(s) &a▲&c▼'
  - '&f[&6ADMIN360&f]     &b<PERCENT>% &fsatisfaction &a▲'
  - ''

# Names are stored in the database with case preserved. Case-sensitive for name inputs.
reset-hpstats-failed: '&f[&6ADMIN360&f] &c&nReset Failed&7 Player not found. Names are case-sensitive.'
reset-hpstats-succeeded: '&f[&6ADMIN360&f] &7You have reset &6<ADMINNAME>&7''s stats successfully.'

############################################################
# +------------------------------------------------------+ #
# |                History (/ticket history)             | #
# +------------------------------------------------------+ #
############################################################

# /ticket history [#]: Honor Points History.
# In this section, you can modify the settings and messages that are related to "/ticket history".
# They are staff commands which require the permissions "admin360.staff.history".

# This command is closely related to the Honor Points system.
# If a /ticket hpreset is executed, the records of that staff will also be removed.
# A ticket will only appear in the history as a record when it is completed. That's because tickets
# in other stages (in queue, in progress, awaiting feedback) will not be stored in the database.
# They will only be stored temporarily in RAM.

# Set the number of records shown in history.
default-history-output: 5

# This message supports multiple lines.
history-title:
  - ''
  - '&7&m-----------------&r &6HISTORY &7&m-----------------'
  - '     &7[ &aP: &fPlayer  &cS: &fStaff  &dR: &fRating  &eD: &fDetails &7]'
  - ''

# History body message
#<TIME> is the time that the player opened the ticket.
history-body: '&7[&f<TIME>&7] &aP:&f<PLAYERNAME> &cS:&f<ADMINNAME> &dR:&f<RATING> &eD:&f<DETAILS>'

# This message supports multiple lines.
history-footer:
  - ''
  - '&7&m------------------------------------------'
  - ''

# End of file. You're done with the configuration. Congratulations!

# Project : https://www.spigotmc.org/resources/admin360-reloaded.28285/
# Support : https://www.spigotmc.org/members/jerryui.139798/
# Authors : Dennie, PPT_T, vidhu1911