Tags
Creators
Details
2.11.7
Compatibility
Changes
After a long wait and countless requests, including multiple pull requests to implement it - PlaceholderAPI is finally able to support Folia!
Additionally there has been some smaller code improvements, including updating the NMSVersion enum to include the latest 1.21.x versions.
Folia Support [#1127]
Folia support has been added, allowing PlaceholderAPI to run on Folia based servers without scheduler related issues. While we’ve tested the core functionality, we haven’t been able to verify every expansion, so some edge cases may still exist. If you encounter any bugs, please report them so we can investigate and resolve them.
NMSVersion updates
The NMSVersion enum has been updated to support the latest 1.21.x versions up to and including 1.21.10 for expansions that depend on this.
Full Changelog
Other changes
- feat: initial work on 1.21 by @darbyjack in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1067
- Added missing NotNull annotations to setBracketPlaceholders methods by @mfnalex in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1000
- Revert api links by @Funny-cube in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1098
- fix for all expansions stop loading after an exception is thrown (#1094) by @Kqliber in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1095
- Merge UniversalScheduler (Folia Support) #980 by @PiggyPiglet in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1127
New Contributors
- @mfnalex made their first contribution in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/1000
- @Anon8281 made their first contribution in https://github.com/PlaceholderAPI/PlaceholderAPI/pull/980
Full Changelog: https://github.com/PlaceholderAPI/PlaceholderAPI/compare/2.11.6...2.11.7
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:lKEzGugV:sn9LYZkM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lKEzGugV:sn9LYZkM"
}

