13.4
Compatibility
Changes
We have implemented an option for those using plugins that rely on Paper's chat event instead of Spigot's (# Use Paper's AsyncChatEvent instead of Spigot's AsyncPlayerChatEvent).
You can enable it in the "event-priority" section inside the config.yml file.
If you prefer, you can also add the option manually:
use-paper-event: false
Make sure it is placed under event-priority:.
Example:
event-priority: use-paper-event: true
This is useful if you donβt want to create a new config file. With this option, full support for Paper is provided.
We have implemented a StaffChat system, completely isolated from DiscordSRV, meaning messages will be fully private for staff members who have the following permission: quickchat.staffchat.
The command to use this channel is /staffchat.
Additionally, we have implemented a BossBar announcement system, which you can use to display information such as your server IP or store.
We recommend reloading the config.yml and messages.yml files.
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:Nw8Sb3nr:JKdP6TUu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Nw8Sb3nr:JKdP6TUu"
}

