CS2 grenades: buy a purpose, then practise the throw

Utility is easiest to learn when every purchase has a job. A smoke might remove one defender's view while your team crosses. A flash might let a teammate challenge a prepared angle. Fire might force a player to leave a protected position. An HE might punish a location the opponent is likely to occupy. Start with that objective before learning a complicated throw.

The job must connect to an action. If nobody crosses after the smoke, the blocked sightline may accomplish little. If the flash pops while the entry player is still far away, the opportunity may expire before anyone uses it. If fire lands where your team intends to walk, the grenade can obstruct your own plan.

These are purpose categories, not promises of a particular damage value or duration. Current costs, carry limits and buy restrictions belong to the active client and server rules. A private practice configuration may differ from a live match, so check the environment before treating a purchase sequence as universal.

Open the buy menu in the permitted buy period and choose the grenade category available under the current rules. Check the total kit rather than spending every remaining unit automatically. You need the weapon and protection required for your role as well as the utility that enables the plan.

Ask what teammates already have. Five overlapping grenades aimed at the same job can leave another important task uncovered. If one player supplies a smoke and another supplies the supporting flash, everyone should understand the order and the movement that follows. Coordinated modest utility can be more useful than a full belt thrown without a plan.

The CS2 economy guide handles the broader purchase cycle. Here the narrow question is whether each grenade has an intended use before the round begins. If you cannot describe its purpose, consider preserving money or choosing equipment that supports a known action.

Adapt when the round changes. A smoke bought for an early crossing might later protect a different interaction; a flash saved after a stalled attack might support the retreat. A planned purpose is not an obligation to throw at the original location after it stops being useful.

Avoid carrying a grenade in hand while entering an uncleared angle. Choose the protected moment and location for the throw, or ask a teammate to cover. Utility has value only if you remain able to deliver it at a useful time. Dying during an unnecessary preparation step is not evidence that the grenade itself was a poor purchase.

Valve's CS2 introduction describes smoke as volumetric and responsive to gunfire and explosions. That makes it a changing information barrier rather than a flat painted wall. Inspect how it fills the space and how opponents can interact with it instead of assuming a generic cloud behaves identically in every location.

Start with the sightline you want to interrupt. Stand where the opponent would view the crossing and identify the edge that must be covered. Then examine the same smoke from the player's crossing route. A cloud that appears full from one side can still leave a useful angle from another position.

Do not confuse concealed vision with cleared space. An opponent can occupy a position close to a smoke or push through it. Your team still needs a plan for nearby corners, sound information and potential contact at the edge. The smoke reduces one problem; it does not certify the entire route as safe.

Timing matters as much as placement. If the team waits too long after the smoke is established, the intended movement can arrive at the wrong phase. Practise the throw together with the crossing or entry action. A perfect landing with no coordinated follow-up is an incomplete exercise.

After using it, ask what the smoke allowed. Did a teammate cross, did you isolate a defender, or did you merely block a view your team did not need? Evaluate the action it enabled rather than rewarding yourself for reproducing a familiar trajectory.

A popflash aims to give the opponent little useful warning before the flash takes effect. The important comparison is between the defender's view of the grenade and your teammate's timing into the fight. It is not enough that the throw looks quick from the thrower's perspective.

Use a local session with a willing partner. Choose one common defending position and one entry route. Let the defender report when the grenade becomes visible and whether the effect interferes with the intended sightline. The entry player should report whether they can act at the useful moment without being blinded themselves.

Adjust one variable at a time: starting position, aim reference, throw input or timing call. If you change all of them after a failed attempt, you cannot identify the cause. Begin with a simple nearby throw or bounce you can repeat rather than a visually impressive long-distance setup.

Use a clear spoken sequence. The thrower announces readiness, the entry player confirms position and the action begins on an agreed cue. Avoid vague calls such as flashing now when the other player has no time to orient. Coordination should be part of the drill, not an assumed benefit of knowing a lineup.

Do not promise that an opponent cannot turn away or that a flash guarantees a kill. Position, attention and response vary. The practical goal is a better opportunity with a known teammate action. If the defender can easily see the grenade early, alter the setup and test again rather than giving the throw a popflash label because it sometimes works.

Choose fire utility because you want a particular area to become harder to hold or cross. Define that area precisely enough to inspect the result: a corner, a route segment or a protected position. Throwing near a general site name does not prove the intended defender was pressured.

