Tags
Creators
Details
Licensed MIT
Created 4 years ago
Updated last month
All versions
10.0.0
Release
CommandAPI 10.0.0 (Velocity)last year 69
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.5
1.20.x
Platform
Velocity
Changes
Minecraft Version Changes
- Adds support for Minecraft 1.21.5
- Drops support for Minecraft 1.16.5 - 1.19.4
Java Version Changes
- Changes CommandAPI from Java 16 to Java 17 (LTS)
New features
- #633 Adds an
AsyncOfflinePlayerArgumentto allow asynchronous fetching of an offline player
Bug fixes
- #477 Fixed
NativeProxyCommandSendernot being able to run Vanilla (and CommandAPI) commands - #578, #583, #629 Fixes
Bukkit#dispatchCommand()not working after Paper's Brigadier API changes - Fixes
PotionEffectArgument.NamespacedKeynot having suggestions in some versions
New changes
- #636 The default namespace has been updated from
minecraftto the plugin's name. If you are not shading, the default namespace is going to becommandapi. If you are shading, the default namespace is going to be your plugin's name. - Updates the config defaults for the datapack reloading step to be opt-in instead of opt-out.
- The CommandAPI will now tell you if you've messed up mappings (in addition to spewing messy errors)
- #634 Functions that use
Componenthave now been changed to useComponentLike - Added support for Velocity!
Website Changes
- The CommandAPI's new homepage is https://commandapi.dev/ (currently points to the documentation)
- Documentation has moved over to https://docs.commandapi.dev/
- JavaDocs have moved over to https://javadocs.commandapi.dev/
- The CommandAPI has moved from
github.com/JorelAli/CommandAPIto its own organization over atgithub.com/CommandAPI/CommandAPI
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:ExxvCi0y:mELNQ3me"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ExxvCi0y:mELNQ3me"
}

