1.0.0
Compatibility
Changes
1.0.0 - Initial Release
-
Java agent that patches
PluginDescriptionFile.isFoliaSupported()to always return true, allowing legacy Bukkit/Paper plugins to pass Folia's load-time compatibility check without modification.
-
BukkitScheduler compatibility layer that routes scheduler calls to Folia's native APIs:
Sync tasks->GlobalRegionSchedulerAsync tasks->AsyncScheduler -
Unsafe-based scheduler injection into CraftServer at startup, replacing Folia's stub scheduler transparently.
-
Fix for AbstractMethodError on server shutdown caused by
CraftServer.waitForAsyncTasksShutdown()callinggetActiveWorkers()through a CraftScheduler reference on a non-CraftScheduler object.
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:jPIVbCDg:66CeTWHo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jPIVbCDg:66CeTWHo"
}

