Tags
Creators
Details
4.23.0-alpha1
Compatibility
Changes
DiSky v4.23.0 is finally out, in early alpha, as it contains tons of internal breaking changes; scripts themselves should not be affected (that's my goal at least), and I'll do everything to not introduce breaking changes on your end! :P
:sparkles: Event Rework
The whole event system has been reworked! All events have description, better event values, and it'll be much, much easier for me to add new events with tons of quality of life features (for instance, every update-related event like
on channel name updatewill now useold [channel] name/[new|current] [channel] nameexpressions instead of the weirdpast/future event-string!)
First, I want to make sure my changes are not breaking any scripts, but once that's done, I'll be able to quickly add literally every remaining events from JDA!
:paper: You can find the new documentation for the event rework here!
:zap: Custom Slash Structure Args
I've added a sort of testing version for the custom argument system for the slash structures: it'll let you put non-discord argument type (e.g.
offlineplayer), and DiSky will then take care of the rest! Not only it'll parse the input correctly, but DiSky will also provide the most UI-efficient way for this type: in case ofplayer, it'll display a choice with the currently connected players!
Available custom types are:
- Any Skript enumeration (enums smaller than 25 constants will use a choice argument, enums with more will use auto autocompletion)
playerandofflineplayermember(argument will be none if the command is not within a Guild)color(accepts Skript's constants, RGB and hexadecimal colors)
If you have an idea for a custom argument type, let me know in #💬・chatting!
That's all for now! As said above,
:warning: This is an ALPHA build! It is NOT recommended to use within a production server! Any feedback is appreciated as always :slight_smile:
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:wBIqL2iv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4KA72Zn8:wBIqL2iv"
}

