1.0.0
Compatibility
Changes
Profanity Guard is a Minecraft mod designed to help server owners maintain a cleaner and more respectful in-game chat environment. By utilizing datapacks, Profanity Guard enables customizable and comprehensive filtering of profanity, ensuring a positive experience for all players.
Key Features:
- Customizable Word Filters: Server owners can easily expand or modify the profanity list using
.jsonfiles. This allows for tailored filtering to suit the unique needs of each server. - Flexible Word Management: The mod supports aliases and common misspellings, making it highly effective at identifying and blocking variations of offensive terms.
- Profanity Replacement: Words flagged as profanity are replaced with
#(hashtags) to obscure offensive language while maintaining the flow of conversation. - Simple Integration Path: To add new words to the filter, place the
.jsonfiles in the following path:
Replacedata/<id>/profanity/<filename>.json<id>with your datapack’s namespace and<filename>with your chosen name for the file.
Example .json Configuration:
To add a new word to the filter, server owners can create a .json file in their datapack using the following structure:
{
"this_is_the_main_profanity_word": [
{
"aliases": [
"These_are_common_typos_or_aliases_of_the_word"
]
}
]
}
Additional Notes:
- Add Multiple Words in a Single File: It's perfectly fine to include multiple profanity words and their aliases in the same
.jsonfile, making management efficient and organized. - Naming Flexibility: The
.jsonfile names are unrelated to the parsing process. You can name them however you like, as long as they follow Minecraft's naming conventions (lowercase only). - Automatic Loading: Any file placed in the
profanityfolder will automatically load, simplifying setup and updates.
With Profanity Guard, maintaining a respectful chat atmosphere has never been easier or more efficient. Customize your filters, ensure inclusivity, and create a welcoming community for all players.
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:w55UhnTf:p0YQIBRV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:w55UhnTf:p0YQIBRV"
}

