2.1.0
Compatibility
Changes
ChatCRL
ChatCRL is a lightweight and configurable Minecraft chat management plugin designed to give server owners better control over their chat.
It currently includes:
- š Anti-Link ā Prevent players from sending unwanted links.
- š¬ Anti-Spam ā Protect your chat from spam and message flooding.
- š Chat Lock ā Lock the chat and prevent regular players from sending messages.
- āļø Fully Configurable Messages ā Easily customize all plugin messages through
messages.yml. - š More features coming soon!
š Permissions
ChatCRL uses simple permissions that work with LuckPerms and other permission managers.
| Permission | Description |
|---|---|
chat.lock |
Lock or unlock the chat |
chat.bypass.* |
Bypass all ChatCRL restrictions |
chat.bypass.lock |
Bypass the chat lock |
chat.bypass.spam |
Bypass the anti-spam system |
chat.bypass.link |
Bypass the anti-link system |
ā Bypass Permissions
Staff members can be given chat.bypass.* to bypass all ChatCRL restrictions.
For more specific control, you can instead assign individual bypass permissions such as:
chat.bypass.lock
chat.bypass.spam
chat.bypass.link
š Configuration
All messages are stored in messages.yml, making it easy to customize ChatCRL to match your server's style.
You can change things such as:
- Error messages
- Anti-spam warnings
- Anti-link warnings
- Chat lock messages
- Permission messages
- And more
š Found a Bug?
Found a bug, issue, or unexpected behavior?
Please let us know so we can investigate and fix it!
š¬ Discord: https://dsc.gg/extradev
When reporting an issue, please include:
- Your Minecraft version
- Your server software (Paper, Spigot, etc.)
- Your ChatCRL version
- The error/console log, if available
- Steps to reproduce the issue
š What's Coming?
ChatCRL is still actively being developed, with more chat-management features planned for future updates.
Stay tuned for upcoming updates!
ChatCRL ā Simple. Clean. Powerful chat management.
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:qlMemHLE:nuIBUlke"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qlMemHLE:nuIBUlke"
}

