[JernejL]

Quote:

Originally Posted by nemesis- I had a working /fps command the very same day you posted your whitepaper on it. The logic was simple enough to follow to work out the math. Mine is different though: my /fps brings up a dialog which shows the FPS of every player on the server with an 'update' button to refresh it all. I also do not have the range check that you do since I have other functions that can break the FPS function on a specific player if they start playing with functions that drastically alter their drunk level (i.e. /mdrunk, /wine, /beer, etc). That, or you can just direct it to a player (i.e. /fps <player name>). Come by my server some time and do /fps .

We had this for months as admin-only-manual-drunk-fps-checker in 0.3a on partyserver, and with 0.3b it's public functions: see /fps /goodfps & /laggers, uses dialogs too.

My implementation will not break if you set drunk level (and highier than 2000 drunk level on partyserver is set if you driveby too much)