4.24.0-beta1
Compatibility
Changes
It's been awhile since the last update! This is finally announcing the release of DiSky 4.24.0-beta1. I will try to keep this short and sweet and explain why this is in beta, so please take some time to read this as this is extremely important.
🎉 Components V2/Containers Update!
Yes, you heard it here, DiSky now supports the new Components v2/Containers. Discord has introduced a completely new component system (which is not compatible with the old one!) meant to replace embeds and components within messages. It allows you to create customizable layouts with sections, galleries, files, and much more, all within one component called a "Container". You can find the documentation for containers here, although this is a beta and you should expect bugs. We have actively tested with our @👑 - Platinum members and have hopefully ironed out most bugs/problems!
🛠 File Upload enhancements
We have made some changes as to how File Uploading is now handled, so this should hopefully be better now!
❓ Why beta?
Now I know you all are going to be asking this, so I am going to explain while taking snippets from JDA's (Java Discord API's) message. We are in beta considering this a huge new update with a heck ton new features for you all to mess around with and also find anymore bugs/issues that may arise. Now for the 2nd part. JDA (Java Discord API) is what we use to make DiSky work, and with that comes it's own issues. As from JDA, "For now, this [6.0.0-rc.1] is just a release candidate, since we might want to do some more breaking changes before the stable release of 6.0.0." This is obviously a beta build of JDA which can lead to even more issues. the next release candidate might include more breaking changes, potentially with components or other parts of JDA." This is why this is a beta.
We hope you enjoy this update, and thank you for using DiSky! ❤
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:4KA72Zn8:ynFIjx3D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4KA72Zn8:ynFIjx3D"
}

