The main problem with serverside minping is that it affects all the players, not just one player. And the way it does it, it makes movement bad, objects on the world look laggy and adds quite a few different unwanted effects. Now we can tackle this situation and I urge EVERYONE to test what has been achieved. You can download the ezQuake test build from:

http://data.cod.ru/64166788554

Or from the Cokeman's nightlies tomorrow or later.

The command for enabling clientside minping is:

/cl_delay_packet MS

Where MS is the amount of delay in milliseconds. So, lets assume you have ~12,7ms avg ping to the server, this makes your ping in QW to jump around 20ms which is quite bad in the terms of playability. All you have to do is to make:

/cl_delay_packet 2

And this will increase your pingtime to 14,7ms so the ping in QW will be stable 25ms. There should be absolutely no side effects in the terms of playability. You can surely increase your ping as much as you want, but be sure ping the server first to see how much you need to add to make proper results.

Pingtimes should avoid multiplications of the 77fps frametime (12,98ms). So, if you have average pings like ~13ms, ~25ms, ~38ms and so on (these pings make your QW ping jumpy) then you should add 2ms delay or so. Notice that going too much over the borderline pings isn't going to help anything, so keep the delay around 2ms above the desired limit.

(READ: player that has 11ms ping to server making him have 12ms in QW, should only add 27 - 11 = 16ms delay if he wants to have 38ms ping in QW.)

In any case, people need to test this feature so that ezQuake people can see if it works like it should. I have tested it already and it worked pretty good for me, I got the pings I wanted with no negative side-effects like serverside mingping has.