- Cape not destroyed on player despawn
- View distance sendpacket
- Cape does not despawn on player left the view range far
- cape still visible, on player body update (water, elytra, bed)
- Official mojang cape is visible on world change
- Performance improvement, using movement detection to avoid heavy calculs

No longer issue with cape height position when using viaversion
Also fix cape despawn issue using viaversion or not

- Prodigycape is now compatible with 1.21
- The permission system for prodigycape apply <user> <cape> was no longer working
- a new command is introduced: prodigycape force apply <user> <cape>, it's admin command to apply a cape even if this user does not have the permission

- official mojang cape were visible
- updating player visibility was causing unmounted cape
- passengersapi is now a soft depends

Thank you for all early adopters, you are the key of the success of this plugin, we were able to fix many issues reported on github !

I would like to add a special thanks to @MaximDe who became my main and most active contributor !

Thanks to him we made amazing improvements !

You can check all the issues fixed here:
https://github.com/corentingosselin/ProdigyCape/issues?q=is:issue+is:closed

For this update you need 2 dependencies, you can remove protocollib if you are not using for any other plugin:

https://www.spigotmc.org/resources/packetevents-api.80279/
https://www.spigotmc.org/resources/passengerapi-entity-passenger-bug-fixes-more.117017/

You can find the issues fixed here:

https://github.com/corentingosselin/ProdigyCape/issues/4
https://github.com/corentingosselin/ProdigyCape/issues/5

Fixed:

New cape apply does not remove previous cape:
https://github.com/corentingosselin/ProdigyCape/issues/1

Change world = cape no longer visible
https://github.com/corentingosselin/ProdigyCape/issues/2

Thank you jurvyy from github for your report