Anti-Dupe V6.0.0
Anti-Dupe helps protect Minecraft Bedrock worlds, Realms and servers against common item duplication methods. Manage protections, staff access, alerts and punishments through an in-game menu.
Quick Setup
- Use Minecraft Bedrock 1.26.40 or newer, import the pack and activate it under Behaviour Packs. Cheats and Experiments can stay off.
- Join with Minecraft's Operator permission.
- Hold a clock, crouch, aim at a block and press Use/Interact. The clock is reusable and is never consumed.
- On first setup, choose a six-digit administrator PIN and enter it twice to confirm.
- Review Settings → Configuration. All protections start enabled and automatic kicks start disabled. Existing worlds keep their saved settings.
Use the same clock action whenever you want to reopen the menu. Ordinary players need no setup.
Screenshots include earlier builds, so some menu labels and alert wording may differ from V6.

Giving Staff Access
Operators skip the PIN after setup. To add staff, open Access Control → Enroll Online Player, select someone and privately share the PIN.
Enrolled admins enter the shared PIN once per login or pack reload. Death and dimension changes do not sign them out. Owning a clock or knowing the PIN alone cannot give an ordinary player access.
Through Access Control, operators can:
- Enroll up to 32 admins.
- Revoke an admin, including while they are offline.
- Reset a forgotten PIN.
- Revoke all enrolled admins.
- Review recent access changes.
Resetting the PIN requires enrolled admins to sign in again.
Five incorrect PIN attempts within ten minutes cause a five-minute lockout. Repeated lockouts get longer, up to an hour. Reconnecting does not clear them.
Existing admins can still use the bedrock shortcut and follow its setup or login prompts. First setup requires an operator or an existing legacy admin.
Settings
Use Settings → Configuration to turn individual protections on or off.
Use Personal Settings to choose whether you receive public messages and admin alerts.

What the Protections Do
Bundles, Hoppers and Droppers
Bundles remain usable in player inventories, chests and barrels. By default, bundles of every colour are restricted from passing through hoppers, hopper minecarts and droppers.
- Hoppers: restricted stacks found inside are deleted.
- Hopper minecarts: restricted item pickup is blocked; restricted stacks found inside are deleted.
- Droppers: restricted stacks are ejected above the block and cleared from its inventory.
Hopper example

Dropper example

Monitoring continues while menus are open and when pistons move containers. Item totals are compared during suspicious interactions and at close to detect extra items, even if the bundle has already been removed.
Change the list under Settings → Restricted Transit Items. It supports up to 90 item identifiers, such as minecraft:bundle. These restrictions apply to protected transfers, not ordinary inventory or chest storage.
If a storage item cannot be safely checked during a protected transfer, the whole item may be deleted or ejected according to the container's rule.

Join/Leave Protection
Anti-Dupe compares item totals before a normal departure and after rejoining. This includes carried items, the stack held by the inventory pointer, equipment, ender chest contents and bundle contents.
When a valid comparison shows extra items, the excess is removed. A full inventory or pointer stack alone does not trigger removal. Missing or unusable records cannot authorise this correction.
Corrections are logged for staff without adding player violations or issuing punishments.
Older join/leave example: V6 records these corrections without the public accusation shown below.

Tall Plants Beside Pistons
Pistons and sticky pistons cannot sit immediately beside a supported double-height plant, including diagonally, at the height of either half.
This covers tall grass, large ferns, sunflowers, rose bushes, peonies, lilacs and tall seagrass.
- Place a piston beside one: the new piston is removed.
- Place a plant beside a piston: both halves of the new plant are removed.
- Grow plants with bone meal: only newly grown plants that break this rule are removed.
- Activate an existing forbidden setup, or have it found by a safety check: the piston is removed.
Pistons two blocks away and unrelated heights are unaffected. One-block flowers and tall dry grass are excluded.

Illegal Item Stacks
Invalid stacks are removed, including amounts above an item's normal limit or above 64.
Checks include inventories, the inventory pointer, equipment, ender chests and storage-item contents, including after respawning.
If another add-on intentionally allows larger stacks, review Illegal Stack Patch under Configuration for compatibility.
Alerts and Player Violations
An incident records something the pack detected and what it did about it. It does not automatically mean a player cheated.
- Direct incidents are tied to an observed player action. They can add violations, appear in public alerts and trigger configured punishments.
- System incidents cover automatic transfers, join/leave corrections and cases where one responsible player cannot be established. Staff receive the record, but nobody gains a violation, punishment or public accusation from it.
Nearby names and closing a container alone are not proof of wrongdoing.
Public alert example

Admin alert example

Optional Punishments
Automatic kicks are off by default.
To enable them:
- Open Punishments → Global Options → Edit Settings.
- Enable Allow Kick Actions.
- Choose the relevant rules under Configure Dupe Types.
Manage player records, resets and repeat kicks through Punishments → Violations.
Operators and trusted admins are exempt from punishments. Item and block protections still apply to them.

Logs and Player Records
Open Logs → Incident Logs to review recent detections and the action taken.
Logs → Violations shows player violation totals. Settings, recent incident history and player records are saved with the world.


Under Punishments → Violations, select a player to review their record, reset violations or manage repeat kicks.
A kick loop repeatedly removes a flagged player, including when they rejoin, while the required kick settings remain enabled.


Debug and Help
Use Debug → Runtime Status to check the pack's activity, or View Debug Log when investigating a problem.

Help provides guidance from inside the game.

Common Questions
Why won't the clock open the menu?
Hold it, crouch and use it on a block. Check that the pack is active and that you are an operator or enrolled admin. First setup requires an operator or an existing legacy admin.
Why did a bundle disappear?
Hoppers delete restricted bundles; droppers eject them. Check the incident log for the recorded action.
Does the pack constantly scan the whole world?
No. It reacts to placements, piston movement and item transfers, with smaller safety checks around players. Container monitoring focuses on nearby loaded areas; busy areas may take longer to check.
Does it stop every possible dupe?
It covers the situations described above. It cannot guarantee protection against every exploit, engine crash or world rollback. Try it in a disposable world before adding it to your main world or Realm.
Credits and Support
- Created by: Frazer
- Special thanks: Eagles
- License: Public Domain
- Support: Join the Discord

