10.0.6 Version Compatibility

Updated CommandAPI 9.1.0 to 9.2.0, adding support for 1.20.2

10.0.5 Bug Fix

Fixed: TicketManager could not read the AVC files and silently defaulted to the internal version.
Fixed: Closed_With_Comment would cause the database conversion to fail in the TM Migrator.

10.0.4 Bug Fix + Thank You

Bug Fixes

Fixed: LuckPerms classpath not accessible to TicketManager on startup
Fixed: %SCC% and %PCC% did not properly slice off last ">" if using Kyori syntax, leading to "> message" syntax in messages.

More

V10 had a very shaky start, and I know that this has been a particularly frustrating update for quite a few people. This update brings us closer than ever before to the finish line of what I hoped V10 could be, so thank you. Thank you for sticking with me through these growing pains and providing amazing support and reports <3

10.0.3 Bug Fix

Fixed: PaperMC updated their new paper-plugin.yml format, and in that format, one of the changes made caused LuckPerms to load immediately after TicketManager instead of before. The target keyword has been rectified.

10.0.2 Bug Fix

A bad merge request caused certain changes to be rolled back. This caused CACHED_H2 to have improper database names.

Also, a bug has been fixed with the migrator tool where it failed for users not using the discord bot.

10.0.0 Major Update (2nd launch)

TicketManager 10: Modularization Update

This is LONG-awaited update, but V10 is finally here! I'm so happy that I could finally finish this many months-long rewrite, so let's get right into things!

Important Information Prior to Update

SE 10 brings two breaking changes:

• New database schema: V10
• The Discord Bot and all database types except for CACHED_H2 were externalized and have their own new configs.

TM Migration Tool

This major version has a special migration plugin to make the transition seamless. It will load before TM SE and automatically migrate your config settings to the correct new config locations. It will also migrate all tickets to the new schema. To use, just add it to your plugin folder-- no configuration necessary. Make sure to delete it once it's complete, but it's smart enough not to run again so long as you don't delete ~plugins/tmmigrator/result.SUCCESS

Features

New API

TicketManager finally has an API for users to hook into! Currently there are 2 systems:

• Events: Allows developers to listen to events
• Extensions: Provide more in-depth control over the plugin by providing some sort of implementation

Currently there's only one event which listens for ticket creations/modifications and one extension which allows new database types to be added. Developers who wish to code for TicketManager can see information on the API on its GitHub page.

Modularization

Modularization was a large focus on this update. Certain core features are no longer a part of the core plugin:

• Discord Bot (GitHub link)
• Non CACHED_H2 databases (GitHub link)

Instead, these features are now addons which allow users to choose what they need. Download these on their respective GitHub pages.

These new addons live in the new ~plugins/TicketManager/addons folder, allowing server owners to keep track of their TM addons without cluttering their main plugin folder.

Command Overhaul

New Command Parser

TicketManager now uses CommandAPI and Brigadier to handle command parsing. The entire command feedback system has been overhauled to provide much better feedback for syntax and validity.

Redesigned Search Command

The search command has been completely rewritten. It reads much more like a sentence now and has tons of new search options depending on the command. For example: /ticket search where time < 4 day && creator != HoshiKurama searches for tickets created by anyone other than me within the last 4 days. Much easier to read than the previous search command! Additionally, the new command parser system is far smarter and will help you out a lot with tab completions for searches.

Changes to Assign Command

The assignment command from before did a lot of magic behind the scenes. It would attempt to determine the best assignment type and always succeed, even when you might not want it to. For example, if you assigned a ticket to a user but misspelled their name, the assigned user would not receive notifications for it.
Now, users must explicitly state the assignment type. For example: /ticket assign user HoshiKurama will search for any Minecraft user with the name HoshiKurama and fail if one does not exist. This ensures assignments are as intended.

Localization Updates

Sadly with this update, simultaneous localization has been removed. The feature required manual parsing, and the new system handles a fair amount of the parsing. Thankfully, I don't anticipate that this will affect any servers as most tend to prefer one language at a time.

Spigot Receives Proxy Support

The artificial limitations in place for Spigot have been removed. Users can now use Waterfall or Velocity with Spigot servers.

Final Notes

I sincerely apologize for the mess that was this update. There were a LOT of setbacks along the way, as well as multiple rewrites / new code of various sizes and difficulties. Some of you may remember the initial V10 launch, which was a disaster to say the least. There were so many undiscovered problems and enough poor decisions made that I pulled V10 to do more work. I received lots of helpful feedback, which lead to the new migration tool and the addons folder. Now, V10 is a much better product that I hope everyone loves. If you have any feedback or issues, please let me know in the Discord server!

Documentation is still a work in progress for everything, so expect that to be slowly churned out.

Thank you for being patient, and I sincerely hope everyone loves this new chapter in the plugin's life. <3

9.0.1 Bug Fix

• Fixed bug where the Discord bot could not send comment updates (Note: users with proxy server bot should also update to PBE 2.1 here).

Version 9 Release + Important Information

TicketManager has reached V9! Firstly, thank you very much everyone who has supported my product to this point. It's something I take great pride in and will continue to work on in the future. With that said, here is the update.

NOTE: If you read nothing else, please scroll to the "Important Information" and give it a look. This update does have breaking changes.

Version 9: Expanded Platform Update

The original goal for this major update was to expand the number of platforms supported. IE: Sponge support and the ability to run a single TM:SE instance on Velocity. However, this has been pushed to a future 9.X release due to some pressing matters that need a hotfix. I already had a new feature written and tested, so it made sense to release now with the new feature instead of wait.

New Feature: Proxy Discord Bot

For networks using TM in proxy mode, the only way to use the discord bot was to create a bot for each server. This has been rectified in V9. Now users can enable a single Discord bot on the proxy. The individual servers can forward the bot notifications to the proxy, thus only needing one bot.
To enable this, enable the discord bot on the proxy using the new config file, then, on the standalone editions, (a) enable discord, and (b) enable discord passthrough to proxy.

Important Information

This update begins a process of consolidating certain internals. As part of this effort, certain things are being standardized. Luckily, permission node standardization already occurred several major revisions go. By contrast, proxy channels did not yet exist during this effort and thus escaped standardization. This update resolves this discrepancy, and thus breaks compatibility with previous PBE versions. The following summarizes the changes:

• TM:SE and TM:PBE experienced a proxy channel standardization which breaks compatibility.
• TM:SE 9.0.0 must use TM:PBE 2.0
• TM:PBE only works with TM:SE 9.0.0

Please make sure to update your PBE if you intend on updating the PBE.

8.5.0 Semi-Feature Update

This version mostly updates all dependencies to the latest versions, but it does add one feature asked about many times

MySQL 8 Support

Previously, users with MySQL 8 could not use TicketManager at first. This was a limitation with the library TM uses to handle MySQL connections, and the only workaround was to change your database's authentication method. Not only was this complicated and annoying to do, it was also less secure and sometimes not possible.

However, a new update was released which provides support for MySQL 8's new authentation method, and so now this limitation has been removed.

8.4.2 Bug Fix

• Fixed bug where using /ticket history on users with no tickets made resulted in an error
• Updated dependencies