Links
Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 3 months ago
All versions
2.3.2
Release
EasyAFK Fabric/Quilt 2.3.210 months ago 81
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
Bug Fixes
- Players can now use /afk command while sitting on modded chairs (previously blocked with "cannot go into AFK whilst jumping" error)
- Auto-AFK now works correctly when sitting on modded chairs
- Fixed duplicate "cannot do while AFK" messages when interacting with entities
- Players can no longer mount horses or other rideable entities while AFK
- Attempting to sit on a chair while AFK is now properly blocked
- Shifting out of a chair while AFK now correctly removes AFK status before dismounting (prevents visual glitches)
- Jump detection now works correctly to exit AFK without native jump events
Enhancements
- Added reusable canEnterAFK() method that validates player state before entering AFK
- Both manual /afk command and auto-AFK now use consistent validation logic
- Improved distinction between chairs (allowed) and rideable entities like horses/boats/minecarts (blocked)
Technical Changes
- Updated passenger validation to check entity types (LivingEntity, Boat, AbstractMinecart)
- Chairs (non-living entities) are now correctly treated as valid AFK locations
- Added UseEntityCallback to prevent mounting entities while AFK
- Implemented tick-based jump detection using vertical velocity monitoring
- Added sneak key detection for proper chair dismounting
- Improved cleanup of tracking maps on player disconnect
- Added rate-limited message handling to prevent spam
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:VfghZPx6:LwmrYYQL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VfghZPx6:LwmrYYQL"
}

