Screenshot 1 of 2. Top-down view of a stone platform with green dotted rays and arcs radiating from a player, showing Raycasted Anti-ESP visibility checks.
What Raycasted Anti-ESP works with.
| Platform | Java Edition |
|---|---|
| Loaders | Folia, Paper, Purpur |
| Minecraft versions | 1.20.6, 1.21.11, 26.1.2, 26.2, 26.3 |
Raycasted Anti-ESP is a packet-based plugin for Paper, Folia and Purpur that hides entities, players and tile entities (chests, banners, signs) from anyone who could not legitimately see them. Packets are blocked before they reach the player unless the block or entity has been confirmed visible. That limits ESP, x-ray and freecam, and blocks pie-ray outright. It runs on the server only, and players join with a normal setup. It was formerly called Raycasted Entity Occlusions.
Server software and versions
- Folia: Minecraft 1.21.4 to 26.3. The newest build requires PacketEvents; some builds for 1.21.4 to 26.2 need no dependencies.
- Paper and Purpur: Minecraft 1.20.6 to 26.3. The newest build requires PacketEvents; some builds for 1.21 to 26.2 need no dependencies; builds for 1.20.6 to 1.21.3 need no dependencies.
- Bukkit and Spigot: Minecraft 1.21, builds stopped after July 2025. The newest build needs no dependencies, optionally PacketEvents.
What it is used for
- Stopping ESP cheats, the plugin's primary purpose.
- Blocking pie-ray, so nobody can locate underground bases or farms.
- Keeping mini-maps and cheat mods from showing entities a vanilla player could not see.
- Easing load on low-end devices by culling hundreds of armour stands, item frames and banners inside megabases.
- Trimming entity packets when keep-client-entity-when-hidden is set to true. The saving is measurable, but unnoticeable unless bandwidth is tightly limited.
Installing and choosing a release
- 1.Install PacketEvents first. It is required for all features, because packets are intercepted and rewritten.
- 2.Place Raycasted Anti-ESP in the plugins folder, as covered in the plugin install guide, then restart.
- 3.Adjust the options listed at raycastedantiesp.cubi.games/config.
The stable 1.x releases keep the old Raycasted Entity Occlusions name. The rewritten alpha line, numbered 0.x, uses the new name, is faster and more correct, and is strongly recommended over stable 1.6.5. Folia support arrived with that rewrite. Only Paper and its derivatives are supported by it, Spigot is not.
Permissions
- raycastedantiesp.command (OP by default) allows /raycastedantiesp, alias /antiesp, and its subcommands.
- raycastedantiesp.updatecheck (OP by default) sends update notifications.
- raycastedantiesp.bypass (false by default) shows everything to the holder.
Trade-offs
Entities pop into view with a short delay once they become visible. Config options soften this, but each one weakens the plugin's ability to block cheaters. Translated display entities are shown and hidden by their real location, not where they render. A server-side Fabric port is planned but not available. For free-camera mods on the player side, see Freecam.
Questions about Raycasted Anti-ESP.
4 questions
Does Raycasted Anti-ESP stop freecam and pie-ray?
It is designed to. Packets for entities and tile entities never reach a player until they are confirmed visible, so freecam, x-ray and ESP tools have little to show, and pie-ray is blocked completely. Options that reduce pop-in also weaken the blocking, so tuning is a balance.
Does Raycasted Anti-ESP work on Spigot?
Current releases support Paper and its derivatives, including Folia and Canvas, but not Spigot. Older Bukkit and Spigot releases exist, yet they stopped in July 2025 and are no longer updated.
Does Raycasted Anti-ESP need PacketEvents?
Yes for current releases. PacketEvents is required for all features, because the plugin intercepts and rewrites packets so players never learn about anything hidden from them. Some older releases need no dependencies, so check the requirements of the file you pick.
Should I give staff the bypass permission?
No. The raycastedantiesp.bypass permission is meant to make everything visible to its holder, but it is currently bugged and does not work as intended. It is off by default, and it should stay that way until it is fixed.








