After a long time I finally got around to invest time into drafting up a new release so here it is. Below will be a list of the major changes that were already included in the latest development builds, see the commit history since the last release for a detailed list of changes!

Major additions and changes

• Support Minecraft versions up to the current 1.21.8 release
• This includes multi-pack support starting with 1.20.3 clients (defined via the packs option). Older client versions will still only apply one pack (the first from the list)
• On 1.20.3 or newer clients packs are now removed directly when they should no longer apply rather than the empty pack being used to reset it
• Added a config option to toggle the appending of the hash to the pack's url (append-hash-to-url, enabled by default to keep old behaviour. On modern Minecraft client versions this should no longer be necessary as MC-164316 was fixed in 1.20.3)
• Added the ability for the plugin to automatically update the hash of a pack based on a path on the machine the plugin is running on. (local-path pack config option, this does not host the pack!)
  Useful for when your webserver runs on the same machine as you Minecraft server or you can deploy the pack in your pack build setup to both your webserver and Minecraft server at the same time. Please note that if you are running in a container like Pterodactyl you need to do additional configuring to expose the files inside the container!
• Added support for more authentication plugins
• Added a warning for when certain hosts are used for packs that have been known to cause pack downloads to break (Dropbox, Google Drive, Mediafire. The last two are blocked completely)
• Added new language files: Simplified Chinese by Q2297045667 and Brazilian Portuguese by Logikoz

• Added 1.17.x support and pack format 6
• Added command to remove packs (/<command> removepack <pack>)
• Added workaround for MC-164316 by applying the file-hash to the URL. This might increase the client-side storage requirement but will correctly re-download new versions of the packs
  
• Fix editing of the global assignment via commands not saving to config
• 1.8.5.1 hotfix: Support latest BungeeCord change in packet registration

See the commit history for all changes

I have been getting numerous reports about issues while sending a resource pack to the client regarding a client freeze and how I could or should fix it so here is some info about it and the explanation why I cannot do anything about that from the server/plugin side:

When a server resource pack is send to a client it will shortly freeze after the download is complete. (Same as manually applying a local pack) This happens because the client has to reload all resources, check which resources overlap and do some other calculation and manipulation with them. (Like stitching all the textures together to a single image like they were in the first texture pack format) It's not a download issue as the client will locally cache the pack files and not re-download them if their hash didn't change.

How long this takes generally depends on the PC's performance and the size of the textures (HD packs take longer) that are used in all resource packs that the player has applied. (So even if the server resource pack doesn't contain any HD textures or textures at all the client will still completely reload all locally applied resource packs) This is something that has to be fixed in the client by Mojang for example by only reloading resources that changed. There's not a lot I can do about that other than advice people to put pressure on Mojang to improve that behaviour.

• Updated to support 1.9.4
• Fixed wrong resolving of secondary packs

If you want to support me, I now have a patreon with some rewards that might interest you

• Added an option to set the format of the pack as 1.9 introduced a new one with the version 2.
  Players with 1.8 will get packs with version 1/no version and players that connect with 1.9 get version 2 if available.
  The defined pack and then the secondary list is used to resolve which pack a player gets from the top to bottom.
• Added option to restrict a pack so that only players with the permission to use it will get it send. You can also set your own permission if you want.

Example on how the new config options could be integrated:

• /usepack without any arguments now lists all the packs a player has access to via the /usepack command.
  You should add the new message config entries "packlisthead" and "nopacks" for that to not display an error on Bungee.
• Experimental AuthMe Reloaded support. (If you want support for more authentication plugins contact me!) It tries to send the pack after a player logged in.
  You have to run World Resourcepacks on the Bukkit server and set "authme" to true in the config.yml

• Fix first secondary pack being send if the user already has the empty pack
  
• Fix a possible NPE
• Add Javadocs

You might ask yourself "Where are versions 1.5.1 and 1.5.2?": I decided to synchronize the version numbers of all three of my resourcepacks plugins. As the next version for my Force Resourcepacks plugin would've been 1.5.3 I decided to use that as the next version for all of them.

• Server secondary packs fixed
• Fixed hashes on BungeeCord not working (WorldResourcepacks only uses the Bukkit API currently and therefor can't send the hashes)
• Made compatible with World Resourcepacks
• Internal structure changes

An alternative download is always available via the github releases!

• Fix an issue with older client versions (older then 1.8) which aren't compatible with the resourcepack send packet.

Please note that this update does not make this plugin compatible with pre-1.8 clients!

There now is an enhanced version of this plugin available as a premium resource called Force Resourcepacks! Check it out if you liked this plugin and want to react on whether the player accepts your server resourcepacks or not!

• Add command to set a user's pack/your own pack (/usepack <packname> [<playername>])

• Allow reloading of config without resending packs (/brp reload [resend])

• Separate permission for /brp version and /brp reload (bungeeresourcepacks.command.reload/resend)

Added the ability to set an empty resourcepack which will get applied if the player had a pack from the previous server but the new one does not have one and there is no global pack set. It will then send the empty pack resetting the server resource pack. (The player will only have his own ones)

Please take a look at the new config options!

Fixed this issue with server packs.