Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last week
All versions
0.4.0-Beta
Beta
0.4.0-Betalast week 28
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.6–1.21.11
Platforms
Folia
Paper
Purpur
Changes
0.4.0-Beta
New Features & Major Changes
- No new modules in this release — this is a reliability and hardening update.
Fixes & Hardening
- Core: Module reloads and toggles now handle asynchronous work, persistence and listener/command lifecycles more safely.
- Teleport: RTP samples random destinations across the configured world area and checks for safe landing spots; search and warmup state handling is more robust. TPA requests and arrival handling were hardened for Paper/Folia scheduling.
- Moderation: Improved database error handling and consistency during concurrent ban operations; added validation and clearer feedback for self-bans, IP addresses and empty result pages.
- Vanish: Improved visibility consistency across joins, quits, respawns and other lifecycle events, including Folia scheduling.
- Plugin metadata: Permission nodes and defaults are now documented in
paper-plugin.ymlalongside the runtime registrations.
Config Changes
- moderation.yml includes additional messages for database errors, self-bans, invalid IP addresses and empty pages.
- Existing module configuration versions are unchanged; no configuration version migration is required.
Tested Environments
- Paper 26.1.2 (local end-to-end tests with VitaminMCP)
It should work on Paper, Purpur and Folia Servers for 1.21.6 to 26.3! Spigot is not supported.
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:yfx0z1Sw:yfSYPh63"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yfx0z1Sw:yfSYPh63"
}
