Tags
Creators
Details
1.0.0
Compatibility
Changes
Plugin: Discord Command Bridge This plugin seamlessly integrates your Minecraft server with your Discord server, empowering your staff to execute in-game commands directly from a Discord channel. It's a powerful tool for remote server management and moderation.
Key Features Feature Description Remote Command Execution Allows authorized users to run Minecraft commands (like ban, kick, tp) from a designated Discord channel without needing to be in-game. Role-Based Permissions Features a highly granular permission system. You can map specific Discord roles to a list of allowed Minecraft commands, ensuring that staff members only have access to the commands appropriate for their rank. The configuration supports a wildcard (*) to grant a role access to all commands. Customizable Configuration The config.yml file allows for easy customization. You can set a unique command prefix (e.g., ., !, /) and optionally restrict the bot to operate in a single, specific Discord channel. Instant Feedback The bot provides immediate and clear feedback messages in Discord for every action. Users are notified of successfully executed commands, permission denials, or incorrect command formats. How It Works A user with a configured staff role in Discord sends a message in the command channel, for example: .kick Notch "Griefing". The plugin checks the role-mappings in the config.yml to verify if the user's Discord role is permitted to use the kick command. If permission is granted, the command is executed on your Minecraft server as if it were typed in the console. The bot then sends a confirmation message, like " Command executed: kick Notch "Griefing"", back to the Discord channel. If the user lacks permission, it will send a denial message instead. This plugin is an essential tool for any server administrator looking to streamline their staff's workflow and manage their server efficiently from anywhere through Discord.
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:Yi3GVMey:1Smkmvnm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Yi3GVMey:1Smkmvnm"
}

