Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 weeks ago
Updated last week
All versions
1.1.0-RELEASE
Release
1.1.0-RELEASElast week 198
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
1.21.4–1.21.11
Platforms
Folia
Paper
Purpur
Changes
Menus for homes, warps, kits and baltop, stored player reports, and a combat tag. Tested on Paper and Folia 1.21.11.
Added
- Menus.
/homes,/warps,/kitand/baltopopen a paged chest menu when a player runs them without arguments. Each one can be switched back to the chat list undermenusin config.yml. The console still gets chat. - Reports.
/report <player> <reason>files a report that is kept in the database. Staff withserversystem.report.notifyhear about it at once, and/reportslists what is still open, withclose <id>andtp <id>./reporthas a 60 second cooldown by default. /helpop <message>calls staff without filing a report.- Combat tag. Hitting another player, or being hit, by melee, projectile
or TNT, tags both for 15 seconds. While tagged, the commands under
combat.blocked-commandsand their aliases are refused, survival flight is switched off, and logging out kills the player. Clicking a menu entry does not get around it.serversystem.combat.bypassis not given to operators.
Fixed
- Language files unpacked by an older version showed the keys a newer one
added as raw text, such as
command.report.self. Missing keys are now filled in from the jar, which is what the fallback was meant to do. - An unreachable MySQL server printed a stack trace instead of the short "check the storage section" message.
/skullwith a name the server has never seen froze the tick while Mojang was asked about it. The profile is now resolved off the server thread./tpahereread the requester's position from the wrong region thread on Folia. It is now read on the requester's own thread.
Changed
- Built against Paper 1.21.11. Teleports no longer link against
TeleportFlag.EntityState, which Paper has marked for removal. - HikariCP 7.1.0, sqlite-jdbc 3.53.4.0, mysql-connector-j 26.7.0, bStats 3.2.1, PlaceholderAPI 2.12.3.
Optional dependencies
Any compatible version
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:3jGmDvjD:wxcQRT31"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3jGmDvjD:wxcQRT31"
}

