From ac73b9c2e72974478c155a1dd7279255f88d3f80 Mon Sep 17 00:00:00 2001 From: Jeff Teunissen Date: Sat, 7 Oct 2000 20:57:55 +0000 Subject: [PATCH] Provide information on what players can do if they are using an accidentally-speed-cheating client. --- speed_cheat.php | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/speed_cheat.php b/speed_cheat.php index 98233d3..11ef2c9 100644 --- a/speed_cheat.php +++ b/speed_cheat.php @@ -23,7 +23,7 @@

This, along with other factors including lag and packet loss, can cause the time reported by the client to be over the time the server expects. -

Well, what can I do?

+

What can I do as a server admin?

QuakeForge's cheat detection is adjustible within the server, so that administrators can decide what settings work best. Here are descriptions of some of the config variables ("cvars") that you can use to @@ -46,6 +46,18 @@ seconds, the time tally is counted. Lowering this value increases the chance of false positives, but helps to minimize the amount of damage a time-cheating player can cause. Default is 30 seconds. + +

What can I do as a player?

+

Obviously, we suggest using one of QuakeForge's QuakeWorld-compatible + clients (available in the Downloads Section of our + web site), none of which exhibit this problem. If you don't want to use + QuakeForge, you can use + QuakeWorld 2.33-005, + the last "test release" before id Software released the source. + You can also use any of the QuakeWorld-compatible clients released by the + other engine projects, but of course we can't verify that any of them do + not exhibit the problem or even if they work. +