Fix pack removal error and multi pack improvements​

• Fixes "pack removal not supported" error on Spigot 1.20.3/4
• Use new pack removal API on Spigot 1.20.4 when using a build where it is available
• Add more startup debug regarding the internal server version
• More improvements for 1.20.3+ multi-pack support
• Improve handling of old packets getting sent when running on BungeeCord

Click to expand...

• Fixes issues with 1.20.3/4 in some cases when running on BungeeCord
• Fixes some multi-pack related issues (especially with pack variants)
• Added per-pack status PlaceholderAPI placeholders (%frp_status_<pack>_<status>%)
• Enforce uniqueness of pack UUIDs
• Fixes an issue with the WorldGuard integration which would cause an error log on join

1.12.0 - 1.20.3/4 support and multi packs!​

• This update adds support for 1.20.3/4 on BungeeCord and Spigot (Velocity will follow once their resource pack API is done)
• Notable for networks: With 1.20.3+ clients the issue where the pack will get resent on every server switch is fixed!
• Added the ability to specify the pack uuid. If it's not set it will be automatically be created based on the pack name.
• Add ability to specify multiple global and per-world/server packs to be applied at the same time for 1.20.3/4 clients.
  This uses the new packs config option which can be added to both global or per-world/server assignments.
  Clients before 1.20.3 will apply only the first pack in that list so you need to use per-version pack variants if you want to support both!
• On 1.20.3+ clients packs are now directly removed instead of using the empty pack.
• Added support for the new 1.20.3+ resource pack statuses (only used when the player uses a 1.20.3+ client!):
  DOWNLOADED: The player finished downloading the pack
  INVALID_URL: The URL provided wasn't valid
  FAILED_TO_RELOAD: The client failed to (re)load the applied pack
  DISCARDED: The client decided to not do anything with the pack (e.g. the same version was applied already)
• Added the ability to specify status actions per-pack with the new pack-actions and first-join-pack-actions config sections for the global and per-world/server assignments. (See the default config for more info)
  This can also be modified via commands:
  /frp [globalassignment|assignment <assignment>] ...
  addpackaction <status> <action> <value>
  removepackaction <status> [<action>]
  addfirstjoinpackaction <status> <action> <value>
  removefirstjoinpackaction <status> [<action>]

Click to expand...

Fix first join actions on BungeeCord​

• Fix a bug that caused the first-join-actions to not work on BungeeCord proxies. (Make sure that you enable store-joins if you want this functionality!)

Click to expand...

JPremium support on Velocity​

• This update adds support for JPremium on Velocity

PS.: This is build number 666

Click to expand...

1.11.47​

• Updated to work with latest BungeeCord builds (these are required for it to work as backwards compatibility in this case is harder to do and doesn't make sense with BungeeCord in the first place as it supports all versions down to 1.8. If in a couple weeks you have an actual compelling reason to need this then please contact me)
• Fixed a potential timing issue when sending a resource pack on BungeeCord

Click to expand...

• Work around MC-265463 removing the pack on BungeeCord when switching servers. This unfortunately means that the pack will get loaded again on each server switch (until I can find a better solution)

Click to expand...

• Updated to be compatible with 1.20.2 (version, pack format)
• Adds support for Configuration phase resource pack packets in BungeeCord and works around an issue with packet send timings there

Click to expand...

1.11.43​