HelpTicket
What is HelpTicket?
Most of the time on server's you will see user's persistently asking for help because someone had griefed or stolen from them. This plugin allows those users to file a ticket that staff can then look at and deal with as they see fit. If a staff member cannot deal with the situation they can assign the ticket to a staff member who can. When you port to a ticket you are not only assigned to the ticket but teleported and the situation is brought up on screen for you to see. Everything is fully customizable and documentation on this can be found here
Features
- MySQL support (through DeityAPI)
- Tickets are assigned a unique ID # which can be used to track the ticket
- Tickets can also be assigned a priority of LOW, MEDIUM, HIGH the default being MEDIUM
- Tickets will be sorted by the priority when viewing all tickets
- Fully customizable language.yml file
- Comment System
- Teleporting to location that ticket is made, viewing the situation just as the person who created the ticket
- Notifications of staff as well as members when ticket is modified
- Offline players will get notified of updates to their tickets when they join
- '/pe' being an alias for '/ticket' for people moving from PetitionPlugin to this
- If my plugin Mail is installed ticket creators will be notified of the status via an in game Mail if they are not online to see the change.
Requirements
Setup
- Place HelpTicket within your plugins folder
- Add permission nodes to users where relevant
- Optional: you can change almost every user message and formatting via the language.yml file I will update the language config wiki soon
Permissions
General Users
For general users you can add the helpticket.general.* or specify below
- helpticket.general.list
- helpticket.general.create
- helpticket.general.info
- helpticket.general.select
- helpticket.general.comment
- helpticket.general.close
Admin users
For admin users you can add the helpticket.admin.* . Or specify below, Note that admins should also have the helpticket.general.* permission as well
- helpticket.admin.tp
- helpticket.admin.assign
- helpticket.admin.priority
- helpticket.admin.purge
How to operate
After your set-up is all complete you are ready to start using it. You can use '/ticket ?' or '/ticket help' in-game to view a list of commands that can be used.
Before you start dealing with tickets you need to select one. To do this you type /ticket select <ticket-id> . After that you can deal with the ticket as you need to
Commands
User Commands
- /ticket list <OPEN/CLOSED> <page-number> - Shows all tickets
- /ticket [select/sel] [ticket-id] - Shows the selected tickets information
- /ticket info <page-number> - Shows the selected tickets information
- /ticket [create/new] [message] - Creates a ticket
- /ticket [comment/cmt] [message] - Comments on the selected ticket
- /ticket close <message> - Closes the selected ticket
Admin Commands
- /ticket [teleport/tp] - Teleports to the selected ticket
- /ticket assign [staff-name] - Assigns the selected ticket
- /ticket [priority/pri] [increase/decrease] - Alters the priority of the selected ticket
- /ticket purge [player-name] - Deletes all the tickets created by the player specified
Console Commands
- /ticket [comment/cmt] [ticket id] [ticket commenter] [message] - Comments on the selected ticket
- /ticket close [ticket id] [ticket commenter] <message> - Closes the selected ticket
- /ticket assign [ticket id] [staff-name] - Assigns the selected ticket
- /ticket [priority/pri] [ticket id] [increase/decrease] - Alters the priority of the selected ticket
- /ticket purge [player-name] - Deletes all the tickets created by the player specified
Extra Links
Source: GitHub
Documentation: Wiki
Player Made Tutorials
@deleted_7554077
delete the HelpTicket folder in plugins folder then reload. Also, make sure you have DeityAPI in plugin folder and setup properly.
Error:
2012-07-23 07:24:31 [SEVERE] Could not load 'plugins\HelpTicket.jar' in folder 'plugins' org.bukkit.plugin.InvalidPluginException: java.lang.NoClassDefFoundError: com/imdeity/deityapi/api/DeityPlugin at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:151) at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305) at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230) at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:213) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:189) at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:53) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:166) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:432) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.NoClassDefFoundError: com/imdeity/deityapi/api/DeityPlugin at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:140) ... 8 more Caused by: java.lang.ClassNotFoundException: com.imdeity.deityapi.api.DeityPlugin at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 24 more
How to fix? Thanks
@Haloclanproductions
MySQL is required to run this plugin, if you don't have an active connection through DeityAPI, then the plugin will not work for you
@zRations
Its not that you can only have one ticket, Its that the tickets are too closely linked. For example If you make one ticket with the information "Bug Testing" and then you make another with the info "Buu Testing", it will see how close they are and not allow you to create the other one. If the ticket that resembles the new one is older then a day old, then it will allow you to create the ticket. This is to prevent spam tickets as well as make people both be sure about what they are reporting and to be explicit.
The "Ticket 1 was assigned to %assignee%" can be fixed server side by changing the language and replacing %assignee% with %ticket_assignee%, however i will update the defaults.
As for the closing issue, ill look at that a bit more. Are you both a mod and the ticket owner on the server that your testing on? [EDIT: Fixed it in v 12.07.22.1, thanks for this one]
Also the whole system hasn't really changed that much. Instead of selecting and closing a ticket (for example) in one step (with /ticket close <id> <message>) you now have to have the ticket selected first. This is much faster for mods to handle tickets imo as instead of repeatedly typing out the id of the ticket, they type it out once, and then can deal with the whole of the ticket without accidentally acting on another one, before moving to the next one.
As for the whole "less informational" its actually got more information built into it now, with timstamps on everything. Also the new priority system not only takes into account the set priority from the staff, but it also takes into account how long the ticket has been open and applies a "modifier" to that so it shows higher up, regardless of its priority
I liked your old HelpTicket interface system better that you had on ImDeity Kingdoms. This new one seems a little less informational and less user friendly.
Also, with a little bit of testing, I have found a few bugs.
When assigning a ticket, a message appears "Ticket 1 was assigned to %assignee%" instead of what I assigned it to.
For some odd reason, I cannot close a ticket. I have selected the ticket, in this case ticket 1. Then tried to close it. It tells me that ticket 1 does not exist. Then in a attempt to try to close another ticket, I try to open one. When I tried another, it reverts me and tells me "Instead of resubmitting that ticket. Please use /ticket info 1" So it appears users can only have one ticket open at a time or the plugin does not register it.
what if i dont use mysql and cant use it
@deleted_7554077
Same principle except now its helpticket.general.* for general users and helpticket.admin.* for admins.... I added in the extra perms for those who wish to limit their moderating staff. However note that this is only in version 12.07.22
Permissions of HelpTicket have also changed?
I am still using - helpticket.help
Or apply same principles as with Mail like - helpticket.player.*
@deleted_7554077
Yeah i had taken it done to attempt to get the conversion script running however I wasn't able to update the new ticket system with the old ticket locations. Other then that, it was fine though so ill do another release with that in there after I awaken.
Not found "http://dev.bukkit.org/server-mods/helpticket/files/15-v12-07-22/" ?
Why not?
Sorry about the delay on the conversion of this plugin. I needed to rethink some of the logic behind how it worked in order to make the command framework more useful/noob friendly. Ill have it up by this weekend at the latest
Ou its fixed now. The Bukkit "Tickets" link wasn't working earlier got a 505 error :D
its all good now :D
Thanks
@deleted_7554077 Not sure if your speaking of an issue in the plugin or you wish to document an issue in the plugin. If its the latter you can use the Github ticket system. Otherwise you will need to explain your opinion more
@ImDeity Would it be possible to fix the ticket section?
Or if you can't get the GitHub one working enable the BukkitDev one?
Thanks!
@vanZeben
Sure I was "loud" can called the plugin "dead", but what would you call it with no response for over 2 months and bugs being "fixed" for 5 months but not being released?!
On May 6th I saw the plugin got a fix on Feb. 2012 for an bug which spams users on every login with plenty of already closed tickets. The current version stated 1.7 at this time and still the download for 1.6 was the last version to get. So I asked what about the 1.7 download. Then on Jun 5th I checked back here and saw that you were at least online on bukkitdev, so I PM'ed you about the problem and the question if the project is still up. Checking back some days later you were online again, so I though you had at least read the PM... Since there was again no response ever, I assumed you just dumped the project like so many other devs.
At least it's good to see the plugin developtment back up again since the other ticket plugins I checked out these days just didn't fit. So I'll go and check out the 1.7 now - hoping it finally fixes the login-spam.
@deleted_7554077
Yes, it is, there is a link in the OP, well there was. Imma re-add it in
Priceless update :D
Love your products. Have always used them.
Thanks for the update!
Is your server public? I'm curious to see what it looks like.
Sorry about the delay on it, I became busy with school and our (ImDeity and myself's) server. The plugin still worked for the 95% of people so I threw the fix-ups on the back-burner. There were some small issues that a few loud people were having and it is something that is fixed in this release. This plugin was and will never be "inactive" as it will be kept up to date with bukkit, but as for features that some people want to see i will be implementing something to make the system simpler. You can check the repo for information on that and its release date. It will be uploaded here as well
@weja93
Same :)
For me this is working perfectly, I am using bukkit R4.0 and HelpTicket version 1.6.
Complete 0 problems, working like a charm.