CS2 Jump-Throw Bind: Valve Rules & Manual Practice
An old one-key CS2 jump-throw script is not a supported default solution. Valve’s August 19, 2024 input update restricted binds combining specified movement or attack commands. Its accompanying explanation says jump-throws can be performed by jumping and quickly throwing, without special scripts.
Source review: October 12, 2026. This page provides a manual practice and troubleshooting method. It does not certify tournament legality, claim a guaranteed landing point or report client-tested lineups.
What Valve actually changed
In Side-stepping Skill, Valve explains that suspected automation of multiple player actions from one input may lead to a match kick, initially on Valve official servers. The August 19 release notes specify that binds with more than one command from a listed set are ignored by default. They also document a cheat-protected override, which is not an ordinary matchmaking setting.
Two different behaviors are involved: a bind being ignored and suspected input automation causing a kick. Neither statement is a blanket declaration that every script has the same sanction. Nor does moving an automated sequence to different software establish that it is permitted.
Use separate manual inputs
- Choose a practice environment where you can repeat the same throw safely.
- Equip the same grenade and establish a starting position and aiming reference.
- Prepare the intended throw using your normal controls.
- Press your ordinary jump control, then quickly release the throw input yourself. Do not have a macro combine or time the actions.
- Observe the grenade’s actual destination and repeat from the same setup.
This sequence follows Valve’s manual-input description. It is not a millisecond timing prescription or a tested lineup. Different throw setups need their own record. A remembered key sequence does not document the position, view direction or movement that produced a useful result.
Verify the landing, not just the sound
The August release notes discuss a jump-throw confirmation grunt being audible to nearby players. Treat the sound as one observation; it cannot establish that your grenade reached the destination you intended. Record the landing area directly and check whether the resulting smoke or utility serves the purpose of the lineup.
| Keep fixed | Write down | Why the record helps |
|---|---|---|
| Map and build | Map name and test date | A later map or game update may require a new check. |
| Starting position | A screenshot and repeatable positioning reference | Separates setup changes from release changes. |
| Aiming reference | Screenshot at your own display settings | Prevents relying on a vague description such as “a little higher”. |
| Throw setup | Grenade, standing/crouching, any movement | Separates distinct throw methods. |
| Outcome | Landing area and useful/not useful | Checks the actual goal rather than a cue alone. |
A ten-attempt practice record
Before declaring a lineup reliable, define its success condition: for example, landing inside a chosen marked area. Make ten attempts from the recorded setup. Label each attempt successful, unsuccessful or invalid because the setup changed. Keep invalid attempts visible and explain why they were excluded.
Illustrative arithmetic: eight successful throws out of ten valid attempts equals an 80% observed success rate for that practice set. It is not an 80% guarantee for future matches. One successful throw provides much less evidence than repeated results under the same conditions.
| Attempt | Setup reproduced? | Observed landing | Outcome |
|---|---|---|---|
| 1–10 | Yes / No | Your observation | Success / Failure / Invalid |
If the setup is consistent but results vary, concentrate on your manual sequence. If results are consistent but miss the destination, re-check the position and aiming reference. Do not fix both at once; you will lose the ability to identify which change mattered.
Old autoexec keeps restoring the script?
Back up your config before removing an obsolete jump-throw alias or bind. Search your own autoexec and other files it executes for that alias, then review the exact key assignment. Preserve unrelated settings. Use the autoexec file-loading diagnostic to distinguish a file that is not loading from a file that loads a command the game rejects.
Keyboard automation is a separate check: review the manufacturer’s documented feature settings and Valve’s warning about automated inputs. This guide does not provide an automation workaround. For an organized event, consult its current rules and administrator; an official-server announcement is not a complete tournament rulebook.
Review note
This replaces the previous page’s unsupported assurances about a “legal” workaround and mathematically guaranteed throws. The original URL is preserved. Valve’s announcement and release notes establish the input-policy baseline; the worksheet is our suggested verification method, not an official Valve test or a measured result from this site.
