
PluginHiderPlus
A lightweight, high-performance security and brand protection suite for Spigot and Paper. Restrict administrative commands in-game (even for OPs), customize your F3 server brand, and globally replace outbound plugin messages using advanced wildcards.
6.0.1
Compatibility
Changes
Thrilled to announce a complete, ground-up rewrite of PluginHiderPlus with the release of version 6.0.x. Now available on Modrinth.
This update is a huge comeback and has been built following strict, modern software engineering principles and fully verified using automated unit/integration test suites to ensure absolute stability, security, and performance.
What's New in v6.0.x:
Native 1.21.11 & 26.1.2 Support: Fully compatible with modern Paper and Spigot versions, including Mojang's newest 2026 versioning scheme.
Zero Dependencies: We have completely removed the dependency on ProtocolLib. The plugin is now entirely self-contained and lightweight, reducing server overhead.
Modern HEX/RGB Color Support: Silently and natively supports modern HEX color codes (`&#FFFFFF`) inside blocked messages, bypass notifications, and custom replacements.
Advanced Wildcard & Player Replacements:
Use `%player%` in search/replacement fields to dynamically resolve player usernames.
Use wildcards (`%0%`, `%1%`, `%2%`, etc.) to capture dynamic text from original plugin messages and safely transfer or reposition them inside your customized replacements (e.g. `"%0% joined %1%"` -> `"%1% [+] %0%"`).
Instant Client-Side Refreshes: Reloading or disabling the plugin via `/ph` now instantly refreshes network handlers and forces online clients to rebuild their command suggestions and F3 brand displays (new feature) in real-time—no reconnects required.
*Note: Due to the structural changes, configurations from v5.x and below are not completely compatible. Please let the plugin generate a fresh, optimized config.yml on startup.
Support is now back and strictly focused on v6.0.x and newer.
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:BP4VrfSy:mpBvA8Uz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BP4VrfSy:mpBvA8Uz"
}
