Simple Help Tickets
Simple Help Tickets
Description:Simple Help Tickets provides a simple and effective system for users to request the assistance of an admin. Starting out as a rather lightweight plugin I threw together for personal use and decided to share, it has continued to expand due to popular demand. By using /ticket a user can open a help ticket, which can then be reviewed and dealt with by an administrator. Both users and admin are able to reply to tickets to further dialogue regarding a ticket. If a user logs in and an open ticket has received a reply from an admin, they will be notified of the change.
Installation:Updating to 1.0
If you are updating to 1.0 you will need to start with a fresh database.
If you're using SQLite simply delete Tickets.db in SimpleHelpTickets plugin directory
MySQL users, delete the table SHT_Tickets in your database, it will be replaced on server start.
1. Download the .jar
2. Place the .jar in your plugins directory
3. Restart the server
Configuration:
• MaxTickets
Maximum number of tickets per user.
• TicketExpiration
Number of days before a closed ticket expires
• NotifyAdminOnTicketClose
Users with the sht.admin permission will receive a message when a ticket is closed.
• MultiWorld
If using more than one world, take/check ticket will display the appropriate world name in ticket details
• OnJoin
Display number of personal tickets to user / total tickets to admin upon join
• USE_MYSQL
Whether to use MySQL instead of SQLite output.yml
• Use to customize plugin output (Language / Formatting)
Commands:
• /helptickets - SimpleHelpTickets Menu.
• /ticket (description) - Open a help ticket.
• /tickets [-a/-c] - List Open/All/Closed tickets.
• /checkticket <#> - Check the details of a ticket.
• /taketicket <#> - Assign self to a ticket. (and be teleported to the location is was set)
• /replyticket <#> <reply> - Reply to a ticket
• /closeticket [-r] <#> - Close a help ticket.
• /delticket (#) - Delete a help ticket.
• /purgetickets [-c/-a] - Purge expired, Closed or All tickets
Permissions:
• sht.ticket - Open a help ticket.
• sht.admin - Administrate help tickets.
• sht.reload - Reload SimpleHelpTickets.
To Do:
•
•
•
•
•
Web GUI
By popular demand, a Web GUI is available for SimpleHelpTickets.
You can download it below. • SimpleHelpTickets Web GUI
Thankyou for your support! :D Recent Change-Log:
1.4
- Updated for Spigot API 1.10.2
- UPDATED: Updated for new UUID system
(Caveats: UUID not translated to player name)
- Fixed: bug when reopening a ticket
1.3.6
- FIXED: MaxTickets not limiting the amount of tickets a user can open
- FIXED: User OnJoin notification of open tickets repeating itself
- FIXED: MySQL Connection Check. (Merged PR: TheCutter)
1.3.5
- Updated extra formatting to not interfere with colour codes
- Recoded ticket.class
- Fixed "CONSOLE has opened a ticket" bug for MySQL users
- Fixed notification of admin reply on user join
1.3.4
- Added bold/italic/underline/strike/reset to output.yml
- Fixed typo in output.yml
- Added check to getconnection in mysqlconnection.java to ensure connection is established, and if not re-stablish connection before continuing.
1.3.3
- minor bugfix: Users rceiving notification about open tickets even if tickt is/are closed
- minor bugfix: Prefix removed from 'No Tickets To Display' message
- minor bugfix: Instances of getDisplayName changed to getName in closeticket & taketicket (Fronix)
- minor bugfix: A few typos in output.yml have been fixed (if your output.yml is unchanged, delete it before starting your server to generate a new one)
Does this ticket system support multiple servers ? ModReq doenst support it
@Odiumxxx
None of the "http://orphanage.dyndns.info" links work for me.
@Edgxxar That'd be Purgetickets -c
Check out the commands above.
@ursak
I'm pretty sure that SimpleHelpTickets is backward compatible with older versions of Bukkit.
Give it a try.
Great Plugin, using it a lot!
Is it possible to implement a command to delete all closed tickets at once? (e.g. /delticket -c) Would be great to have!
Thanks :D
Hi !
It's possible to use the scoreboard to display the current opened ticket ? :) and even more options as the number of tickets that we manage
Thanks :)
@Odiumxxx
Know what this means? [SimpleHelpTickets] Error: com.mysql..jdbc.exceptions..jdbc4.MySQLNonTransientConnectionE
The new webUI is only for latest simple help ticket?
I'm still running a 1.5.2 server (because of a bunch of mods not updated). Is there any way to make the WebUI work for the 1.4.6 version? Or does the 1.6.2 version work for 1.5.2?
@Darthmineboy
Then use /checkticket instead
i dont want my admins to get teleported to the ticket creation location, could u make this configurable?
@LordKainzo
1) Taketicket does just that.
2) helptickets opens the commands menu, the command structure is simple, no guessing required.
@TheAcastus
A basic Web GUI existed previously however requires updating, you may see it's return soon. EDIT: Speaking of which, here's it is now. - SimpleHelpTickets WEB GUI
@ThoLav
Are you sure you've not altered the output.yml? Beyond that CONSOLE will only be used if there isn't a player entity executing the command.
Make web system ===> If I ingame make ticket, ticket will be view on web and Admins can reply the tickets and close, delete and more... :) Can you do this please?
Looks like an interesting plugin but has some framework issues.
1) I didn't see the ability for a mod (or admin) to teleport to the location of a ticket. This is invaluable and almost a requirement for any ticket/petition plugin.
2) Good plugins have a "flat line" command base. This means that instead of having /ticket, /replyticket - etc. you would have one default command "/ticket *" and then add to it from there logically. I had to guess every time to see what a command was when it could have been just using the flat line command method.
/ticket close # ... /ticket open <msg> ... /ticket warp # ... /ticket comment #, etc.
I would strongly suggest considering this. I run a server of 100,000 users and our ticketing system works great for this.
Hello,
I didn't change the output.yml, but I'm always getting "CONSOLE has opened a Help Ticket." instead of the players name when someone wrote a ticket.
Any ideas?
I suppose that it isn't possible to notify affected by the ticket via the achievements notifications yet?
@Marium0505
Another suggestion is priorities, This will make it easier for servers to work on different levels. Different ranks should be able to deal with different kinds of tickets. A ticket of a player in need of someone to place water or lava can easily be handled by a lower ranked staff member, but a giant grief will require attention from higher ranks. By default there will be three priorities: Normal, High and Critical. These priorities are highly configurable and can also be disabled entirely. If a player submits a ticket the default priority will be Normal, so all (or only low ranked staff, depending on your configuration) staff members will get notification. As soon as the staff member notices that they will not be able to resolve the issue they can escalate the ticket to a higher priority, so the staff members with enough permission will get another notification. The command ./ticket setpending will be replaced by ./ticket escalate <id> (priority), but if the command escalate is executed the status of the ticket will become pending, to indicate that the ticket has yet to be reviewed by a higher staff member. Keep in mind that you will be able to add and delete priorities to your likings, but if you have any other suggestions on how I can improve the priority system you can submit a ticket or comment on the poll. Speaking of the poll, please cast your vote on what you think about the priority system.
Is there any chance that you can add an option whether the players have to add a subcommand (like sht to give an example) before the Simple-Help-Tickets command, to handle conflicting commands?
I would also like to suggest to add different status, like: Unclaimed (Means that the request hasn't been claimed) Claimed (Means that the request has been claimed) Unfinished (Means that the request is unfinished) Pending (Means that the player who created the request or the mod who have claimed it (or another person with permission to reply have commented the request and is waiting for an answer from the other part.) Finished (Means that the request has been finished)
I would also like to suggest that there was a final comment where the player who fixed the request needs to fill out a final comment, like "/ccloseticket finish [#] The Grief has been taken care of" to give an example.
I would also like to suggest that comments didn't override each other, but was shown as comments, so you can see all the comments and who made the comment.
Edit: Two more things: 1. Really cool plugin! 2. Please update!
This is a great plugin, but I have some small additions, it would be nice if you could do that.
- Notify a player (who created a ticket) when he joins if his ticket has been replied by a admin. (In changelog (1.3) stands that this is already included, but it isn't)
- Notify a player (who created a ticket) if his ticket has been deleted (now it's only when the ticket is closed)
Hope you are able to add these, but if it costs too much time, no problem.
Does this work on 1.5.2?
Hi, i like your ticket plugin, however i do have a feature request, would it be possible to add shorter commands? because we have so many tickets typing out /replyticket and /closeticket all the time is getting on my nerves, something like /treply and /tclose would be much much better, and also, when replying to a ticket i would love to beable to close it in the same command like "/trclose grief repaired (ticket autoclosed)" for exampe, just my 2 cents ;)
@Rmarmorstein
I know, for me, it seems sensible to make ticket plugins in minecraft as much like a normal ticket system in a website.