Open one decisive round, jump to each utility throw and inspect its complete trajectory. Compare the throw and detonation with player movement, contact and the round result. For flashes, check recorded victims; for damaging utility, check recorded damage; for smokes, inspect the intended lane and any available sightline result. Then label the evidence separately from your conclusion: “the flash detonated before the entry and two enemies were recorded blind” is evidence; “this was the best flash” is interpretation.
Start with evidence, not a verdict
A CS2 demo records game state and events. In Memorin, the utility view groups throws by type and round, lets you jump to an individual throw and can draw its complete trajectory in the 3D world. Depending on the recording and processed cache, a throw can also include detonation or landing details, recorded flash victims, utility damage, repeated throws from a nearby origin and smoke-blocked sightline results.
Those observations do not reveal the team’s intended execute, a player’s attention or every voice call. Write two lines for every important grenade:
- Observed: what the replay or event data directly shows.
- Interpretation: what you think the utility was meant to accomplish and whether another choice may have worked better.
This distinction prevents hindsight from turning a visible outcome into certainty about intent. Read what a CS2 demo analyzer can and cannot measure before making broader claims.
A round-by-round utility review workflow
- Choose the round and purpose. Start with an entry, site hold, retake or post-plant where utility plausibly shaped the result.
- Watch once without pausing. Note the first contact, space gained or lost, and the final result.
- Open the utility view. Count the recorded throws and jump to each relevant smoke, flash, HE grenade or fire grenade.
- Show its trajectory. Inspect the release point, path, bounces and destination in the world rather than judging the inventory icon alone.
- Compare the timeline. Look at where teammates and opponents were when the grenade was thrown and when its effect occurred.
- Check recorded outcomes. Use flash-victim events and utility damage where present. For a smoke, use a sightline result only when Memorin reports it as available.
- Write one actionable change. Tie it to an observable cue: teammate position, contact, bomb state or the start of a coordinated move.
What to inspect for each grenade type
Smokes
Follow the trajectory to its destination, then switch to a free or top-down view. Ask which lane it occupied, who could move while it was active and whether teammates used the space. When the review reports smoke-blocked sightlines, treat that as geometric evidence for the reported pairs—not proof that every player was watching or reacting to the smoke. If sightline analysis is unavailable, review the reconstructed scene directly and state that limitation.
Flashbangs
Compare the detonation with the supporting peek. Recorded blinded-player events and durations show who the demo says was affected; they do not prove where a player’s attention was or whether the blind caused the next kill. A flash that affects opponents but arrives after the entry fight may still be poorly coordinated. A flash with no recorded victim may still have forced a turn, but that is an interpretation unless the available replay evidence supports it.
Molotovs and incendiaries
Inspect where the fire appears relative to the intended choke, plant position or clearing route. Then check whether players moved, waited or fought around it and whether recorded utility damage followed. Damage is one outcome, not the only purpose: space denial and delayed movement must be assessed from the round context without inventing player intent.
HE grenades
Check the trajectory, detonation location and recorded utility damage. Compare the throw with known opponent positions visible in the replay. Avoid concluding that a player “knew” an opponent was there unless the preceding POV and events support that information.
Review timing without inventing a magic number
There is no universal “correct” delay between a grenade and a peek. The useful comparison is the sequence recorded in that round. Pause before the throw, at the effect and at first contact, then ask:
- Was the entry player ready to move when the flash or smoke took effect?
- Did defenders regain the lane before teammates arrived?
- Did the throw expose its user or leave another lane unsupported?
- Was the grenade reacting to recorded information or thrown before that information appeared?
- Did teammates duplicate the same function while another required lane remained open?
- Was utility still available when the round reached the situation it was meant to solve?
Describe timing relative to visible events—“before the first player crossed,” “after contact,” or “while the retake players were separated”—instead of relying on an estimated universal constant.
CS2 utility demo review checklist
- What was the round situation and likely utility purpose?
- Who threw it, and from where?
- Where did the complete trajectory end?
- What happened immediately before and after its effect?
- Which flash victims or utility damage are recorded?
- For a smoke, is sightline analysis available, unavailable or unnecessary for this question?
- Did teammates act while the utility created an opportunity?
- Is your conclusion directly observed or an interpretation?
- What single cue should change the next throw or follow-up?
Keep the final note specific: “wait until both entry players reach the choke before throwing the site flash” is testable. “Use flashes better” is not.
Frequently asked questions
How do you review utility in a CS2 demo?
Choose a decisive round, jump to each recorded throw, inspect its trajectory and outcome, then compare its timing with teammate and enemy movement. Record observations separately from tactical interpretation.
Can a demo prove that a smoke or flash was good?
No. It can show recorded state, events and outcomes, but the best tactical choice also depends on plans, communication and intent that may not exist in the demo.
What utility evidence does Memorin show?
Depending on available demo and asset data, the review can show throws by type and round, complete trajectories, detonation or landing details, flash-victim events, utility damage, repeated nearby throws and smoke sightline results.