Tags
Creators
Details
Licensed ARR
Published last month
Updated 2 weeks ago
All versions
1.1.0
Release
Ultimate Anti-Illegals 1.1.03 weeks ago 12
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platform
Paper
Changes
Ultimate Anti-Illegals 1.1.0 is now live!
Its a huge update for the plugin, featuring loads of new features and improvements, for your ultimate experience:
- Actions per Violation - Choose what happens to an illegal item: remove it, repair it, quarantine it or only log it
- Quarantine - Removed items are saved, so you can restore false positives or delete them for good
- Dry-Run Mode - Try the plugin without it touching anything, perfect for your first hour on a new server
- Punishments - Customizable warnings, kicks and commands (like tempbans) for players who keep using illegals
- Nested Storage Scanning - Automatically scans shulker boxes and bundles, and only removes the illegal item inside
- Container, Chunk & Hopper Protection - Illegals are cleaned from containers when opened or loaded, and hoppers can no longer move them
- Allow List - Exempt certain items, so e.g. custom items from other plugins won't get flagged
- Better Enchantment Checks - Detects conflicting enchantments and over-leveled enchanted books
- Permissions - Bypass specific checks with per-category permissions, like NBT items but still no bedrock
- World Control - Enable or disable the plugin per world
- Staff Alerts & Logging - Get notified in real time, with a full log of everything that was found
- Fully Customizable Messages - Every message now lives in the config
- Bug Fixes - Various optimizations keep the plugin lag-free and responsive
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:yGopgZsH:7FbUy7sV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yGopgZsH:7FbUy7sV"
}

