[ON] Aimbot [ON] ESP [ON] WH ⟳

Off the Grid: Kestrel Executes Its First Ban Wave

Off the Grid’s Kestrel anti-cheat has started enforcement, with recoil scripts, macros, and input remapping accounting for most reported bans.

Off the Grid’s first Kestrel ban wave was announced on October 21, and its most revealing detail is what dominated the enforcement breakdown. Conventional aimbots and wallhacks were a minority: recoil automation, macros, and input manipulation accounted for most reported actions.

Most bans targeted input automation

The developer divided the first wave into four groups:

  • 55% involved recoil compensation, rapid-fire or jitter scripts, and automated movement loops;
  • 27% covered controller-converter remapping and third-party mouse macro setups;
  • 12% concerned automated targeting, including silent aim and rotational aimlock;
  • 6% involved speed manipulation, wallhacks, and other movement or memory exploits.

Together, macros and remapped input represented 82% of the wave. That makes the update relevant beyond players using software that reads or modifies game memory. Kestrel is also looking at behavior and input patterns, so running automation through a mouse profile, controller adapter, or similar external configuration does not inherently place it outside detection.

No total number of banned accounts was disclosed. The percentages show where enforcement was concentrated, but they do not establish how large the wave was.

How Kestrel built its detection baseline

Before applying penalties, Kestrel reportedly processed more than 15 billion gameplay data segments during a passive telemetry phase. The system compared movement curves, server-side information, and signatures to establish a baseline for human play and identify artificial assistance.

Accounts using several methods at once received particular attention. Examples given by the developer included combining input remapping with recoil scripts or pairing rotational aimlock with speed manipulation. Confirmed multi-vector cases were assigned immediate permanent bans under the highest enforcement tier.

This also means the announcement is not simply about a one-time signature sweep. Kestrel is described as remaining active in every match, refining its models and issuing further bans on a rolling basis.

Suspensions also serve as telemetry holds

Kestrel uses three enforcement levels rather than applying the same penalty to every flag:

  • Tier 3 permanently removes accounts confirmed to be using cheat engines, memory manipulation, aimbots, or wallhacks;
  • Tier 2 applies a 30-day suspension for repeated exploit abuse and boosting in a party with confirmed cheaters;
  • Tier 1 places accounts in a seven-day quarantine following initial anomaly flags, deliberate bug abuse, or an ongoing telemetry review.

According to the developer, the temporary tiers have a second purpose. They allow Kestrel to observe how an exploit or tool changes after detection and connect revised signatures to the same source. Player reports are also being used as additional input for the system’s detection models.

What this means for players using software

This announcement does not identify a new client build or say that offsets changed, so it is not evidence that every tool suddenly became technically incompatible. The more immediate issue is detection status. A menu opening correctly or an overlay appearing in-game says nothing about whether Kestrel is recording its behavior for a later enforcement wave.

Before starting a session, check the software update statuses and compare them with the available Off the Grid builds for the current version. Waiting for an explicit provider update is particularly relevant for recoil scripts, mouse macros, and controller remapping because those categories formed the majority of the first wave. A compatibility update can confirm technical operation, but it cannot by itself establish that the setup is not being detected.

There is currently no stated basis for treating an HWID spoofer as mandatory. The developer described permanent loss of account access, but did not announce hardware bans or device-identifier enforcement. This update confirms active detection and enforcement, but it does not establish either the compatibility of a specific tool or the need for an HWID spoofer.

Dominate Off the Grid with our software

Statuses update automatically; ambiguous cases are reviewed manually. Sales may be paused during extended updates.

Open the catalog