Tags
Creators
Details
10.2.9
Compatibility
Changes
CraftersStaff v10.2.9 – Unified Language & Official PlaceholderAPI Support
This version 10.2.9 is focused on polishing the plugin's foundation for international networks and better preparing integration with other server systems.
-
🌐 Unified Default Language – English
- Fixed the language selector to always respect the value configured in
general.languageinsideconfig.yml. - The internal default language is now English (
en), with normalization of invalid codes and better fallbacks when unsupported values are used.
- Fixed the language selector to always respect the value configured in
-
🖥️ Improved Branding & Console Messages
- Fixed startup branding colors in console; legacy color codes
&now display correctly. - All console messages respect the configurable prefix defined in
general.prefix, maintaining a consistent visual identity in server logs.
- Fixed startup branding colors in console; legacy color codes
-
📊 Official PlaceholderAPI Support (
cstaffexpansion)- New official PlaceholderAPI support via the
cstaffexpansion, designed specifically for HUDs, scoreboards, TAB and staff network menus. - Includes placeholders to display the player's Staff Mode and Vanish status, as well as staff counters both at individual server level and across the entire network (proxy).
- The system is ready to work in hybrid Spigot/Paper + Velocity environments, leveraging the
craftersstaff:mainmessaging channel to request and receive staff counts from the proxy when needed.
- New official PlaceholderAPI support via the
In summary, CraftersStaff v10.2.9 strengthens the plugin's internationalization, improves the administration experience in console and opens the door to more advanced integrations with PlaceholderAPI in professional network configurations.
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:UAUjFHnX:fU0PCOJj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UAUjFHnX:fU0PCOJj"
}

