1.1
Compatibility
Changes
π Update v1.1
This update focuses on polish, configurability, and better control over chat restrictions.
Several issues have been fixed and new features have been introduced to make VoidChat more flexible and intuitive for server administrators.
Changes & Improvements
- Fixed an issue where the message displayed after enabling or disabling chat did not correctly format the
%player%placeholder - Improved
config.ymlby adding clear comments for easier editing and better understanding - Enhanced item lores in the management GUI for a cleaner and more polished look
- Added a world blacklist β a configurable list of worlds where players are not allowed to send chat messages
- Introduced a new permission:
voidchat.bypass- Allows players to bypass global chat restrictions
- Server operators automatically bypass chat blocks as well
This update improves overall usability while keeping VoidChat lightweight and performant.

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:NrGWfY52:YN905hXH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NrGWfY52:YN905hXH"
}

