Exploits server-side latency compensation by delaying position update packets. Attack players where they were, not where they appear to be—making hits register on targets that have already moved out of range.
The module intercepts server side packets to build a map of where the server believes each entity is located. These "ghost" positions lag behind the visual client position by your configured delay, creating a window of opportunity where attacks connect against outdated hitboxes.
Not all packets should be delayed. Critical updates like health, respawn, time sync, and chat messages are whitelisted to pass through immediately. Only movement-related packets are queued, ensuring the game remains responsive while maintaining the backtrack advantage.
An optional bounding box renders at the server-side position of your target. This translucent outline shows exactly where you need to aim for hits to register. The alpha smoothly fades in/out when targeting, providing clear visual feedback without screen clutter.
1. Position Tracking: As the server sends entity movement packets, BackTrack stores the raw coordinates in a concurrent hash map keyed by entity ID.
2. Packet Queuing: Movement packets are intercepted and stored in a queue with timestamps. They're not processed until the delay expires.
3. Attack Window: When you attack, the server still sees the target at their delayed position. Hits connect against this "ghost" hitbox even if the player has visually moved away.
→ Low Ping (0-30ms): 38-50ms delay — Subtle advantage without visible desync.
→ Medium Ping (30-80ms): 50-100ms delay — Compensates for your own latency plus adds backtrack window.
→ High Ping (80-150ms): 100-200ms delay — Maximum advantage, but movement may appear choppy.
→ Aggressive: 200-500ms — Huge hitbox extension, very noticeable to other players.
→ Weapon filters: Only enable for combat items to avoid flagging while mining/building.
→ Require Click: Enable to only backtrack while actively holding attack. Reduces passive detection vectors.
→ Range limits: Keep at reasonable values (6-8 blocks). Attacking from extreme ranges is a red flag.
→ Flush on Damage: When enabled, clears queue immediately on hit. Some servers check for this behavior.