Tags
Creators
Details
v1.2
Compatibility
Changes
✨ New Features:
💾 Hybrid Database System: The plugin now supports SQLite (local, enabled by default) and MySQL (ideal for BungeeCord/Velocity networks). Everything runs asynchronously using HikariCP to guarantee 0% lag on your server.
📜 Global Report History GUI: Added a new /reportes <player> command (with tab-completion). It opens an awesome GUI where administrators can view all accumulated reports of a user (reason, date, server, and who reported them).
👻 Deep Vanish 2.0: Being invisible now means being a true ghost:
Join-Hide Security: If a new player joins the server, they won't see staff members who are already in Vanish (Fixed Spigot's native visibility bug).
Hides invisible staff from the multiplayer menu player count (Server Ping).
Invisible staff no longer prevent the night from passing (Sleeping Ignored).
Mobs will no longer target or follow you if you enter Vanish in front of them.
Automatic compatibility with Scoreboard/TAB plugins (via Metadata).
🌟 Staff Glowing (Configurable): Staff members will now automatically glow when entering staff mode to be easily identified by other admins. The glow color automatically adapts to your TAB/Ranks plugin. Can be disabled in the config.
🦉 Automatic Night Vision: Grants infinite, clean night vision upon entering Staff Mode.
🔧 Fixes & Optimizations:
Anti-Spam Item Fix: Added an invisible cooldown (250ms) to staff tool (RandomTP) to prevent a Bukkit bug that executed actions and sent chat messages twice on a single click.
Message Optimization: Implemented a global {prefix} variable across all commands so changing the plugin's chat prefix only requires editing a single line in the config.
⚠️ IMPORTANT NOTE FOR SERVER OWNERS: Please make sure to add the new database: and settings: sections to your existing config.yml, or simply delete your old config file so the plugin can automatically generate the new version with the latest options.
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:e8XHrrop:e9IQNg1W"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e8XHrrop:e9IQNg1W"
}

