Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated last month
All versions
1.4.1
Release
BetterPunish 1.4.1last month 128
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.11
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
BetterPunish v1.4.1 - Paper 26 compatibility
BetterPunish 1.4.1 updates the plugin for the new Minecraft calendar-versioned Paper releases while retaining the Paper 1.21.11 baseline.
Compatibility
- Stable support: Paper 1.21.11, 26.1, and 26.2
- Preview verification: Paper 26.3 build 15 (alpha)
- Java 21 on Paper 1.21.11
- Java 25 on Paper 26.1 and newer
- One Java 21-bytecode JAR across the supported range
- Paper only; Spigot is not supported
Compatibility fixes
- Updated the compile API to stable Paper 26.2 build 124
- Replaced deprecated legacy chat, sign, book, sound, broadcast, color, display-name, and anvil APIs
- Updated Adventure-component handling for Paper 26.2's Adventure 5 baseline
- Moved asynchronous player and server access back onto the main server thread where required
- Kept
plugin.ymlat API baseline 1.21.11 to preserve the older supported server
Reliability and GUI fixes
- BetterPunish now starts correctly when optional LuckPerms is not installed
- Inventory drag actions touching a BetterPunish GUI are cancelled
- Click, hotbar, shift-click, double-click, and offhand interaction paths remain cancelled by the GUI click guard
- Report and suspect middle-click actions now open the actual punishment history GUI instead of invoking an unregistered command
- Invalid punishment-dashboard page arguments now return a clear error
No configuration or storage migration is required.
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:61dNEC9e:VFnTc2F8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:61dNEC9e:VFnTc2F8"
}

