DupeSight

Every material in material-values is weighted on a shared scale where one diamond is 1. Inside an inventory that only moves items — chest, barrel, shulker, ender chest, hopper, dropper, dispenser — the total value a player can see must never increase.

Legitimate transformations are neutral by construction. Nine diamonds and one diamond block are both 9. Four netherite scrap and one ingot are both 4. Shulker contents are counted recursively, so packing a box changes nothing. Value arriving from a hopper into an open container is credited and subtracted, and the check is skipped entirely while a second player is viewing the same container.

Anvils, smithing tables, villager trades, furnaces, enchanting tables and crafting grids are deliberately absent from that list. They legitimately turn one thing into another, and plugin GUIs conjure items outright — including any of them would flag every normal use.

Container contents are hashed, sorted first so that shuffling a slot does not change the hash, and recorded against the player holding them. When the identical contents show up under a second player — days later, across restarts — that is a SharedFingerprint alert.

Empty containers and containers holding nothing of value are never fingerprinted. That is what stops two spare shulkers being reported forever.

The duplicate-fingerprint-threshold setting decides how many byte-identical containers one player may carry before it counts as evidence.

Red lines scored violation points. Grey lines are context — drops, pickups, deaths, joins — and never score. They exist so the red lines have a timeline around them.

Every lookup resolves through the plugin’s own player table rather than the server’s online list, so inspect, history and reset all work for players who have logged off. That is the case an investigation is actually in.

Reach for /dupesight fingerprint when a player hands you a suspicious shulker. It gives you the hash, what the contents are worth, and every player DupeSight has seen holding them.

Set auto-kick and auto-ban true once you have read a day of real evidence, and set their violation-level thresholds to taste. Both run as console commands with the player, check and violation level substituted, so they flow through whatever punishment plugin your staff already uses.

The cancel-illegal-stack action trims an over-stacked stack back to its legal maximum. It is off by default because silently editing a player’s inventory is a support ticket if the detection was wrong.

The alert cooldown gates violation points as well as messages. Without that, one offending item sitting in a hopper could walk somebody up to a ban threshold on its own.

dupesight.inspect covers inspect, history and fingerprint. dupesight.alerts receives alerts in chat. dupesight.admin confers both and adds reset and reload.

The two bypass nodes default to false rather than op. Defaulting a monitoring bypass to op exempts every staff member from the audit trail, which is the opposite of what an audit trail is for. Grant them deliberately or not at all.

Staff who want quiet should use /dupesight alerts off rather than having the permission taken away.