Tags
Creators
Details
0.3.0+26.2
Compatibility
Required content
Changes
AFK to Ghost 0.3.0 for Minecraft 26.2
This release adds full support for Minecraft 26.2 on Fabric while preserving the existing AFK to Ghost 0.3.0 behavior.
Changes
- Added support for Minecraft 26.2 and Java 25.
- Updated Fabric Loader to
0.19.3. - Updated Fabric API to
0.156.0+26.2. - Updated Fabric Language Kotlin to
1.13.13+kotlin.2.4.10. - Updated optional Cloth Config support to
26.2.155. - Added compatibility with Mod Menu
19.0.0-alpha.1. - Updated Fabric metadata, dependency information, documentation, and build configuration for 26.2.
- Preserved the existing input-only AFK detection without requiring packet or Mixin changes from the 26.1.2 version.
AFK behavior
Passive or externally caused movement still does not count as player activity, including:
- Knockback
- Water currents
- Pistons
- Player/entity collisions
- Vehicle movement
- Server position corrections
- Teleportation
Intentional input, interactions, attacks, chat, commands, and inventory actions wake the player as expected.
Validation
Successfully verified with:
- Java and Kotlin compilation
- Automated tests
- JAR remapping/build
- Minecraft 26.2 dedicated-server startup
- Fabric Loader 0.19.3
- Fabric API 0.156.0+26.2
- Fabric Language Kotlin 1.13.13+kotlin.2.4.10
- Both required AFK to Ghost mixins applied successfully
Requirements
- Minecraft
26.2 - Java
25 - Fabric Loader
0.19.3or newer compatible version - Fabric API
0.156.0+26.2or newer compatible 26.2 version - Fabric Language Kotlin
1.13.13+kotlin.2.4.10or newer compatible version
Mod Menu and Cloth Config remain optional and are only needed for the client-side configuration screen.
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:kscTzYpt:BTHR0uQk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kscTzYpt:BTHR0uQk"
}

