Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last week
All versions
1.5.3-c550cc8
Alpha
FP's AntiFreecam 1.5.3-c550cc8last week 668
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
FPAntiFreeCam 1.5.3
New
- Line-of-sight Anti-Xray. Ores are sent to the client as the rock around them (stone, deepslate, tuff, netherrack, ...) until the player can actually see them. Xray packs and Xray mods see plain rock where the ores are hidden.
- Each check tests every exposed ore face from the player's eye, and also from the F5 front/back camera, so third-person view doesn't reveal or hide anything wrongly. A camera clipped into a wall can't see through it.
- Ores within a few blocks are always shown, and ores next to a block you break are checked straight away, so you never mine into fake stone.
- Once seen, an ore stays real until you move away (
forget-distance), so nothing flickers back to stone. - Per-world ore lists and height ranges under
anti-xray.worlds. Defaults cover all Overworld and Nether ores; the End is off. - Works alongside FreeCam protection and Smart Fill. Smart Fill never uses a hidden ore as fill material.
- Split bypass permissions.
fpantifreecam.bypass.freecamandfpantifreecam.bypass.xraybypass one feature each.fpantifreecam.bypassstill bypasses both, and setting one of the new nodes tofalseturns that part back on (e.g.bypass+bypass.freecam: false= Anti-Xray bypass only). - Cleaner
/fpac stats. Grouped into Server / Protection / Smart Fill / Anti-Xray / Traffic sections, one setting per row, no chat prefix on every line, short numbers (12.3k).
Performance
- Reveals are sent as block-change packets grouped per chunk section. Anti-Xray never re-sends whole chunks.
- Chunk sections that contain no hidden ore are skipped without scanning their blocks.
- Visibility checks run every 5 ticks with a per-player step budget (
ray-budget), nearest ores first, and are skipped while the player stands still and doesn't turn. - Bedrock (Geyser) players get at most 256 reveals per check, so Geyser isn't flooded.
Bug fixes
- Smart Fill and Anti-Xray now share the same line-of-sight code, so both use the same safety checks (no chunk loads, no reading other Folia regions).
- An error in Anti-Xray can no longer stop the plugin from enabling, or skip FreeCam hiding on a packet.
Notes
- Config updates to
config-version: 5.4automatically. A newanti-xray:section is added; your existing settings are kept. - OPs no longer bypass protection automatically.
fpantifreecam.adminno longer includes any bypass permission. Givefpantifreecam.bypass(or.bypass.freecam/.bypass.xray) to staff who should be exempt. - If Paper's built-in anti-xray is enabled in a world, the console warns you. Turn one of them off, since running both stacks fake ores on top of ours.
- Tested on Purpur 26.2. Spigot and Folia are supported but not tested on a live server yet, so please report any issues.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:NodGIhss:fqU8ESPH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NodGIhss:fqU8ESPH"
}

