Riverly AntiElitraTR banner
Riverly AntiElitraTR icon

Riverly AntiElitraTR

Act as a Senior Java Developer specializing in Minecraft Anti-Cheat heuristics. I have a core plugin called RiverlyAntiTarget that detects 'Elitra Target'...

00Free
spigotServer1.21.1mod

Riverly Anti-ElitraTR

Overview

This is an anti-cheat plugin that catches players using "Elitra Target" cheats - those sneaky hacks that let people switch hotbar slots way faster than any human could. It watches for perfectly-timed slot changes (like a bot) versus the natural, messy timing of real players.

Features

  • Packet Jitter Analysis - Detects cheaters by analyzing timing patterns. Real humans have slightly different timing each time (45ms, 62ms, 51ms), while cheat bots are unnaturally consistent (exactly 50ms, 50ms, 50ms)
  • Smart Filtering - Ignores normal scrolling and sequential slot changes so you don't get false alerts
  • Lag Protection - Automatically stops checking during server lag to prevent false positives
  • Staff Alerts - Alerts players with the riverlyac.alerts permission when cheaters are detected
  • Regular Resets - Clears violation data every 15 seconds so players don't get punished for old, unrelated actions

How to Use

  1. Drop the plugin into your server's plugins folder
  2. Start the server - the anti-cheat begins working automatically
  3. Staff with the riverlyac.alerts permission will receive alerts when cheaters are detected
  4. Use /riverlyac stats to see how many players are being tracked
  5. Use /riverlyac reset <player> to clear a specific player's data if needed
  6. Use /riverlyac reload to clear all tracking data

Tips & Tricks

  • Give your moderators the riverlyac.alerts permission so they can see alerts
  • Give admins the riverlyac.admin permission to use management commands
  • The plugin works best on servers with stable TPS (18+)
  • Violations reset every 15 seconds, so repeated violations indicate actual cheating

Known Limitations

  • May have reduced accuracy during significant server lag (TPS below 18)
  • Requires at least 3 rapid slot changes before analysis begins
  • Works best with Spigot and Paper servers (TPS detection uses reflection for compatibility)