- Joined
- Jul 13, 2021
- Messages
- 5,021
Context
A recent Counter-Strike update caused Bhopping to become inconsistent in the game and introduced an imbalance where players with their FPS capped to 64 would be able to hit jumps/perfs both more consistently and frequently than those with high FPSes (capped or uncapped). This effect was further amplified by the usage of desubtick script(s), allowing for near-guaranteed bhopping. For a game where movement is critical, like Jailbreak, this gave players a significant advantage over others.
On August 12th, 2025, a patch was implemented by Tech that prevented this exploit through the imposition of a jump penalty through the Source2 game engine, which significantly increased the difficulty of bhopping. While successful in negating the imbalance between players, this came at the cost of bhopping efficacy in general, for all players. A subsequent update from Valve on August 14th, 2025 blocked the ability to change
It became clear that some players were discontent with the impact the jump penalty had on normal gameplay, and in an effort to gather broader, quantifiable input from the community, a survey was put out. Through analysis of the responses to this survey and other key factors, CS Leadership have chosen to modify our approach to handling this inconsistency, effective immediately. You will find a list of changes and how they affect you below.
Moving Forward
If you have any questions regarding these changes, please reply to this post. If you encounter any further issues on the servers, please create a Bug Report.
A recent Counter-Strike update caused Bhopping to become inconsistent in the game and introduced an imbalance where players with their FPS capped to 64 would be able to hit jumps/perfs both more consistently and frequently than those with high FPSes (capped or uncapped). This effect was further amplified by the usage of desubtick script(s), allowing for near-guaranteed bhopping. For a game where movement is critical, like Jailbreak, this gave players a significant advantage over others.
On August 12th, 2025, a patch was implemented by Tech that prevented this exploit through the imposition of a jump penalty through the Source2 game engine, which significantly increased the difficulty of bhopping. While successful in negating the imbalance between players, this came at the cost of bhopping efficacy in general, for all players. A subsequent update from Valve on August 14th, 2025 blocked the ability to change
fps_max while on a server (preventing toggling). Unfortunately, they did not patch the inconsistently itself, and the ability to gain an advantage remained. A decision was made at the time to leave the penalty in-place pending further review.It became clear that some players were discontent with the impact the jump penalty had on normal gameplay, and in an effort to gather broader, quantifiable input from the community, a survey was put out. Through analysis of the responses to this survey and other key factors, CS Leadership have chosen to modify our approach to handling this inconsistency, effective immediately. You will find a list of changes and how they affect you below.
Moving Forward
- The imposed jump penalty will be reverted. This will return the state and feel of bhopping to its typical, base game state.
- Usage of FPS capping to gain an advantage (e.g. bhopping) will now be considered exploiting. Those who choose to do so will be subject to admin action.
- At this time, no new server-imposed mitigations are planned, though this may change as we evaluate the continued impact the inconsistency has on the Jailbreak server.
If you have any questions regarding these changes, please reply to this post. If you encounter any further issues on the servers, please create a Bug Report.
