Raycasted Anti-ESP

RaycastedAntiESP v0.7.0 Paper v0.10.0

This update adds several new config options, including the ability to exempt arbitrary entity types, and significantly reduces object allocations.

• After feedback from several users, keep-client-entity-when-hidden has been changed to false by default.
• SimpleEngine has been renamed to AsyncEngine to more accurately describe it.
  • Configs will not automatically transfer over, but the default configuration of one async thread should be enough for over 500 players, so I don't think it matters.
• Added a new config option: checks.entity.excluded-types.
  • All entities in this list will be exempted from antiesp checks for all players
  • By default, entities such as projectiles, boss mobs, and display entities have been exempted. You can change this as you see fit.
• Update checks can now be disabled
  • The config has a new updates category where checks for different release channels–and sending update notifications to players with the correct permission–can be enabled/disabled.
  • This feature is a contribution from UsainSrht
• The same exempted entities system was extended to exempt all FancyNPCs/FancyHolograms entities as they cause odd issues with RaycastedAntiESP.
• Object allocations have been significantly reduced.
  • Raycasting has been modified so the JVM can fully scalarise the raycast method and the code that calls it.
  • The visibility transition queue now queues batches of 8 visibility transitions to reduce object allocations.
    • In combination, the above two changes reduce engine-thread allocations by 90%. When not loading many chunks, this reduces overall RaycastedAntiESP allocations by ~50%.
  • Netty thread allocations have been reduced by reusing the same wrappers to dispatch packets.
• Glowing entities are now always visible.
• checks.player.only-check-sneaking: false has been added. When true, players must be sneaking to be hidden.