Tags
Creators
Details
3.6
Compatibility
Changes
Anti-Dupe 3.6
Anti-Dupe 3.6 delivers improved detection accuracy, world-level control, plugin compatibility and performance.
🌍 Per-World Enforcement
Every world can independently use disabled, audit, quarantine, or inherit the global mode.
World policies now cover:
- Live inventory transactions
- Delayed confirmation checks
- Player inventories and Ender Chests
- Loaded storage containers
- Signed item identities
- Cross-inventory UUID scanning
This makes temporary-kit PvP arenas and minigame worlds easy to isolate while maintaining full protection in survival worlds.
🎯 Accurate Item Pickups
Ground pickups now receive exact item-and-quantity receipts. Items collected while another inventory action is being checked are recognized as legitimate transfers.
Only the amount actually collected is authorized, meaning additional unexplained quantity remains detectable.
Mined block drops are also registered as legitimate persistent-ledger supply.
🤝 Improved Plugin Compatibility
- Trusted custom-GUI plugins no longer require title patterns.
- SmartSpawner virtual-storage withdrawals are supported.
- Anti-Dupe recovery menus are completely exempt from detection.
- Double chests and their open views share one physical-storage identity.
- Trusted GUI receipts authorize only items received by the player.
🔎 Investigation and Recovery 🩹
Players → Incidents → Incident Items
Each incident can include:
- World and exact coordinates
- Nearby players
- Nine-chunk redstone and storage audit
- Previous ten offender commands
- Individually restorable items
- Restore All and Back controls
Items are always backed up before enforcement.
🕵️ Detection Improvements
- Persistent global quantity ledger
- HMAC-signed unique-item identities
- Two-stage enforcement
- Atomic network transfer claims
- Exact item-boundary receipts
- Expanded detection simulation suite
📈 Performance
Background scans are batched, time-budgeted, and automatically deferred during low TPS. Live protection and confirmed enforcement remain active.
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:u5dKxq9Q:8BCm6Tea"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:u5dKxq9Q:8BCm6Tea"
}

