Tags
Creators
Details
Licensed MIT
Published last year
Updated 2 weeks ago
All versions
2.4.2
Release
CustomCommand 2.4.23 weeks ago 62
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
Changes
- Added
cooldowns.ymlto store cooldowns on restarts. You can manipulate the data inside when the server is not running. All changes will be overridden when the server stops/restarts - Made cooldowns applicable for the console and command blocks
- Intoduced a bug where sometimes when the plugin is on the server, command blocks' "last output" just doesn't work anymore. Idk what to do about it, really.
- Added
cooldown-messagefield in command (sections) to specify the cooldown message. Use<cooldown>for the remaining time. Only the first occurrence is replaced, so<cooldown> <cooldown>will result in e.g.10s <cooldown>. - Added
/ccmd cooldownless run <custom-command>, which runs the specified command, ignoring the cooldown. The old cooldown persists after. - Made
/ccmdmore permission-driven. The command is now visible by default and/ccmd helpcan be run by anyone Every subcommand (exceptversioncurrently) has a permission<base-permission>.<node-name>, e.g.ccmd.command.custom-command.update - Check updates every 5min if no new one was found. This is, because a substantial part of servers are not on the latest version and I assume they don't restart often, therefore not calling the updater.
- Fixed a bug where the duration format would not accept formats with spaces
Optional dependencies
Any compatible version
Any compatible version
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:EqFQEONl:ZwiiueF8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EqFQEONl:ZwiiueF8"
}

