Rob Run ESP, layer by layer
The ESP is the part everyone sees first and understands last. Five separate draw layers, each with its own switch, its own range and its own failure mode. Here is what each one does and when it helps.
What ESP actually is
ESP is a drawing pass that runs over the finished frame. The game renders as normal, then the overlay paints outlines and markers on top of it. Nothing is read back from the screen, nothing is injected into the render pipeline, and the game never knows a second pass happened.
That matters for two reasons. First, it survives resolution changes and windowed mode because it draws in the same coordinate space the game uses. Second, it can be switched off mid-match without touching a single game asset.
The five layers
Boxes
A rectangle around the character's bounding volume, colour-coded by state: team, civilian, police, hostile. Team-aware highlighting means your own crew never gets drawn as a target. Box colour follows the palette you set on the Colors page, so the same person stays the same colour across layers.
Skeleton
Joints and limbs rather than a box. A box tells you someone is behind a wall; a skeleton tells you which way they are facing, whether they are crouched, and whether the arm is raised. This is the layer experienced players leave on and turn everything else off for.
Head marker
A single dot above the head, sized by distance. It is the cheapest layer to read at range and the one that costs the least attention. If you only run one thing on a second monitor, run this.
Chams
Highlights the body through geometry instead of drawing an outline around it. Chams read better than boxes in dense interiors — warehouses, stairwells, the inside of a base — where an outline can be confused with the architecture behind it.
Vehicle markers
Vehicle chams, vehicle markers, and a switch for occupants. Seat data is only readable on some vehicle types, so occupants are drawn from the vehicle transform and suppressed inside a car when seat data is not available. That suppression is deliberate: a marker stuck to a car door is worse than no marker.
Range, and why two numbers
The two ranges exist because they cost different amounts of attention. A box at 400 m is a useful dot on the horizon. A skeleton at 400 m is a smear of lines that pulls your eye away from what is in front of you. Splitting them lets you keep long-range awareness without cluttering the near field.
Line width matters more than people expect. At 1 px the overlay stays out of the way; at 2–3 px it reads faster on a bright background but starts to obscure the target it is describing. There is no correct answer, only the one you stop noticing.
The visibility check
With visibility on, a target behind geometry renders in a dimmed state and a target in line of sight renders solid. It is a trace against world geometry, not a screen-space test, so it holds when the target is behind a fence, a wall, or the body of a vehicle.
Turn it off if you want the classic look where every target reads the same. Turn it on if you are deciding whether to shoot — the difference between "I know where they are" and "I can hit them from here" is the whole decision.
What it does not do
- It does not draw players who have not spawned into your session.
- It does not reveal loot through the ESP page — that is a separate page with its own filters.
- It does not guess. If the game has not sent a transform for a character, nothing is drawn for that character.
Skeleton on, boxes off, chams off, range 150 m. Play a match. Add layers until the screen stops being readable, then take one back off. That ceiling is your setting, not anyone else's screenshot.
Where it sits in the build
The ESP layers are part of the same overlay as the radar, the labels and the aim assist, driven by one panel and saved to one profile. Loading a profile restores every layer at once — ranges, colours and switches together. There is no per-page save to forget.
Keep reading
Keys are issued one at a time
Lifetime, bound to one machine, updates included. Message @kongthebest on Discord.
See access details