Config · Guide
CS2 jump-throw rules and useful binds
A jump-throw bind automates jumping and releasing a grenade from one input. Valve announced restrictions on binds combining movement and attack actions in August 2024 and made jump-throws reliable without special scripts. Use supported buy, grenade-slot and chat shortcuts instead, and review every command before adding it to your CS2 config.
Reviewed · Editorial method
What changed for jump-throw binds?
On 19 August 2024, Valve’s Side-stepping Skill announcement and release notes drew a boundary around automated player actions. The notes say binds containing multiple movement or attack inputs are ignored by default. Valve also warned that automation could lead to removal from official-server matches.
The same announcement explains that jump-throws had been made reliable without special scripts. Advice that every CS2 player needs a jump-throw alias is therefore a poor starting point. A recipe’s name, age or presence on a website is not evidence that it works on your current server.
Which binds are useful to build?
| Bind type | What it does | What to review |
|---|---|---|
| Buy bind | Attempts selected purchases on a chosen key | Team side, loadout, equipment and purchase order. |
| Grenade-slot bind | Selects a particular grenade slot | Whether the key replaces a movement or interaction action you need. |
| Chat bind | Sends a chosen message | Message text, team or public chat and the intended key. |
| Practice bind | Controls an offline or practice-only task | Required server settings and separation from your everyday config. |
JumpThrow’s binds builder rejects multi-input automation and keeps practice-only output separate. This is a useful guardrail, not a promise that every command works under every game update or server rule.
Add a file without losing your settings
Use jumpthrow-binds.cfg and load it with exec jumpthrow-binds. Before exporting, inspect the exact commands and existing key assignments. A separate autoexec.cfg option is available; replacing an existing autoexec can remove unrelated settings.
Custom practice binds use practice-binds.cfg; a standalone practice-server setup is another artifact. Keep those purposes distinct.
Review the result, not just the setup
Once your utility keys are comfortable, review utility evidence and replay from an available match. A convenient key assignment does not prove that a flash, smoke or lineup achieved its intended result.
For a different editing workflow, read the bind-generator comparison.
A practical starting point
Keep player inputs manual
Do not assume a legacy jump-throw or null-bind recipe is appropriate for official matches.
Choose a useful shortcut
Start with a buy bind, a grenade-slot key or a chat shortcut you actually need.
Review the command
Read its exact output and check whether the chosen key already has an important action.
Add and test the file
Follow the builder's installation steps and test the result in the appropriate game environment.
Quick answers
Frequently asked questions
Do I need a jump-throw bind in CS2?
Valve's August 2024 announcement says jump-throws were made reliable without special scripts or binds. JumpThrow's generator therefore does not supply automated jump-throw recipes. Practice the game's manual jump and release rather than assuming an old config is needed.
Are all binds allowed in CS2?
No. Valve said multi-action movement or attack binds would be ignored by default and warned that automated player inputs could lead to removal from official matches. Buy, grenade-slot and chat shortcuts are different from automating multiple protected inputs. Check the rules for your server.
How should I install a generated config?
Review it alongside your existing key assignments. JumpThrow normally exports jumpthrow-binds.cfg, loaded with exec jumpthrow-binds. Keep practice commands separate and inspect an explicit autoexec export before replacing an existing file.
Put the guide to work · JumpThrow
Put the guide to work.
Use JumpThrow for the next step, or keep exploring the field guide.