All versions
1.0
Release
ezFilter 1.02 years ago 98
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Paper
Changes
EzFilter v1.0.0 - Initial Release
Release Date: 08/11/2024
New Features
-
Chat Filtering:
- Introduced the ability to filter specific words in player chat. Messages containing banned words will be automatically deleted.
- Added a configurable list of banned words in
config.yml. - Implemented basic bypass prevention by detecting spaces and other character manipulations.
-
Warning System:
- Players will receive warnings if they attempt to use banned words.
- Configurable threshold for warnings before taking further action.
- Option to kick or ban players after reaching a certain number of warnings.
-
Discord Webhook Integration:
- Logs filtered messages and player warnings to a configurable Discord webhook.
- Includes player information and message content in Discord embed.
- Configurable Discord embed styling, including player head as an image.
Configurable Options
- Banned Words List: Easily modify and update the list of banned words via
config.yml. - Warning Thresholds: Configure the number of warnings a player can receive before they are kicked or banned.
- Action on Max Warnings: Choose between kicking or banning players when they exceed the warning limit.
- Discord Webhook: Enable or disable Discord logging, and configure the webhook URL in
config.yml.
Improvements and Optimizations
- Performance: Efficient handling of chat events to minimize impact on server performance.
- Usability: Easy-to-use configuration file with comments explaining each option.
Known Issues
- None reported yet. Please report any issues or bugs on the plugin's support page or repository.
Future Plans
- Advanced Bypass Detection: Implement more sophisticated techniques to detect and prevent bypass attempts.
- Customizable Messages: Allow for fully customizable warning messages, kick/ban messages, and Discord log messages.
- Database Integration: Optional logging of filtered messages and warnings to a database for long-term storage.
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:qnOgDcap:kDrGAZQz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qnOgDcap:kDrGAZQz"
}

