############################################################
# +------------------------------------------------------+ #
# |                       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: -admin360.player.helpme
#so that they would not be able to exploit the loopholes.

#Staff_online (with permission admin360.admin.respond) will be notified (ticket_staff_notify) when a ticket status is changed from pending to processing.
#The involved user who has opened the ticket will be notified (ticket_user_notify) as well.


next_no_ticket: '&6Admin360 &f» &7There are no tickets in the queue at the moment.'
next_attending: '&6Admin360 &f» &7You need to close the ticket first before proceeding to the next case.'
next_anti_staff_abuse: '&6Admin360 &f» &7You are not allowed to process your own ticket.'

ticket_user_notify:
- '&6Admin360 &f» &c<staff> &7is now handling your case.'

#Use command? Example using title manager.
ticket_user_notify_usecommand: false
ticket_user_notify_command: 'tm msg <player> &6\n&c<staff> &6is now handling your case.'

ticket_staff_notify:
- ''
- '&e<staff> &dis now handling &e<player>&d''s case &d(&e<tickets> &dtickets remaining).'
- ''



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

#/ticket close: Mark a ticket as completed.
#In this section, you can modify messages that are related to /ticket close.
#This is a staff command with permission node admin360.admin.respond.

# 2 Cases:
# 1 (close_not_attending) : No tickets would be closed because there are no cases currently in progress.
# 2 (close_ticket_closed) : There is a case in progress and it is closed now.


close_not_attending: '&6Admin360 &f» &7You are not handling any cases at the moment.'
close_ticket_closed: '&6Admin360 &f» &7You have successfully closed this case.'



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

#/ticket yes, /ticket no: Providing service feedback
#In this section, you can modify messages and settings that are related to /ticket yes and /ticket no.
#This is a player command with permission node admin360.player.helpme.


#Set it to true if you would like your players to be reminded to give
#a feedback right after their tickets were marked as Completed.
showReminder: true

#If the above (showReminder) is set to true,
#A timer with an interval measured in seconds is set to remind your players
#for completing the feedback in case they have kindly forgotten. (This could
#be disturbing for your players if the frequency is set to a lower number.
#But then, they would be forced to submit a feedback.)
reminderFrequency: 20


#feedback_required: Players are invited to give feedback after a staff has completed their requests.
#feedback_not_required: Feedback is not required because that player did not open a ticket or he/she has already submitted a feedback.
#feedback_received: Feedback received.
#notify_point_received: If the player has up-voted the service, the staff handling the case would be given an honor point.

feedback_required: '&6Admin360 &f» &7Your case is now closed. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'
feedback_not_required: '&6Admin360 &f» &7You are not required to give a feedback at the moment.'
feedback_received: '&6Admin360 &f» &7Thank you for your generous feedback. Good luck and have a nice day.'
notify_point_received: '&6Admin360 &f» &7You have just received an honor point.'

#Use command? Example using chestcommand.
feedback_required_usecommand: false
feedback_required_command: 'chestcommands open feedback.yml <player>'



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

#/ticket status: Display your ticket status.
#In this section, you can modify messages that are related to /ticket status.
#This is a player command with permission node admin360.player.status.

# 4 Cases:
# 1 (status_no_ticket) : You have not submitted any tickets yet.
# 2 (status_inqueue) : You have already submitted a ticket, which is on the queue now.
# 3 (status_inprogress) : A staff is handling your case right now.
# 4 (status_feedback) : Your case is closed but you still have not submitted any feedback.


status_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
status_inqueue: '&6Admin360 &f» &7Your ticket is now in position &c<position> &7of the queue. Please be patient.'
status_inprogress: '&6Admin360 &f» &7A staff is now processing your case.'
status_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'



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

#/ticket cancel: Cancel your ticket.
#In this section, you can modify messages that are related to /ticket cancel.
#This is a player command with permission node admin360.player.helpme.

# 4 Cases:
# 1 (cancel_no_ticket) : You have no opened tickets. There are no tickets for you to cancel.
# 2 (cancel_cancelled) : You have cancelled your ticket successfully.
# 3 (cancel_inprogress) : You cannot cancel your ticket because a staff is now processing it.
# 4 (cancel_feedback) : You cannot cancel your ticket because you still have not submitted a feedback.


cancel_no_ticket: '&6Admin360 &f» &7You have not submitted any tickets. Open a ticket via &6/helpme [details]&7.'
cancel_cancelled: '&6Admin360 &f» &7Your ticket has been cancelled successfully.'
cancel_inprogress: '&6Admin360 &f» &7A staff is now processing your case. You cannot cancel your ticket.'
cancel_feedback: '&6Admin360 &f» &7You still have not submitted your feedback. Was the staff helpful? (&a/ticket yes&7, &c/ticket no&7).'



############################################################
# +------------------------------------------------------+ #
# |            Counting Tickets (/ticket count)          | #
# +------------------------------------------------------+ #
############################################################

#/ticket count: Display the number of tickets.
#In this section, you can modify messages that are related to /ticket count.
#This is a player command with permission node admin360.player.count.

count_message:
- ''
- '&7&m---------------&r &6Counting Tickets &7&m---------------'
- ''
- '  &c<inQueue> &7ticket(s) in the queue.'
- '  &e<inProgress> &7ticket(s) in progress.'
- '  &a<completed> &7ticket(s) awaiting feedback.'
- ''
- '&7&m--------------------------------------------'
- ''



############################################################
# +------------------------------------------------------+ #
# |            Purging Tickets (/ticket purge)           | #
# +------------------------------------------------------+ #
############################################################

#/ticket purge: Remove all the tickets from the database.
#In this section, you can modify messages that are related to /ticket purge.
#This is a staff command with permission node admin360.admin.purge.

purge_message:
- ''
- '&7&m---------------&r &6Purging Tickets &7&m---------------'
- ''
- '&7Purged &c<purged> &7tickets.'
- ''
- '&7&m--------------------------------------------'
- ''



############################################################
# +------------------------------------------------------+ #
# |  Leaderboard and Stats (/ticket leaderboard, stats)  | #
# +------------------------------------------------------+ #
############################################################

#/ticket leaderboard, /ticket stats: Honor points leaderboard and statistics.
#In this section, you can modify messages and settings that are related to /ticket leaderboard and /ticket stats.
#This is a staff command with permission node admin360.admin.leaderboard and admin360.admin.stats.

#default_leaderboard_output: Set the number of records shown.
default_leaderboard_output: 5

leaderboard_title:
- ''
- '&7&m-------------&r &6Staff Leaderboard &7&m-------------'
- ''

leaderboard_message: '    &6<name>: &f<points> &7honor points'

leaderboard_footer:
- ''
- '&7&m--------------------------------------------'
- ''

stats_message: '&6Admin360 &f» &c<name> &7has &6<points> &7honor points.'



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

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