0.1.3
Compatibility
Changes
Colours
palette.yml has every colour that will be used. Write <c:accent> in any message or on any GUI and close it with </c>. Change one line there and the whole plugin changes colour. Nineteen names included.
Messages moved
messages.yml and menus.yml are now the messages/ folder, one file per module of the plugin. Translations too: messages/es/ instead of messages_es.yml. Any file may set a prefix of its own.
A command can output custom lines
A messages block in a command's config replaces a line for that command alone, by the same keys. An empty one sends no message.
Updating
Nothing to delete/change. Old versions of messages.yml or messages_es.yml still works.
1.18.2 - 26.2 · Paper & Folia
Wiki was updated too https://chorusdev.lat/wiki/choruscore
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:ZXE5W9di:8kXjP4BA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZXE5W9di:8kXjP4BA"
}

