1.0.0
Compatibility
Changes
GUICommandBlocker Stop players from using commands while they have menus open! (Specially to prevent mod like ui utilis to sent commands in gui)
What does this plugin do? Have you ever worried about players using commands while they have shop menus or other GUIs open? This plugin solves that problem by blocking commands when players have any menu open. This prevents many common exploits and keeps your server secure!
Main Features Choose how it works: Whitelist Mode: Only commands you specifically allow can be used with menus open Blacklist Mode: Block specific commands when menus are open Easy to use: Simple commands to set everything up Customizable message when commands are blocked Works automatically in the background Server Admin Friendly: Enable/disable command logging Compatible with other plugins Permissions system for staff members Commands /guicmd list - See which commands are allowed or blocked /guicmd message <text> - Change the message players see when blocked /guicmd mode whitelist - Only allowed commands work with GUIs open /guicmd mode blacklist - All commands work except blocked ones /guicmd allow <command> - Add a command to the allowed list /guicmd block <command> - Add a command to the blocked list Admin commands:
/guicmd reload - Reload the plugin settings /guicmd logging on/off - Turn command logging on/off /guicmddebug - Check if the plugin is working correctly How to Install Download the GUICommandBlocker.jar file Put it in your server's plugins folder Restart your server The plugin is now working! Use /guicmd commands to set it up Why You Need This Plugin Many server exploits happen when players use specific commands while they have menus open. This plugin stops these exploits before they can happen!
Perfect for:
Servers with shop plugins Servers with custom menus Any server that wants extra protection The plugin works quietly in the background and only steps in when needed to block potentially harmful commands.
Made with ❤️ by @helloguys98 DM @helloguys98 on discord for help!
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:vaF2C6dp:jpp1sC5q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vaF2C6dp:jpp1sC5q"
}
