Mirage smokes: learn the blocked sightline before the throw

These are coverage objectives, not verified pixel lineups. Use Mirage callouts to agree on which gap your team means.

1. Load current Mirage in local practice and record the version/date.
2. Use a clearly identified standing position, aim reference and throw type from a current source.
3. Throw repeatedly, not just once, to expose inconsistent positioning.
4. Inspect both ends of the sightline and the smoke edges.
5. Repeat without trajectory aids before relying on it in a match.

Practice commands explains the local/server boundary. Valve’s smoke description establishes interaction with bullets and explosions; it does not validate a community lineup.

Blocking an angle is useful only if someone crosses while it is blocked. Avoid throwing a full set while the team remains too far away to use it. Also identify which defender route remains visible: utility can reduce the number of angles, not guarantee an uncontested entry.

Choose a practice goal through aim maps, then rehearse the actual route. The map pool guide explains why event and mode versions matter.

PvPStrike is a rifle-and-cover browser arena; this page does not claim its loadout includes Mirage utility. Use 1v1 strategy for that arena and the FPS topic for native CS2 guides.

Use Inferno callouts to identify banana, the sites and the routes a smoke is meant to cover. Mirage coordinates do not transfer. The CS2 grenade guide explains how a smoke, flash or incendiary serves a round decision before you memorize its throw.