How We Verify Lineups

Every lineup on this site goes through the same three steps before it’s published. Skip a step, and it stays in draft — it does not go live.

1. Tested in-game. The lineup is thrown on the live patch, from the exact position described, until it lands consistently. If it needs a jumpthrow or a specific bind to be consistent, that’s noted.
2. Captured on video. Setup, aim, and result are recorded directly from the same session — not staged after the fact, not pulled from someone else’s upload. Original footage only.
3. Published with a verification date. Every lineup page shows “Verified on patch of [date]” so you know exactly how current it is, not just that it “works.”

What the “Verified on patch of …” badge means

It’s the date we last threw this exact lineup in-game and confirmed the smoke, flash, or molotov still lands where it’s supposed to. It is not a publish date — a lineup published a year ago with a recent verification date has been re-checked since.

The re-verification cycle

When Valve ships a patch, we read the notes for anything touching map geometry, smoke behavior, or grenade physics. If a map is affected, every lineup on that map gets re-thrown before its verification date is updated. If a lineup breaks, it’s pulled or corrected — it does not stay up with a false “verified” badge.

This is a recurring workflow, not a one-time pass: it runs every time a relevant patch lands, for as long as the map stays in the active pool.

Why we don’t publish unverified content

A lineup that doesn’t work wastes a round, a smoke, and a player’s trust. We’d rather have fewer lineups on the site than lineups nobody actually tested. If a position is missing data — an exact spot, a throw type — it stays undocumented until someone tests it in-game. Nothing here is guessed.