Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last month
All versions
1.7.0
Release
1.7.011 months ago 1,380
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.5–1.21.10
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
Changes
- Updated to JDA 6.1.1. With that comes some breaking changes. See "Migrating" section below for necessary migrations
Components
- Added new Label component type
- This replaces the use of Action rows in modals and the
labelproperty in text inputs
- This replaces the use of Action rows in modals and the
- Action rows are now its own component type
- Instead of the
componentsin the message content schema being a list of lists of components, action rows can be declared explicitly with a component of typeaction_row. The old syntax of defining an action row from an array is still supported for backward compatibility and convenience.
- Instead of the
- The
labelfield of text inputs has been removed. Use a label component instead. - Added support for components V2 via
use_components_v2in message content - Added new components from components V2 (See docs for details)
- Separator
- Container
- Text display
- Section
- Thumbnail
- Media gallery
- File display
- File upload
Documentation
- Message components example was split into seperate buttons and select menus example
- Added misc components example for component V2 components
- Added links to relevant examples to docs for functions and schemas
- Updated modal example with file upload and select menu
Migrating
To migrate your scripts, the following is necessary:
- Converting action rows in modals to labels
- Check the updated modal example in the documentation
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:m00L1GVJ:ly6rFJiH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m00L1GVJ:ly6rFJiH"
}

