Here’s my post on the CAL Forums.

You can’t fix a majority of the problems with scripting, you’d need engine source to properly fix it, instead of using bandaids (scripting)

When you raise sv_fps to 30, quite a few things happen, and there are more downsides to raising it than upsides.. also; there are more issues with it being anything other than 20.. I just post the signifigant ones.

- Physics get whacky. Some/most/all physics that are hard coded to sv_fps 20 wake up too early/too late. They can be fixed, but they won’t be as accurate as they would be with it being 20, since 30 doesn’t divide evenly. Timers are the most common thing to get broken.. Any animations that are controlled server side can also be broken.

- G_RunFrame() is called at 33.3ms intervals on the server. Sometimes, it will get called a frame or 2 late, or 2 early, because of rounding errors.

- Prediction gets fubared, since the built-in engine lag of 50ms is reduced to 33ms, which means there isn’t as much data to predict/interpolate for. High pingers notice this more than low pingers (you can even debug prediction errors to see for yourself)

- Antilag is affected, but nobody uses it because it’s broken. I think IW used/uses a point release from ID with busted antilag.

I’ve always told people to stick with using sv_fps of 20, because things are hard coded around it, and fixing them gets messy.