Tags
Creators
Details
1.3
Compatibility
Changes
Update 1.3
New Features
Global Command Permission System:
Added a new feature to enforce permissions for all commands when enabled in the configuration. Commands now require permissions in the format:
- fluffylobby.<command>.
A configurable whitelist (e.g., /spawn, /server) ensures critical commands remain accessible. Tab Completion Filtering:
Players now only see commands in tab suggestions that they have permission to execute. Helps prevent unauthorized players from discovering blocked commands. (BETA)
MiniMessage Support Across All Features:
- Enhanced MiniMessage formatting for all messages, including gradients, colors, and bold/italic text. Configuration messages such as "No Permission" or "Spawn Set" now fully support MiniMessage styling.
Improvements
Added a new configuration option: require_command_permissions (default: false). When enabled, all commands require proper permissions to execute. Dynamic and Clean Command Validation:
Only registered commands are intercepted by the permission system. Prevents blocking non-existent commands and improves performance.
Improved Error Handling:
Customizable "No Permission" messages with MiniMessage support for a better user experience. Configuration Changes New Config Option:
- require_command_permissions: false
Enable or disable the global command permission system.
New message entries for permissions and general feedback Fixes Command Execution for Non-Players:
Improved handling of commands to ensure proper messaging for non-player usage.
Duplicate Messages in Join Event:
- Resolved issues with duplicate MiniMessage parsing in the join event handler.
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:IFN012qu:pi2NmJYp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IFN012qu:pi2NmJYp"
}

