StaffTickets
This is my first Bukkit plugin, always open to suggestions. This is a ticket system solution that saves messages in chat, that consists of trigger words in which you may add/delete in the configuration file. These messages are saved on a HashMap (persistent until server restart/reload) and can be dealt with in many ways by using the /ticket command. For a full list of brief features, scroll down below.
Love my work? Feel free to donate, anything is appreciated! :)
Donate: https://www.paypal.me/hquirit
MCStats
StaffTickets utilizes the plugin Metrics system, which collects useful information of its environment and sends it to mcstats.org:
- A unique identifier
- The server's version of Java
- Whether the server is in offline or online mode
- The plugin's version
- The server's version
- The OS version/name and architecture
- The core count for the CPU
- The number of players online
- The Metrics version
Features
- Ticket counter of all open tickets.
- Configurable trigger words.
- Compatible with essentials /helpop command.
- Enable file storage for all tickets.
- View player's tickets from their file.
Installation
Just drag and drop into your servers '\plugin' directory.
Permissions
Commands
Configuration
Source
- Source
@Madminor
You suggested that before, most if not all tickets need to be dealt with by staff in-game, rendering an online interface pointless.
It would be nice if u could add mysql support. I would like to use this on a small network, and wish to use one global database for tickets. Also my staffs can only be found on certain systems, with mysql support users who are in different servers than the staffs, can still get support.
Cheers,
Darthmineboy
Would be cool to have a online portal self hosted by this, which lets you reply to tickets from the web
2.0 uploaded and awaiting approval.
@palipali
It does instantly alerts staff members that a ticket has been created. You might of forgotten to give yourself 'staffticket.mod' permission node, regardless if the user is OP it's still required. Otherwise if that's not the problem, please let me know. At this moment, I've added both your requests and will be uploaded soon.
EDIT: Did you want the reminder's title header be configurable? Can't really make the ticket list sent along with the reminder 'configurable' to how you want it.
EDIT2: Nevermind, uploaded and awaiting approval.
@palipali
Hey,
No problem, glad you like it. And what do you mean by single message alert option? I think the feature you're looking for is right in the configuration file, where you can enable ticket reminders.
Comment if you have a reasonable feature request and I'll have a look and see what I can do. :)
@Darthmineboy
I don't see any good reason to disable teleporting ability, just don't use it simple as that.
@ZombehPig2
How often will Staff members be rewarded, per day, per month? I'm not sure if I'm able to do this as this would better require some sort of database to store the points rather than a YAML file.
Just installed it an I am liking it so far!
Few suggestions: Point system (Once someone fulfills a ticket the staff member who completed it gets a point, maybe configurable reward to the mod who had the most points?) Also maybe having a /ticket complete option? (Its realted to that ^ suggestion)
I dont like the teleporting idea, could this be disabled via an config option?
Version 1.8 is uploaded and awaiting for approval.
@xDeeKay
Cheers brah !
Congrats on 1000 downloads man! =)
Could you please make the return as in when someone types /helpop The people with stafftickets.mod will see (red)Helpop: (player)(message) Instead of just the name in red? thank you
@Gametista
Ahh some sort of questionare thing.
Example
Staff member claims a ticket. Staff member receives message prompt to teleport to the player with given co-ordinates in the message, by using /yes or /no.
Other than that, seems feasible enough, I'll have that done by next update.
@HenzQ
Not automatically. When they assign themselves the ticket, they should be able to be given the option of teleporting to where the ticket was filed, that way they can investigate even if the user isn't around.
Also, if a staff member is teleported automatically, most of the time they have ways of getting back to where they were since many servers run things like /back.
@Gametista
Well from my standpoint, I wouldn't think it's necessary to have a random selected staff member teleport to the co-ordinates of the ticket that has been triggered. There can be some possible disadvantages to this: What if the ticket was a false call, staff member was afk etc.
@HenzQ
Ha, no problem! Yes, basically the logged coordinates that were reported when that user put in a ticket is where the person answering the ticket should be sent.