All versions
1.6
Release
Tub's Status Plugin 1.6last year 326
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
Paper
Purpur
Spigot
Changes
New Features
- Introduced
/tspAdmin Command:- Added
/tsp(Tub's Status Plugin) as the primary command for plugin administration and information. - Includes subcommands:
/tsp reload,/tsp setmaxlength,/tsp resetmaxlength,/tsp info,/tsp help. - Admin-only status management:
/tsp setstatus <player> <status>,/tsp remove <player>. - Many
/tspcommands are now console-executable.
- Added
- Enhanced Group Permissions:
- The
statusGroupssection inconfig.ymlnow supports a specificpermissionslist for each group, allowing for more granular access control.
- The
- Configurable Logger Level:
- Added
loggerLeveltoconfig.yml(options: DEBUG, INFO, WARN, ERROR) to control plugin message verbosity in the server console.
- Added
Improvements & Changes
- Refined Command Structure:
- The
/statuscommand is now primarily for players managing their own status and for admins directly managing other players' statuses. - Administrative tasks are consolidated under the new
/tspcommand.
- The
- Admin Status Setting in Group Mode:
- Admins with
StatusPlugin.admin.setStatuscan now set custom statuses for players via/tsp setstatusor/status, even whengroupModeis active.
- Admins with
- Improved Update Checker:
- The update checker now uses
UpdateUrgencyfrom Modrinth for more informative admin notifications.
- The update checker now uses
- Tab Completion Enhancements:
- Added and improved tab completion for both
/statusand/tspcommands, suggesting relevant options based on context and permissions.
- Added and improved tab completion for both
- Color & Formatting Permission Handling:
- Strengthened checks for individual formatting permissions when players set statuses.
- Configuration Management:
- Upgraded
config.ymlhandling usingBoostedYAMLfor better automatic updates and versioning.
- Upgraded
- Logging System:
- Implemented a
FilteredComponentLoggerfor more controlled logging based on theloggerLevelsetting.
- Implemented a
Optional dependencies
Unavailable 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:km0yAITg:OU1MuceC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:km0yAITg:OU1MuceC"
}

