All versions
1.1.0
Release
Unstable Ban 1.1.08 months ago 272
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Version 1.1.0
Additions:
- Configurable radius for kill/join/leave messages
- Ban Reason (Killer or Natural)
- Countdown-Bar Title
- Ban duration reset after the longest/last time
Bigger Config:
# The reason the player should see if he dies
# %player% = the name of the player who died
# %killer% = the name of the player who killed the player (if there is one)
# %banCount% = the amount of bans the player has after being killed
ban-reason: "You were killed by %killer%!"
# when there is no killer, the player should see this message
ban-reason-natural-causes: "You died!"
# Should a players bans be resetet after the last/longest ban time
ban-durations-last-reset: true
# The radius in which the death message/sound will be seen/heard when someone dies. 1 = 1 Block
death-radius: 1000
# Should the plugin send a death message in the chat and/or play a sound when someone dies ONLY IN THE ASSIGNED RADIUS?
death-message: true
death-sound: true
# Only use sounds that are listet in https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Sound.html
death-sound-type: ENTITY_WITHER_SPAWN
# The title on top oft the boss bar
# Use %time% to show the remaining time until the next ban is removed
countdown-bossbar-title: "ยงcYou will lose one ban in %time%"
# Join and Leave Messages
# Should leave messages only be sent to players in a certain radius around the player who left?
leave-msg-radius-enabled: true
leave-msg-radius: 1000
# Should join messages only be sent to players in a certain radius around the player who joined?
join-msg-radius-enabled: true
join-msg-radius: 1000
Bug Fixes:
- Countdown not being removed after killing a player and being on 0 bans
- Improvement of the performance
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:yK5HP519:xbYiDqpJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yK5HP519:xbYiDqpJ"
}

