A check on engine and police-system claims
“RAGE 9” is commonly used online as a label for Grand Theft Auto VI's technology, but Rockstar has not publicly identified the game's engine with that version number. The official game pages and media describe Leonida, its characters, and the planned release; they do not provide an engine-version specification.
The same limit applies to detailed claims about police behavior. The requested ideas—six-star heat, persistent witness descriptions, license-plate tracking, line-of-sight search rules, and vehicle fences—may be familiar from earlier games or fan discussion, but that does not prove they work that way in GTA VI. No verified guide can give reproducible in-game steps before those mechanics are demonstrated in the released build or documented by Rockstar.
How we will verify a future guide
After release, a mechanic guide should identify the platform and game version, describe repeatable steps, distinguish observed behavior from interpretation, and link to a primary source where one exists. Until then, this article is a claim check, not an evasion walkthrough. Treat any precise AI or wanted-level table without reproducible footage or a direct source as unverified.
Sources
- Rockstar Games: Grand Theft Auto VI official media
- Rockstar Games: Only in Leonida
- RAGE engine version claim review
Describe the visible cue first
A pursuit shot can show an indicator, a vehicle, or a reaction without exposing the rule behind it. Begin with the visible action and keep the inferred mechanism on a separate line. An edited sequence does not show every state before or after the frame.
The robbery scene analysis follows this method when discussing witnesses. A reaction can be described honestly without assigning an invisible threat variable or claiming a universal line-of-sight rule.
A tactic needs a repeatable starting state
A future evasion guide should identify the platform, build, location, starting conditions, and result. It should explain whether the same action worked more than once and what caused a failure. That is how an interesting observation becomes an instruction another player can evaluate.
The heist preparation guide places the recovery point beside a risky step. It does not promise that changing a vehicle, crossing a boundary, or using an alleged tool will always produce the same result.
Keep the rating distinct from the evidence
A guide writer can describe a sequence as demanding without inventing the number of wanted stars in the finished system. Likewise, an engine label or a fan-made difficulty scale does not explain how a witness, plate, or patrol behaves. Those questions require a source or a controlled test.
Evidence to preserve in an evasion note
- The visible objective and pursuit state.
- The action taken and the actual response.
- The conditions and exceptions encountered during a repeat attempt.
Field note: The completion roadmap should record tested requirements, not a police-system assumption copied from a different game.
Questions & answers
Where does the article’s factual information come from?
Primary sources are linked in the article and its source list. The copy distinguishes a published statement from editorial explanation or an untested claim.
Does this article claim a hands-on test of the unreleased game?
No. Promotional analysis and public announcements do not establish a completed gameplay test, a universal performance target, or an unannounced mechanic.
How can I check whether information has changed?
Read the review date, follow the newest linked official source, and compare any dated update with older coverage before relying on a schedule or purchase claim.
Read our editorial policy for verification and corrections.