Fix /usepack adding packs instead of overriding existing ones in 1.20.3+ (now works the same way as before again)
Fix /resetpack command adding the pack if one was stored instead of replacing existing ones like before on 1.20.3+.
Changed the communication between the proxy and backend servers to improve maintainability and security.
There is now a key required on the Minecraft side for the information forwarding to work. This should be generated and populated automatically on first join through the proxy but you can also manually define it in the key.yml file on the key as a string.
(If you don't run a proxy then the file should automatically be set to key: "" the second time any player joins which means no plugin messages are accepted. Of course you can prepopulate it with that value.)
1.12.6.1 hotfix: Fix automatic key generation on Bungee
Unifies how pack statuses are forwarded in a proxy network. Now any combination of Spigot + BungeeCord/Velocity sending packs in both directions should also forward all statuses between the other plugin if FRP is installed on both. This means that actions are now executed on the Minecraft server as well as the proxy at all times! (Previously only some were executed based on the combination) Please test your setups if you use actions on both Spigot and the proxy to see if this impacts you!
If you do run into issues then I suggest testing out the pack-actions added in the 1.12.0 update. With them you should be able to properly specify which pack should cause which action to run.
Fixed that the UUID wasn't properly read when running FRP on Bungee and a backend server sent a pack (via plugin or server.properties) which would cause a packet reading error.
Please note that running ViaVersion on the proxy might still break it. Move them to the Spigot server for best compatibility!
Fixed packs not being (easily) removable when sending them from Velocity due to missing UUID in resource pack packet.
Fixed new statuses causing errors on Velocity and generally unified how pack statuses were parsed from packets/platform-dependent API methods to avoid such error s in the future
Fixed that running the plugin on an outdated Velocity would print a non-descriptive error. It now prints a proper error message indicating that at least Velocity 3.3.0 is required.
Fixes issues with the pack status (a possible NPE when no/an unknown UUID is sent as well as a different behaviour between Velocity and the other platforms)
Changes the Bedrock-client detection so that it will always use the Geyser or floodgate APIs if they are installed. It will only fall back to checking for an XUID if neither of them are installed.
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!)
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
Added forwarding of all pack statuses to the backend server when running behind a proxy (when using the API the FRP
ResourcePackStatusEvent should be used instead of the Vanilla one)
This also means that all actions configured in FRP on the backend server are now properly executed.
Fixed an issue that prevented integrations with certain auth plugins to work properly when used together with a proxy
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
