Tags
Creators
Details
1.0.1
Compatibility
Changes
JustAFK 1.0.1
This release significantly expands backwards compatibility while keeping Paper 26.2 as the primary platform.
Compatibility
- Paper: 1.8.8–26.2
- Purpur: 1.14.1–26.2
- Folia: 1.19.4–26.2
- Spigot and Bukkit: 1.8.8–26.2, with best-effort runtime support
- Sponge and proxy platforms: Not supported
Changes
- Targeted Java 8 bytecode to support older Minecraft server versions.
- Kept Paper 26.2 as the primary compilation target.
- Added compatibility compilation against the Spigot 1.8.8 API.
- Added bytecode comparison between the Paper and legacy API builds.
- Improved compatibility with older Bukkit configuration APIs.
- Preserved Folia-aware scheduler support without introducing a hard Folia dependency.
- Added compatibility and regression tests.
- Confirmed that the plugin has no external runtime dependencies.
- Preserved the existing AFK behaviour, commands, permissions and configuration format.
Validation
The release build passed all 11 automated tests and compatibility checks.
Runtime smoke tests were completed on:
- Paper 1.8.8
- Paper 26.2
- Purpur 26.2
- Folia 26.1.2, the latest public Folia build available during testing
A public Folia 26.2 server build was not available during testing. The plugin uses the appropriate Folia scheduler API and is prepared for 26.2, but that specific server version has not yet been runtime-tested.
Updating
This is a drop-in update from JustAFK 1.0.0. Existing configuration files remain compatible.
The plugin JAR uses Java 8 bytecode, but you must still use the Java version required by your chosen server. Paper 26.2 requires Java 25.
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:r9gMsdyf:F2bkr6bf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:r9gMsdyf:F2bkr6bf"
}

