New Release: Proxy Support and Cache Rewrite

Proxy Support

We are happy to announce that our plugin now supports proxy servers, including Velocity and BungeeCord! To use the plugin on your proxy server, simply download the latest release and place it into the plugins directory of your proxy. Ensure that the PacketEvents plugin is also installed on your platform. Once set up, the plugin will automatically take care of all your backends. You won't need the plugin on your backend once installed upon the proxy.

Cache Rewrite

This update also introduces a significant overhaul of our cache management system. Previously, a single cache was maintained for the entire server, retaining entities until they were explicitly removed. This led to inefficiencies, especially when entities remained cached unnecessarily due to the potential for client-side demand.

To support proxy servers, we completely rewrote the cache manager. Now, each user has their own cache, addressing the challenge of server-specific entity IDs and user server-hopping. This user-centric caching relies entirely on packets, eliminating the need for platform-specific methods to track entity spawning and removal. Entities are promptly removed from the cache when your client receives a packet indicating they are out of render distance, etc, dramatically improving cache size and lookup speeds.

With this new approach, we no longer require the Caffeine Library, reducing the plugin size from 1.06MB (1006KB) to a mere 74KB. As the saying goes, "Size doesn't matter, but rather what you do with it." We have surely taken that seriously. 1 Jar, 3 Platforms (and forks), hundreds of different versions across all platforms. All of that is in a single jar of 74KB.

Acknowledgments

This release wouldn't have been possible without the invaluable contributions of the following individuals:

• @Tofaa2: Instrumental in supporting Velocity and redesigning the cache system.
• @Booky10: Provided essential tips and insights for developing the packet-based entity tracker.
• @Abhigya: Assisted in redesigning the Gradle Build Chain.
• @AlexDev: Offered numerous optimization suggestions and guided the configuration manager rewrite.

Thank you to everyone involved for your support in making this release possible!

Kind regards, Bram