Tags
Creators
Details
1.9.1
Compatibility
Changes
We are thrilled to release DeathPenalty v1.9.1 (Free Edition)! This update brings our groundbreaking Dynamic Per-Player Multi-Language System with 10 international languages, native Folia multi-threading compatibility, modernized Paper Adventure GUI rendering, and hardened server shutdown lifecycle management.
โจ What's New in v1.9.1
๐ 1. Dynamic Per-Player Multi-Language (10 Languages)
- 10 Built-in Language Files: Automatically generated in
plugins/DeathPenalty/lang/:- ๐บ๐ธ English (
en_US) - ๐ฎ๐ฉ Bahasa Indonesia (
id_ID) - ๐จ๐ณ ็ฎไฝไธญๆ (
zh_CN) - ๐ฏ๐ต ๆฅๆฌ่ช (
ja_JP) - ๐ช๐ธ Espaรฑol (
es_ES) - ๐ฎ๐น Italiano (
it_IT) - ๐ธ๐ฆ ุงูุนุฑุจูุฉ (
ar_SA) - ๐ฉ๐ช Deutsch (
de_DE) - ๐ซ๐ท Franรงais (
fr_FR) - ๐ท๐บ ะ ัััะบะธะน (
ru_RU)
- ๐บ๐ธ English (
- Instant In-Game Cycling: Players can change their own language preference independently in
/dp infoor/dp configwith a single click. - Zero Reloads Needed: Interface, messages, drop alerts, and chat prompts adapt instantly without reloading the plugin or restarting the server.
โก 2. Zero-Lag Async Engine & Anti-Leak Hardening
- 20-Tick Debounce Buffer: Player language preferences are saved asynchronously, coalescing rapid clicks into a single batch database write.
- Thread-Safe Architecture: Uses lightweight
ThreadLocal<String>primitive locale codes, completely eliminatingCraftPlayer/ entity memory leak risks. - Flapping Protection: Instantly flushes pending database transactions and evicts caches when players disconnect.
๐ 3. Native Folia & Paper 26.2 Adventure Engine
- Folia Regional Multi-Threading: Tickers and death listeners run safely across
RegionSchedulerandEntitySchedulerwithout main-thread blocking. - Paper Adventure API Modernization: Replaced legacy reflection calls with native Paper Adventure components, permanently resolving
NoClassDefFoundError: MinecraftComponentSerializercrashes.
๐ก๏ธ 4. Server Lifecycle & Shutdown Safety
- Graceful Disable: Hardened
onDisable()ensures pending SQLite / MySQL writes flush completely before the server stops. - Clean cancellation for all schedulers, connection pools, and PlaceholderAPI expansions.
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:pbV6iFNe:vzTnzBkf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pbV6iFNe:vzTnzBkf"
}

