Tags
Creators
Details
1.4.3
Compatibility
Changes
š”ļø FPAntiFreeCam v1.4.3 ā Security & Optimization Update
This massive update introduces critical security hardening, prevents CPU thread/scheduler leaks on reload, and resolves several gameplay edge-cases such as vehicle mounting and spectator mode bypasses. Fully tested and verified on PaperMC & Folia from 1.19 up to 1.21.11 / 26.1.2.
š Security & Protection Hardening
- Pie-Chart Protection Overhaul: Removed the
isPieChartProtectionEnabledconditional guard from block entities and spawn entity packet interception. Security features (like stripping tile entity NBT data and hiding underground entity packets) are now active unconditionally while a player is in the protected zone. - Teleport Race Condition Fixed: Delayed state updates to align perfectly with the actual teleport tick. This eliminates a brief 1-tick window where client-side exploits could grab chest/ore data before the teleport fully registered.
- Surface Raycast Protection Fixed: Corrected a bug where players standing fractionally below the surface Y-level had their protection inadvertently disabled.
- Mounting Protection: Integrated
VehicleEnterEventandVehicleExitEventmonitors to instantly evaluate protection states when players enter or leave vehicles.
ā” Bug Fixes & Optimizations
- Scheduler Thread Leaks Remedied: Resolved a CPU leak during command reloads (
/fpac reload) where repeating background tasks were not tracked and canceled. All active schedulers are now safely destroyed and re-initialized. - Spectator Mode Bypass Support: Fixed a layout obscuring issue where Spectators traversing protected zones were impacted by the void replacement blocks.
- Event Listener Cleanup: Dropped redundant Bukkit event listeners to prevent internal state-racing during gamemode transitions.
- Invite Link Fix: Fixed the expired Discord invite link in documentation.
š§ Configuration
- Verified compatibility across configurations. No manual file changes required!
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:VYEE41kG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NodGIhss:VYEE41kG"
}

