# A solution to FPS 'fairness'?

**URL:** <https://forums.sourceruns.org/t/a-solution-to-fps-fairness/2428>\
**Category:** λ Half-Life\
**Created:** [August 19, 2014, 4:03pm UTC](https://forums.sourceruns.org/t/a-solution-to-fps-fairness/2428 "2014-08-19T16:03:59Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Matherunner](https://b-cdn.sourceruns.org/user_avatar/forums.sourceruns.org/matherunner/32/215_2.png) [@Matherunner](https://forums.sourceruns.org/u/Matherunner)\
**Post date:** [August 31, 2014, 11:07am UTC](https://forums.sourceruns.org/t/a-solution-to-fps-fairness/2428/21 "2014-08-31T11:07:26Z")

</div>

> [@PJC](#):
>
> EDIT: A good feature for Bunnymod might be to have some sort of system that caps bhop when going over 100fps and vice versa, that way you cannot make use of the non-legit combination, also meaning that Steam traits runs cannot be compared with WON traits runs.

I assume you want to prevent cheating. But then one can abuse such system by airstrafing at 1000 fps, then switch to 100fps just before jumping to avoid triggering the cap.

I don’t think it is possible to implement frame rate restrictions robustly. You need to check the recorded demos if you don’t trust the runner.

---

_[View the full topic](https://forums.sourceruns.org/t/a-solution-to-fps-fairness/2428)._