The jump-throw in CS2: why the bind went away and how the throw is made now

Valve Changed the Ground Rules for Grenade Throws

Grenade throws in CS2 now operate on a sub-tick basis, meaning movement, shooting, and throwing are no longer dependent on the old tick rate. This shift, outlined on the game's official page, brings a new level of consistency to grenade arcs. As Valve puts it, "Tick rate no longer matters when moving, shooting, or throwing," and "grenades will always fall the same way." This fundamental change means players no longer need scripted command chaining to achieve a reliable throw.

The end goal is clear: Valve wants players to be able to reproduce the same grenade throw every time, without needing the old multi-command binds. The official news page highlights "Improved consistency of grenade jump throws and the accuracy of the jump throw preview camera." This implies Valve is giving players new tools to land the same throw reliably, but through in-game mechanics instead of config file scripts.

Why Command Chaining Is No Longer the Answer

In the past, jump throws often depended on carefully timed command chaining – a sequence of console commands that players would bind to a single key press. However, Valve has now restricted console command use in CS2. The developer community's official CS2 command documentation uses a whitelist system, meaning only commands explicitly allowed by Valve can be used in the console. Worse, certain commands can only function when cheats are enabled by a server – these require the sv_cheats 1 server variable, according to the documentation. This effectively blocks out any jump throws that rely on non-whitelisted or cheat-only console commands.

Moreover, not every command suitable for the console can be used as a launch option – the commands added to the game when it starts, via Steam's settings. Valve's Steam Support page on launch options specifies that while many console commands can be used this way, some cannot. This further restricts the viability of old multi-command throw binds, which often relied on custom launch options to work.

What Valve Gives Players Instead

In place of the old bind system, Valve has introduced a built-in jump-throw helper and a manual timing method for accurate throws. The developer console, accessed through Steam's settings per Valve's support page, is the key to this new system. Valve's CS2 command documentation lists commands like sv_jump_impulse, the initial upward velocity for player jumps, and the jump commands +jump and -jump, which simulate pressing and releasing the jump key.

With these tools, Valve aims to provide players with in-game control over jump throws, rather than relying on config files. The official news page mentions a "preview camera" for jump throws, implying a dedicated tool to help players circle in on the perfect arc each time. While the exact system isn't spelled out in Valve's documentation, the pieces are there: with some practice, players can put together a manual throw by timing their jump and grenade toss in relation to the jump-throw preview camera.

The Manual Jump-Throw Method

The exact sequence for a manual jump throw in CS2 has not been published by Valve, but with the available commands and the throw preview camera, a plausible system emerges:

1. Move the player to the desired throw position.
2. Use the throw-preview camera to frame the target area.
3. At the right moment, execute the jump command (+jump then -jump), and release the grenade simultaneously.
4. Fine-tune the jump height with sv_jump_impulse as needed to hit the target spot.

It's a deceptively simple sequence, but it demands practice to nail down the right timing. Compare this to the old bind system, which aimed to package the whole process into one scripted command.

What Not to Tell Readers

It's crucial not to lead readers astray with outdated or incomplete information. CS2 is a different beast from CS:GO, and many old throw binds simply won't work in the new game.

Don't tell readers to put old CS:GO jump-throw syntax into CS2 config files. Those binds are built on top of the tick-based system Valve has now replaced – an outdated method that won't produce consistent throws in CS2.

Don't encourage players to rely on launch options to twist their jump throw into shape. As Valve's support page makes clear, many console commands don't have an equivalent launch option, and CS2's built-in tools should be enough for a reliable throw.

Why This Changed in CS2, Not CS:GO

This shift in how jump throws work was a necessary change for CS2, not a tweak that could've been done in CS:GO. The new game runs on a revamped engine, with a subtly different model than its predecessor. Valve's official CS2 page emphasizes this, noting that with the new game, "Tick rate no longer matters when moving, shooting, or throwing." This fundamental change, which Valve describes as a move toward sub-tick grenade behavior, sets CS2 apart from CS:GO and demands a fresh approach to jump throws.

With CS2's throw consistency and previews, there's no need for the old multi-command scripts. Now, it's all about manual control, enabled by Valve's in-game systems.

The same smoke. The same spot. But a different way to get there.