Skyotickets
Skyotickets - A powerful ticket plugin !
Skyotickets is a powerful ticket plugin (a reborn of Ticket System GM). Actually, this one does not supports MySQL but supports remote control with sockets ! :D
If you have problems with messages, please DELETE your file (messages.yml). It will be re-created with original messages.
Features
- Not many commands (and sub-commands) to avoid disturbing your players.
- File based system.
- Easy to use for you and your players.
- Highly configurable.
- Tickets can save : id, priority, status, date, player, message, location and owners.
- Remote control with sockets (you can download apps here).
- Skyupdater included for auto-updating.
Commands and Sub-Commands
/ticket <priority> <text> - [Aliase(s) : /tk] - Used to create a new ticket.
/mytickets - [Aliase(s) : /mtk] - Used to view informations about your tickets.
/mtickets - [Aliase(s) : mticket, manage-ticket, manage-tickets] - Main command used to manage tickets (see sub-commands below : things in < > are optional and things in [ ] are not optional).
- view <player> <id> - View the ticket <id> of <player>.
- delete <player> <id> - Delete the ticket <id> of <player>.
- claim <player> <id> - Claim the ticket <id> of <player>.
- status <player> <id> - Change the status of the ticket <id> of <player>. You need to be an owner of this ticket.
- teleport <player> <id> - Teleport you to the location of ticket <id> of <player>. You can use /mtickets tp <player> <id> instead.
Permissions
ticket.* - Give access to all commands (and-subcommands).
ticket.view.* - Give access to all 'view' commands (and sub-commands).
ticket.delete.* - Give access to all 'delete' commands (and sub-commands).
ticket.request - Allow you to use /ticket <text>.
ticket.mytickets - Allow you to use /mytickets.
ticket.claim.ticket - Allow you to use /mtickets claim <player> <id>.
ticket.status.ticket - Allow you to use /mtickets status <player> <id>.
ticket.teleport.ticket - Allow you to use /mtickets teleport (or tp) <player> <id>.
ticket.view.ticket - Allow you to use /mtickets view <player> <id> (with the two arguments).
ticket.view.player - Allow you to use /mtickets view <player> (with only one argument).
ticket.view.all - Allow you to use /mtickets view (without arguments).
ticket.delete.ticket - Allow you to use /mtickets delete <player> <id> (with the two arguments).
ticket.delete.player - Allow you to use /mtickets delete <player> (with only one argument).
ticket.delete.all - Allow you to use /mtickets delete (without arguments).
Configuration
"config.yml"
FormattedString - The formatted appearance of a ticket.
PlaySound - If you want to play a "pop" sound when a ticket is created.
DateFormat - The format of the date which is saved in a ticket. Check this document for more informations.
NoData - When socket give no data, this text will be placed.
NoOwner - When a ticket does not have any owner.
TicketsFolder - The folder where you want to save the tickets.
MaxTicketsByPlayer - If you want to limit the amount of tickets by player. Will be reseted when you clear the player's ticket. Set to -1 if you want to disable it.
EnableUpdater - If you want to automatically update this plugin with Skyupdater.
Socket
Use - If you want to use the remote control.
Print - If you want to log informations (in the console) about connections, commands, ...
WhiteListedAddress - Adress that does not requires authentification.
Host - Usually, localhost. If you do not know what is it, please leave it as it.
Port - Do not use your Minecraft server port ! If you do not know what is it, please leave it as it.
Password - The client needs to know your password to be able to connect to your server.
Name - Name used in tickets.
Remote
A tutorial is available here.
Use - If you want to use remote database.
Host - The host of the remote database.
Port - The port of the remote database.
Password - The password of the remote database.
Log
Use - If you want log actions into a file.
File - The file in which you want to log informations.
"messages.yml"
The plugin's messages.
If you want, you can share this with others people who speak the same language than you. Just post a comment with your file's link.
Remote controlling the plugin
This plugin can be remote controlled with sockets.
If you are a developer, you can build your own application to use with Skyotickets.
If you are anyone else, you can :
- Download the Android app (You want it for iOS ? So buy me a Mac ! :D ).
Medias
Presentation of Skyotickets :
Tutorial on how to use multiple installations of Skyotickets (as of v0.5) :
If you have a YouTube channel and you have made a video for Skyotickets, feel free to post it in the command, I will add it to the page ;)
Third party services
This plugin utilizes Hidendra's plugin metrics system, which means that the following information is collected and sent 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
This plugin uses the Skyupdater too which means that the following may occur :
- Connection to curseforge.com
- Plugin version compared against version on curseforge.com
- Downloading of the plugin from curseforge.com
Before posting comments
I hate comments like this :
Quote from plantj0:What a useless and bad plugin. Whenever i edit something in the config file it just changes it back.
So please read the documentation and this before posting a comment.
If you want to make a bug report or you want a new feature please use the ticket tracker here.
Donations
Development cost time and time is the money of the life. Please feel free to donate.
@diannetea
Can you explain your request a bit more please ?
I'd like to see ticket give, and an admin take/reassign command
@HaxtorMoogle
Not MySQL, but sockets.
Any plans on using mysql to store tickets? Im looking to setup a multi server ticket system with, Plugin / server bugs reports. admin mod jails / bans player warnings and player needing help tickes
@ElementMC2
I do not understand all of your message but I have said that I will add the "Remote database" feature with sockets (but not for v0.4, v0.5 maybe).
For the sockets part is it possible to make it so I can create "accounts" or perms for the web database or somthing so that the remote will connect to a player ingame so I can make it so staff can use the remote as well as when I fire staff I just need to delete their account/create a new password every time or the ingame thing won't allow them the permission to admin tickets
@HaxtorMoogle
Done, check the pages ;)
@ElementMC2
1) I will add the feature "Remote database" with sockets ;)
2) For sure, I will look on it ;)
3) No sorry, a lot of servers want to keep the player and the id.
3 questions/additions
1) have you thought about multi server support so I can see tickets made on other servers? and then adding a line in the info like "server: <server name>"
2) can you add a priority system so staff can set tickets as pending, high priority or anything the owner names the priority and having permissions to go with them so only staff can set priorities and only high staff can take high priority tickets?
3) have it so when you do /mtickets it shows you the open tickets as well as gives each ticket created an id rather of a player and an id and then make the claim command /mtickets claim <id> and then if you want to see a player's past tickets you do /mticket info <player>. Then also the ./mtickets only shows one line of the issue. and then when you do /mticket info <ID> it will show you the complete problem and info for the ticket.
@HaxtorMoogle
Tomorrow ;)
Can you put all the application source on github along with the plugin source?
I would love to customize and add a ton of new features :)
If you want sources for the remote control applications, please post a comment here.
@Slind14
Yes but still need approval :
@Skyost
Is there already a v0.3 dev build ?
@Darthmineboy
I will implement remote control with sockets ;)
Done, you have to wait for the v0.3.
Are you going to be adding MySQL support for this plugin?