Performance Improvements about serverauth HOT 6 CLOSED

Using PlayerMoveEvent isn't the main problem. The problem is that you are unnecessarily querying whether a player is registered, while that can be cached (at least for this session) in PlayerMoveEvent.

from serverauth.

Yes, you're right! Authenticated users are stored in an array in memory. Accessing it only, instead of doing also Disk I/O or database queries is 99% faster. Then, registration check in each event is useless because if the user is authenticated automatically it's also registered

from serverauth.

@legoboy0215 About the PlayerMoveEvent why should I make a task instead of using PlayerMoveEvent?

from serverauth.

Check PM forums. @PEMapModder wrote a detailed post about this, with performance concerns. I'll try to make a PR, but I haven't got time yet :)

from serverauth.

@legoboy0215 I wrote that when you asked which one was better, and you might not be running the handler per tick. But the difference isn't really that big in this case ;)

from serverauth.

Fixed in v2.12

from serverauth.