Practice routine
How to practice CS2 lineups in a focused 15-minute session
To practice CS2 lineups efficiently, work on one map and no more than three throws at a time. Reproduce each throw from a fresh setup, inspect its result from the target side, then recall it once without the source video. Finish by saving only the throws you can explain and repeat.
Key takeaways
- Practice one map and at most three new throws per session.
- Reset the full setup between attempts.
- Inspect the result from the opponent's side.
- End with a no-video recall test and schedule the next review.
What should you prepare before practicing lineups?
Choose one map, one round problem and up to three candidate throws before opening a private practice session.
A narrow goal prevents the session from becoming an endless search through videos. Pick utility for the same route or role so the throws share useful context—for example, three pieces needed for one site entry.
Keep NadeNerd open on a second screen or phone. Save the source timestamp and map positions only after the throw works in your own session.
What is the 15-minute CS2 lineup routine?
Use two minutes to choose, nine minutes to reproduce and inspect, then four minutes to recall and record.
- 1
Minutes 0–2: define the job
State the round problem and choose up to three throws that solve it.
- 2
Minutes 2–5: reproduce throw one
Copy the full stand, aim and movement setup, then inspect the result from the destination.
- 3
Minutes 5–8: reproduce throw two
Reset between attempts and replace vague landmarks with ones you can describe aloud.
- 4
Minutes 8–11: reproduce throw three
Skip the third throw if either earlier setup is still inconsistent.
- 5
Minutes 11–14: recall without video
Perform each saved throw from memory after approaching the position normally.
- 6
Minute 15: record the next review
Write the result, tag the side and schedule a short review before the next match on that map.
When has a lineup passed practice?
A lineup passes when you can rebuild the setup, land it repeatedly and explain what the team should do next.
- You recognize the stand point without tracing the creator's exact movement.
- You can name the aim landmark in plain language.
- You remember whether the throw is standing, moving, crouched or jump-thrown.
- The grenade produces the required coverage or effect on repeated attempts.
- You know the teammate action or round timing that makes it useful.
When should you review a practiced lineup?
Review it the next day, before the next match on that map and after any relevant map or grenade update.
The first delayed recall matters more than another immediate repetition. If you miss the next-day attempt, inspect the saved clip once, improve the label and retry from a fresh setup.
Do not review the whole library before every match. Filter to the map, side and utility needed for your likely role; focused retrieval is the skill you need during play.
Open a supported map workspace
Pin the thrower and landing positions, attach the exact source timestamp and filter the saved lineup by side and grenade type.
Common questions
How long should I practice CS2 lineups?
A focused 15-minute session is enough for two or three throws. Short delayed reviews are more useful than adding many new lineups in one sitting.
How many times should I land a lineup?
There is no universal number, but three clean attempts from a reset setup is a practical minimum before the first no-video recall test.
Should I save a lineup before testing it?
Use a temporary candidate if needed, but keep the main library curated. Save a match-ready record only after you reproduce and inspect the throw yourself.
Sources and update checks
NadeNerd separates stable practice advice from details that Valve may change. Current gameplay and command claims should be checked against primary sources after an update.
- Counter-Strike 2 release notes — Check relevant updates before diagnosing a previously reliable throw.
Related CS2 lineup guides
Written by NadeNerd. The organization that builds and maintains the map-based CS2 lineup library.
See the editorial and testing policy for sourcing, corrections and the difference between documented, tested and editorial guidance.