After the throw, inspect where the effect reaches and what escape remains. A player forced out of one position may move into another angle your team has not covered. Coordinate who watches that response. Utility that moves an opponent is most useful when the team is ready for the movement it creates.

Do not treat the T-side Molotov and CT-side incendiary as interchangeable in every numerical detail. The current client and patch notes determine costs and behavior. This guide does not invent identical duration, spread or damage figures to make a tidy table.

Consider your own route. If the team needs to enter immediately, fire in the wrong place can delay the attack or split the group. Decide whether the purpose is clearing, delaying or redirecting, then make sure the movement matches it. A grenade can land where you aimed and still be tactically wrong.

Practise a follow-up with the weapon ready. The throw should lead into holding an escape angle, moving with the team or returning to cover. Remaining exposed to watch the flames can turn a useful action into an avoidable death. Evaluate both the effect area and the thrower's recovery.

For Inferno, begin with smoke objectives rather than unverified pixel references. On a B approach, identify which CT-side view or nearby defensive route your team wants to separate from the entry. On an A approach, identify the sightline that prevents the intended crossing or plant plan. Agree the callout locally so the whole team means the same place.

Load the current Inferno build in an allowed local practice session. Where the current interface offers a relevant official starter guide, use it as a starting reference rather than assuming an old community clip still matches the map. Valve's March 2026 update added starter map guides; availability and permitted guide use depend on the current environment.

Choose one target sightline and inspect it from the defender's position. Find a repeatable throw from a safe place your team can actually reach. Record the standing point, visible aim reference, movement state and input sequence only after you have checked the result. This guide does not fabricate those coordinates or claim that a specific throw was tested here.

Walk both edges of the resulting smoke. Check whether the intended crossing remains visible from an alternate position and whether the cloud creates an unexpected close-contact space. A smoke is not complete because its center lands near the desired spot; its boundary must answer the actual sightline question.

Then rehearse the team action. On B, a smoke that isolates one view still leaves nearby site positions to clear. On A, a blocked lane does not remove every player close to the entry. Pair the smoke with the correct flash, weapon readiness and spacing instead of treating it as a site-clearing button.

Recheck after a relevant map or grenade update. Save the build date with your notes and retire a reference when it no longer produces the intended coverage. The goal is a small set of verified useful throws, not a large archive of impressive but unreliable lineups.

A grenade can fail because of execution, coverage, timing or the team's response. Separate these before replacing the throw. If the landing is correct but nobody acts, the problem is not the aim reference. If the timing is correct but a gap remains, repeating the same call louder will not repair coverage.

Use the practice-commands guide for the separate local setup workflow. Apply practice features only in environments you control or have permission to configure. This page focuses on evaluating outcomes, so it does not duplicate a command catalogue or suggest modifying public competitive servers.

The Mirage smoke guide is a related map-specific page. Keep those references separate: a principle about checking coverage transfers, while a lineup's standing point and aim reference belong to its actual map and version.

• Buy a grenade for a named sightline, position or timing.
• Confirm which teammate acts after the throw.
• Practise from a safe position that exists in the real route.
• Keep starting state and input sequence repeatable.
• Inspect the result from the opponent's viewpoint.
• Check smoke boundaries and fire escape routes.
• Rehearse the movement after the grenade, not just its flight.
• Date your notes and recheck after relevant updates.

Use the FPS & aim topic for surrounding mechanics. Learn one complete utility play before adding several unrelated throws. A complete play includes the purchase, protected delivery, effect, teammate action and recovery. That is a more useful unit of progress than the number of lineups you can recite.

Native CS2 grenades do not define PvPStrike, our separate CS-style browser shooter. Use the CS2 1v1 comparison and browser FPS overview before assuming a Valve lineup or weapon rule transfers.

Hypothetical USD example A: $1 each creates $2; our 5% combined-pot FPS fee takes $0.10, leaving $1.90 winner credit and +$0.90 net. Hypothetical USD example B: $5 each creates $10; $0.50 fee leaves $9.50 credit and +$4.50 net. Losing costs the entry; these examples are not reported results.

The FPS money hub, crypto FPS explanation and fairness page cover the separate product. Cash participation is 18+ where permitted, actual entries must be checked in the lobby, and server validation does not promise cheating immunity. Learning a smoke is not evidence of expected cash returns.