Tags
Creators
Details
2.0
Compatibility
Changes
HypeSpam v2.0 ā Changelog
š Bug Fixes
Fixed a major false-positive bug in the word filter. Previously, blocked words were matched using plain substring search, so a short blocked word like "oc" would also trigger inside completely innocent words ā for example, typing "bedrock" got auto-muted because it contains "oc". Words are now matched as whole words only, using Unicode-aware boundaries (also fixes matching for Turkish characters). The same bug existed in the leetspeak/repeated-character variation check and has been fixed there too.
⨠New Features
whitelist-words config option ā an extra safety net list of words that will never be flagged, even if they'd otherwise match a filter. /antispam test <message> ā new admin command to test whether a message would get blocked, without needing a real player to trigger it. Near-duplicate spam detection (check-similarity) ā catches spam that isn't 100% identical but very close (e.g. "hey" ā "heyy" ā "heyyy"), using a configurable similarity threshold. /antispam version command. Short-word warning on /antispam addword for words 3 characters or shorter.
š§ Internal
Word-filtering logic is now centralized in a single shared method, so live chat filtering and the new /antispam test command always produce identical results.
ā ļø Config note: if you're upgrading from v1.0, add the new keys (blocked-words-whole-word-only, whitelist-words, check-similarity, similarity-threshold, similarity-min-length) to your existing config.yml, or delete it to regenerate the default.
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:k20jTp0R:ThqF2TgA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k20jTp0R:ThqF2TgA"
}

