Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last week
All versions
1.5.1-9de9d9d
Alpha
FP's AntiFreecam 1.5.1-9de9d9d2 months ago 38
Compatibility
Minecraft: Java Edition
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
This update introduces significant stability improvements, memory leak fixes, cleaner shutdown handling, and Bedrock/Geyser integration improvements for the Freecam detection engine.
š Bug Fixes & Stability
- Fixed Shutdown Scheduler Crashes (
IllegalPluginAccessException):- Handled Bukkit's internal lifecycle restriction where
BukkitSchedulerrejects task registrations once disabling starts. Shutdown tasks now execute inline cleanly on both Paper and Folia region schedulers.
- Handled Bukkit's internal lifecycle restriction where
- Fixed
EntityHiderDisable Warnings:- Guarded
hideEntity/showEntitycalls during server shutdown to preventCraftPlayerdisabled-plugin warnings.
- Guarded
- Fixed Memory Leak in
entityYCache:- Entities (mobs, items, orbs) registered in the Y-cache are now periodically pruned every 60 seconds against active world entities, preventing unbounded RAM growth on long-running servers with mob farms.
- Preserved Backwards-Compatibility for 1.19.4+:
- Refactored cache cleanup to avoid relying on newer Paper-only removal events, ensuring 100% compatibility across Paper 1.19.4 through 1.21.x+.
ā” Freecam & Bedrock Improvements
- Geyser / Floodgate Compatibility:
- Bedrock players connecting through Geyser/Floodgate are now automatically identified and skipped by the translation-key probe engine to prevent unnecessary GUI packet flashes on Bedrock clients.
- Entity Status & Diagnostics:
- Added entity cache statistics to
/fpafc statusfor easier monitoring by server administrators.
- Added entity cache statistics to
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:AwjfeiGn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NodGIhss:AwjfeiGn"
}

