Skip to content

TicketManager 4.1.0 Feature Update

Compare
Choose a tag to compare
@HoshiKurama HoshiKurama released this 19 Jun 23:26
· 381 commits to master since this release

New Requirements:

  • Java 16+
  • Spigot/Paper 1.17+

Changelog

Internal Changes:

  • Moved to API 1.17. This means Spigot/Paper 1.17+ is required
  • Compiled to Java 16. This version will ONLY work on Java 16+
  • Slight optimisations made to ticket searches
  • All dependencies have been unshaded. Paper and Spigot 1.17 now have the ability to download required libraries at runtime. TicketManager 4.1.0 is now only 425KB! (down from 13MB)

Feature Updates:

  • Added Update Checker - Server will alert certain users on login that a new plugin update is available. This feature can be toggled in the new config section.
    -- For users upgrading from a previous TicketManager version, you will need to manually add "Allow_UpdateChecking: true/false" to their config file (unless you want to generate a new one with the added documentation). Not updating this results in a default value of false.
    -- For people who have tinkered with the localization files, note that Notify_Event_PluginUpdate has been added. Check example.yml to see the placeholders.
    -- New permission: ticketmanager.notify.pluginUpdate has been added. Users with this node will see if there is a plugin update (when there is one) on login. It refreshes every server restart or on plugin reload. Users with ticketmanager.notify.* will also see the message.
  • Added new ticket search constraints: closedby and lastclosedby! Usage can be found in the TicketManager 4 wiki

End Notes

I apologize for people having to always change their config file! The YAML parser that comes with Spigot and Paper removes all comments when modifying the file from the code, so that's why I don't do it.

For people still running 1.16, you're not missing out on much with this version, so no need to fret if you can't switch to 1.17 quite yet! TicketManager 4.0.1 is still essentially identical as far as most functionality goes.

For users who block outgoing connections, future releases for the forseeable future will also release with a self-contained JAR with all dependencies baked in!