Tags
Creators
Details
4.26.0
Compatibility
Changes
Hello there! Here comes DiSky v4.26.0 with some nice quality of life improvements and bug fixes! Thanks to @EquipableMC and @Fusezion for their help on some stuff!
:sparkles: New Features
- Embed Fields as Expressions: Embed fields are now accessible and manipulable as expressions, giving you more flexibility when working with embeds. See here
- Embed Templates: Brought back the embed template system from DiSky v3! You can now register and reuse embed templates for more efficient embed creation. You may also use them in data structures!
- Member Boost Time Support: Added support for
Member's boost time, allowing you to retrieve how long a member has been boosting the guild. See here - Better Variable String Support: This enables more intuitive variable storage for Discord objects (channels, messages, members, etc.). You can now use
{blah::%{_member}%}instead of{blah::%discord id of {_member}%}.
:tools: Improvements
- Enhanced Message Editing: The
edit messageeffect now supports full or transient replacement modes, giving you better control over whether previously unedited content (like embeds) should be replaced or preserved. See here
:bug: Bug Fixes
- Fixed global and guild slash commands creation/updating system that was broken due to command ID changes on server restart.
What's Changed
- Spelling correction in
RetrieveMember.javaby @Mushkrem in https://github.com/DiSkyOrg/DiSky/pull/269 - Adds support for getting the boosted time of a member, and fixes invalid docs url in feature template by @EquipableMC in https://github.com/DiSkyOrg/DiSky/pull/270
Full Changelog: https://github.com/DiSkyOrg/DiSky/compare/4.25.0...4.26.0
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:yRzuFsac"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4KA72Zn8:yRzuFsac"
}

