Tags
Creators
Details
1.1.8
Compatibility
Changes
-
Added new module /announcements/ with multi-channel display. Broadcast messages simultaneously via Chat, Action Bar, Titles, and Boss Bars.
-
Added /announcetoggle for players. Preferences are saved persistently in the database just like the rest of the other toggles.
-
Added new command: /announcement <trigger|enable|disable> <key> [args] (aircore.command.announcement)
-
Added new placeholder %aircore_player_toggle_announcements% returns the state of the current player announcements toggle.
-
Added new message keys [code]utilities: announcement: not-found: "%prefix% <red>Announcement <yellow>%name%</yellow> was not found.</red>" triggered: "%prefix% <green>Announcement <yellow>%name%</yellow> has been manually triggered.</green>" enabled: "%prefix% <green>Announcement <yellow>%name%</yellow> is now enabled and scheduled.</green>" already-enabled: "%prefix% <green>Announcement <yellow>%name%</yellow> is is already enabled.</green>" disabled: "%prefix% <red>Announcement <yellow>%name%</yellow> has been disabled.</red>" already-disabled: "%prefix% <red>Announcement <yellow>%name%</yellow> is already disabled.</red>"
toggles: enabled: "%prefix% <green>You will now see automated announcements.</green>" disabled: "%prefix% <red>You have muted automated announcements.</red>" enabled-for: "%prefix% <green>Announcements enabled for <yellow>%player%</yellow>.</green>" disabled-for: "%prefix% <red>Announcements disabled for <yellow>%player%</yellow>.</red>" enabled-by: "%prefix% <green><yellow>%player%</yellow> enabled announcements for you.</green>" disabled-by: "%prefix% <red><yellow>%player%</yellow> disabled announcements for you.</red>"[/code]
-
Added new command usages [code]command-usages: announcement: usage: "/%label% <option> <key>" usage-trigger: "/%label% trigger <key> [args]" usage-enable: "/%label% enable <key>" usage-disable: "/%label% disable <key>" aliases: [announcements] announcetoggle: usage: "/%label%" usage-others: "/%label% [player]" aliases: [][/code]
-
Fixed homes being removed after reload
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:8VonM7S3:CLNAYmGC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8VonM7S3:CLNAYmGC"
}

