Tags
Creators
Details
1.1.8
Compatibility
Changes
StrengthSMP 1.1.8
🌐 Six languages
English · Русский · Español · Deutsch · Français · Português
Switch live with /strengthsmp lang <en|ru|es|de|fr|pt> — no restart, no reload.
Tab-completed, and the choice is saved to config.yml.
All six live in one messages.yml as top-level blocks, 196 keys each at exact
parity. Add your own language by copying a block and translating it; anything
missing falls back to English rather than printing a raw key.
🛠️ Admin commands are now translated
The entire /strengthsmp interface — help menu, every success and error, the
system-info readout, item checks — previously printed English only. It now runs
through the message system: 60 new keys across all six languages.
[ERROR] and [SUCCESS] labels localise too, which affects every command in the
plugin, not just admin ones. So do the shared no-permission, only-players,
player-not-found and invalid-amount messages, which were already translated
but never actually used by any code.
🍳 Crafting recipes now read config.yml
The recipes: section was previously decorative — recipes were hardcoded in Java
and ignored it. It is now authoritative: shape and ingredients both come from
config.yml.
Validated on load. A bad material, a ragged shape, or a symbol with no ingredient logs a clear reason and falls back to the built-in recipe, so a typo can never break crafting:
[Recipes] recipes.strength-item: unknown material 'BANANA_SWORD'
for ingredient 'P'. Using the built-in Strength Item recipe.
Existing servers: your crafting does not change. Configs still carrying the old placeholder values are migrated automatically to the recipe that was actually in force, and it says so in the console. Genuinely customised configs are left alone.
🔧 Fixes
- Startup banner read a hardcoded
v1.1.5regardless of the real version. It now reads fromplugin.ymland cannot drift again.
Compatibility
Minecraft 1.16 → 1.21.11 · Bukkit / Spigot / Paper / Purpur · no dependencies.
Drop-in upgrade from 1.1.7 — no config changes required, nothing to migrate by
hand. New message keys are added automatically; your existing messages.yml
edits are preserved.
Verified before release
Load-tested on a clean Paper 1.21.1 server alongside ViaVersion/ViaBackwards:
zero errors, zero warnings, clean enable and disable. Live checks confirmed
class switching, all six actives and their cooldowns, damage scaling
(STR −10 → 3.5 avg damage vs STR +10 → 10.2), kill-to-shard transfer, the
Monarch crown, the totem limiter capping at 2, /bind, permissions, the combat
tag, recipe loading from config, the invalid-material fallback, the stale-config
migration, and live language switching.
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:ppfnRp2Y:Exo1XJ63"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ppfnRp2Y:Exo1XJ63"
}

