Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 7 months ago
All versions
1.0.1
Release
Command Controls 1.0.17 months ago 759
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
CommandControls v1.0.1
๐ New Features
Hidden Commands
- Added
hidden_commandsconfiguration option - Commands in this list will work when typed but will not appear in tab-complete suggestions
- Perfect for hiding the "real" command when you want players to use aliases instead
- Example: Hide
/sidebarso players use/sbinstead
Command Aliases Support
- Added
aliasesconfiguration option - Define shorthand commands that map to their target commands
- If a player can use an alias, they can also use the target command (and vice versa)
- Bidirectional alias resolution - works both ways
Improved Sync Protocol
- Enhanced client-server sync to include hidden commands
- Client now properly filters hidden commands from suggestions while still allowing execution
๐ง Improvements
- Added
_hidden_infocomment to default config explaining hidden commands feature - Aliases section added to default generated config
- Better debug logging showing exactly which commands are sent to each player
- Improved alias resolution in permission checks
๐ Bug Fixes
- Fixed aliases not appearing in tab-complete suggestions
- Fixed command tree not including alias targets when only alias is allowed
- Fixed sync packet not matching command tree contents
๐ Configuration Changes
New configuration options added:
{
"hidden_commands": [
"sidebar"
],
"aliases": {
"sb": "sidebar",
"b": "balance"
}
}
โ ๏ธ Important Notes
- Both server AND client need to be updated to this version for hidden commands to work correctly
- Existing configs will continue to work - new options are optional
- Delete your old
commands.jsonto regenerate with new default structure, or add the new fields manually
๐ฆ Dependencies
- Minecraft 1.20.1
- Fabric Loader 0.16.10+
- Fabric API 0.92.6+
- LuckPerms (recommended)
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:dzcEK3Qd:f84L4I9A"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dzcEK3Qd:f84L4I9A"
}

