Anti-Dupe Pack - Version 5.0.0

Version 5.0.0 is a major upgrade that expands the pack from “single-purpose dupe mitigation” into a broader server-side incident + mitigation system, with improved administrative visibility, configurable protections, and optional enforcement tools.

What’s New

Expanded Mitigation Coverage

V5 hardens multiple exploit outcomes and near-player dupe setups:

• Join-Leave (Ghost Stack) Mitigation

  • Detects suspicious cursor/overflow states on initial spawn and prevents persistence.

• Tall Plant / Piston Dupe Mitigation

  • Detects piston proximity near two-block-high plants and removes involved pistons.

• Bundle / Restricted Item Transfer Mitigation

  • Automatic Hopper Purge: removes restricted items found in hopper inventories.
  • Dropper Ejection: ejects restricted stacks from droppers (item is not destroyed) and clears the container slot.

• Illegal Stack Size Enforcement

  • Clears invalid stacks (non-finite, <= 0, > maxAmount) and enforces a hard cap of 64.

Player-Centric Scanning Model (Performance-First)

Instead of scanning the entire world, V5 focuses on active gameplay areas:

• Scans a small cube around each online player (SCAN_RADIUS = 4 → 9×9×9 volume).
• Uses a per-tick work budget to reduce lag spikes:
  • BLOCKS_PER_TICK_LIMIT controls how much scanning occurs per tick across all players.

Practical effect: strongest coverage where players are active (spawn, bases, shops). If nobody is near a setup, it will not be scanned.

Standardised Incident Announcements

All detections follow a consistent structure for clarity and moderation value.

Public announcements (toggleable) can include:

• Offender username
• Dupe method attempted / detected
• Specific item involved
• Quantity where available (e.g., 64x minecraft:bundle)

Administrator alerts (toggleable) include everything above, plus:

• Exact coordinates (and dimension where available)
• Nearby players within a configured radius (e.g., 50–100 blocks)

Logging System (In-Game Viewer)

V5 improves internal logging for staff review:

• Incidents are written to a rolling internal log (session-first).
• Admins can view logs in a scrollable menu and clear them when needed.
• When supported, logs can persist via Dynamic Properties (size-capped storage).

Violations, Totals, and Administrative Visibility

V5 introduces more structured tracking:

• Scoreboard-backed totals (per-player + global participant totals where supported).
• A Violation Registry used by the punishments UI and repeat-offender tooling.
• A Violations Dashboard / Leaderboard for quick staff overview.

Optional Punishments (Configurable)

Punishments are modular and can be enabled per incident type:

• Type-specific thresholds (e.g., ghost/piston/hopper/dropper/illegal)
• Optional actions:
  • Apply tags (type-specific and/or global)
  • Optional kicking (requires /kick permission and config enablement)
  • Optional repeat enforcement (kick-loop) for persistent offenders
• Safety controls:
  • Admins are exempt
  • Optional bypass tag
  • Cooldown throttling to prevent kick spam

Notes | Using the Admin Menu

1. Have the Admin tag.
2. Hold a Block of Bedrock.
3. Use / Right-click / LT the item to open the menu.

Compatibility Notes

• Designed for Worlds, Realms, and Servers
• Requires the Script API modules:
  • @minecraft/server
  • @minecraft/server-ui
• Does not require Beta APIs or experimental gameplay toggles when deployed against stable scripting modules (host panels may still require “Enable Scripting” to be on).
• Supports custom environments and typical survival/factions setups (note: V5 treats stacks above 64 as illegal if that protection is enabled).