CS2 lineups: a practical guide to grenade utility

What counts as a CS2 lineup?

A complete lineup records where you stand, where you aim, how you throw and what the grenade accomplishes.

The landing spot alone is not enough. Two throws can land in the same area but differ in safety, timing and whether a teammate can act on the utility. A useful record includes the side, the intended round phase and a short result label such as “blocks CT during an A split.”

NadeNerd treats the video timestamp and the two map positions as one unit. That makes the original demonstration easy to verify while the radar pins make the throw easy to retrieve before a match.

Which grenade lineups should you learn first?

Prioritize smokes that remove a dangerous sightline, flashes that let a teammate take space, and mollies that clear a common defender position.

• Smoke: isolate one angle so the team can fight fewer positions at once.
• Flashbang: blind a specific defender without also blinding the teammate who swings.
• Molotov or incendiary: force a player away from cover or delay a chokepoint.
• HE grenade: punish a known damage spot or combine damage with a teammate.
• Decoy: situational misdirection; usually lower priority than the four utility types above.

How do you build a lineup pool that survives match pressure?

Use a five-step loop: choose one round problem, find one throw, verify it, name it clearly and recall it on a schedule.

1. 1

   Choose the round problem

   Start with a real need: entering a site, retaking, delaying a rush or protecting a plant.

2. 2

   Verify the full setup

   Reproduce the stand point, aim point, movement and release. Do not save a clip you have only watched.

3. 3

   Record the result

   Name the blocked angle or cleared position, not the creator or a vague label such as “good smoke.”

4. 4

   Test from a fresh spawn

   Reset and repeat until the landmarks are recognizable without replaying the video.

5. 5

   Recall before play

   Review only the few throws relevant to the map you are about to play.

How can you tell whether a lineup is worth keeping?

Keep a lineup when it is repeatable, fast enough for its round timing, safe enough to set up and tied to a decision your team actually makes.

A pixel-perfect lineup may be impressive but fragile. Prefer stable edges, obvious texture changes and broad landmarks. Note whether the throw is standing, crouched, running or jump-thrown; confusing those inputs is a common cause of missed utility.

Delete or archive throws that solve the same problem less reliably. Curation is part of practice: every unnecessary option adds recall cost during a short buy period.