Name

g_antiwarp — enable/set bitflags for antiwarp functionality

Synopsis

g_antiwarp [flags]

Table 13.2. g_antiwarp Flags

FLAGDESCRIPTION
1enable antiwarp functionality
32log player's warping to their desktop

Default

g_antiwarp 1

Description

g_antiwarp enable/sets bitflags for antiwarp functionality.

Warping occurs when the server recieves several new commands for a player in a very short period of time. This happens because packets from the player were lost or never sent. The player will appear to cross a great distance in a very short period of time, making them hard to hit and possibly allowing them to avoid landmine damage.

The antiwarp system delays commands when they are recieved too quickly. Thus, when a player sends 700ms worth of commands in 50ms, the commands will be spread out over 700ms, causing the player to move smoothly to other players. This affects the player who sent the commands too quickly only by increasing their ping, and will not keep increasing ping endlessly - at maximum, the added ping is the highest ping the player is actually getting. If temporary network issues cause ping to increase beyond a sensible number, the player can stand still for a moment and their ping will normalize.

The net effect is that players with unreliable or congested upstream will not benefit from their situation; rather they (in a sense) are penalized for it, while all the other players on the server are not.

[Caution]Caution
Flags enabling extra debug/logging can be extremely network-expensive and should not be used for normal gameplay.

[Note]Note
The initial code implementation for antiwarp was contributed to Jaymod by Zinx Verituse, June 2007.