Take A Number Is a simple efficient help ticket system. It allows server staff to easily and effectively review edit and take in game help tickets.
It's as simple as "/ticket someone griefed my house" The server staff with the proper permissions can then check and take thus ticket.
If set to true, players with the tan.admin permission will see the current open help tickets upon entering the server.
NotifyAdminOnTicketClose
If set to true, players with the tan.admin permission will recive an ingame message when a ticket has been closed.
MaxTickets
The number of tickets a player can make.
ResolvedTicketExpiration
The number of days before a resolved ticket will expire.
DateFormat
Configurable date format of the tickets.
AlwaysLoadTickets
If set to true, this setting avoids keeping the tickets in memory and reads and write to yaml directly. (not officiant, but good for cross server ticket system)
Command
Description
Aliases
/ticket-help
Help Menu.
tickethelp, tan
/ticket-open (description)
Open a help ticket.
ticket, report, rpt, tkt
/ticket-list
Review help tickets
tickets
/ticket-check (#)
Check a help ticket.
checkticket
/ticket-visit (#)
Teleport to a help ticket.
visitticket, ticket-tp, tpticket
/ticket-reply (#)
Reply to a help ticket.
replyticket
/ticket-take (#)
Take a help ticket.
taketicket
/ticket-resolve (#)
Resolve a help ticket, starts the expiration time.
I have noticed that when a user is using a nick (Essentials) the tickets will show their nick instead of their real username. And when they change nick (using /nick), they loose access to their tickets.
We have now uplodaded the support for custom messages and languages, every message can now have color and be changed to say what ever you want.
(the file is waiting approval)
Soon(TM) we will be adding sql support for cross server tickets. Look for this in the next update.
I understand that, but with the comments, I did want to make it clear, as to not get accused of copying code. :(
If you ever want to talk or collaborate on anything let me know. :)
A description of what each command does, is not "code" lol
All that shows, which I already stated is we liked your plugin but felt we could do the same thing but code it new from scratch.
At first we did keep the same descriptions for each command, but then we realized we were taking it way beyond eve the original idea, thus viewing the code now reflects that.
Again, the plugin.yml is not even close to code.
To be clear, I respect sht and the dev of that plugin, but none of Simplehelptickets code is in our current plugin, I promise. It's new, fresh, optimized, sexy code.
I prefer permission based over op based. I think that this feature is necessary because if a player was suspicious of using hack and was reported by another players, admins cannot just chat plainly in the global chat because the hacker will immediately stop using hacks. In this case admins need a private chat channel to discuss what to do with the suspicious hacker. Another case is when the admin is not sure about a certain command when resolving a ticket or when someone has found a bug that should not be known by normal players but it needs alll admins' attentions immediately, the admin chat channel would come in handy. That's just my thought and experience. If that sounds reasonable to you, that's great.
Not sure admin chat goes with support tickets, but let me think about it, as it would require defining who are admins, etc. Would it just be ops, that's easy, but if you wanted it permissions based, that's easy too, but again this would need to some how fit into this plugin, so it makes sense.
https://github.com/OdiumxXx/SimpleHelpTickets https://github.com/Jadedwolf/TakeaNumber
As you can clearly see from the source this is not a fork of the simple help tickets plugin, this is a re-write.
The only thing similar is the function and style, we kept those the same because we liked the style but the code was not done well at all.
So we started fresh but kept the sht style and functionality and adding our own too.
At no point was this ever supposed to be a fork or a competitor, I loved and still do love Simplehelptickets, but it was lacking so much and the code was really a mess, no offense <3 So we were like lets keep the same functionality but code it fresh.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hello,
Great plugin, we love it :)
I have noticed that when a user is using a nick (Essentials) the tickets will show their nick instead of their real username. And when they change nick (using /nick), they loose access to their tickets.
Is that something you can fix?
Thanks!
We have now uplodaded the support for custom messages and languages, every message can now have color and be changed to say what ever you want. (the file is waiting approval)
Soon(TM) we will be adding sql support for cross server tickets. Look for this in the next update.
Users cannot check tickets, says the ticket isn't owned by them.
Will you be adding MySQL support into this plugin so I can use it all over my network?
@Jadedwolfs
At the current moment, unless bugs are found this plugin is done. Not much if any thing needs added or changed, unless people can find something.
@Semajnad
yes, we are very much still active and using this plugin.
Is this plugin still active, I see an update for 1.5.1, but just checking the devs are still here before I start using it :)
@Jadedwolfs
That's a bad way to do it. The correct way to do it is to open bukkit.yml and add them the aliases: section.
I.e
@94miner
You can do that your self.
Open the plugin.jar and inside of it you will see a file called plugin.yml in that you can add more aliases for commands.
can you add the following commands so that even people that do not know the commands can get help please?
/helpme
/ineedhelp
Is it normal that resolved tickets stay in the /ticket-list ? Its kinda annoying.
Resolved/closed tickets should be in a separate list. and have a command like /ticket-closed to view them.
@OldDragon2A
Wow. I think it would be the first ticket plugin with a web side to it. Would be great.
@minecraftkee
We are actually testing a very simple read-only web page for it now.
@Odiumxxx
I understand that, but with the comments, I did want to make it clear, as to not get accused of copying code. :(
If you ever want to talk or collaborate on anything let me know. :)
@Jadedwolfs
er, you seem to have the wrong end of the stick here, I'm not accusing you of theft?
As I said to nhoclesnar,
"it wasn't my idea to begin with ... it's great to see the idea expanded upon by a duo with more time than my humble self."
Allow me to clarify that..
"Great to see someone expanding on this with more time than myself, nice work."
I think you should hook this into a webpage somehow and i'd use it! XD Oh what the heck ill use it now!!!
@Odiumxxx
A description of what each command does, is not "code" lol
All that shows, which I already stated is we liked your plugin but felt we could do the same thing but code it new from scratch.
At first we did keep the same descriptions for each command, but then we realized we were taking it way beyond eve the original idea, thus viewing the code now reflects that.
Again, the plugin.yml is not even close to code.
To be clear, I respect sht and the dev of that plugin, but none of Simplehelptickets code is in our current plugin, I promise. It's new, fresh, optimized, sexy code.
@Jadedwolfs
I prefer permission based over op based. I think that this feature is necessary because if a player was suspicious of using hack and was reported by another players, admins cannot just chat plainly in the global chat because the hacker will immediately stop using hacks. In this case admins need a private chat channel to discuss what to do with the suspicious hacker. Another case is when the admin is not sure about a certain command when resolving a ticket or when someone has found a bug that should not be known by normal players but it needs alll admins' attentions immediately, the admin chat channel would come in handy. That's just my thought and experience. If that sounds reasonable to you, that's great.
@nhoclesnar
Not sure admin chat goes with support tickets, but let me think about it, as it would require defining who are admins, etc. Would it just be ops, that's easy, but if you wanted it permissions based, that's easy too, but again this would need to some how fit into this plugin, so it makes sense.
@Odiumxxx
https://github.com/OdiumxXx/SimpleHelpTickets
https://github.com/Jadedwolf/TakeaNumber
As you can clearly see from the source this is not a fork of the simple help tickets plugin, this is a re-write.
The only thing similar is the function and style, we kept those the same because we liked the style but the code was not done well at all.
So we started fresh but kept the sht style and functionality and adding our own too.
At no point was this ever supposed to be a fork or a competitor, I loved and still do love Simplehelptickets, but it was lacking so much and the code was really a mess, no offense <3
So we were like lets keep the same functionality but code it fresh.