Log file format

BIATCH has two forms of output: messages into the FDS console window that provide a summary of what BIATCH is doing and detailed messages written into 'log/biatch/extended.txt' in your Renegade FDS folder. Those detailed log messages can be used by the BIATCH developers to debug BIATCH; they also contain more information about the culprit's activities than the console messages do. The console messages are also written to the 'log/biatch/main.txt' log file.

General info

Every extended log message has a small description followed by the following information. The information depends on the type of the message, which are further described below.

  • Name: The name of the player in question.
  • SessionTime: How long the player has been playing in the server.
  • IP: The IP address the player used.
  • Ping: The player's ping.
  • BIATCH version: The version of BIATCH that wrote this log file entry. It is the same as the version announced in the console at startup.

Seems to use bighead

No additional information.

Netcode hack (<type of netcode hack>)

Additional information dependant on the type of netcode hack, due to the many messages and improbability that you get one, you best ask a BIATCH coder about how to interpret these exactly.

Note that not all of the general part is included in the message because this information could be unavailible.

Invalid radio message

  • AnnouncementId: The id of the radio message the player tried to send (every renegade string has an id, radio messages are in the range range from 8535 to 8565 (8565 not included).
  • IconId: The icon that would be used to display the message.

Note that not all of the general part is included in the message because this information could be unavailible.

Bandwith too low

  • RequestedBandwidthBudget: The bandwith budget the player tried to set.

Note that not all of the general part is included in the message because this information could be unavailible.

Secret character purchase

  • Type: What the player purchased (refill, infantry, vehicle, beacon, secret (aka extra) infantry or secret vehicle).
  • Index: The Purchase Terminal index (aka the number in the lower-right corner of each PT tile) of the unit the player tried to purchase (this can be used with the "Type:" field to deduce the exact unit purchased)

PT out of range

The same as for 'Secret character purchase', but additionally:

  • Distance: How far the player was from the nearest Purchase Terminal. If the map does not have PTs then it will display "No PT found on map (<mapname>)"
  • PTDistanceThreshold: The value of the 'PTDistanceThreshold' setting in 'cfg/biatch/main.ini'.
  • IsInVehicle: If this shows '1' then the player was in a vehicle when he purchased something. If it is '0' he was not.

Weapon not available

  • Damage: How much damage the player attempted to do.
  • Warhead: The warhead id of the player's weapon he was trying to use. This defines how much damage it will apply to the different armor types used by Renegade.
  • Distance: How far the player was away from his target.
  • IsAutoBanEnabled: The value of the 'IsAutoBanEnabled' setting in 'cfg/biatch/main.ini' in numeric form ('1' is on, '0' is off).
  • Owned ammo types: A list of the weapons the player has used in that game. Each entry is shown as <weaponname>, <lastusedinfo>, where <weaponname> is the preset name of that weapon and <lastusedinfo> is either 'currently selected', 'last selected <num> ms ago' or 'never selected before'.

Weapon not selected

The same as for 'Weapon not available', however not including 'IsAutoBanEnabled', but instead:

  • AllowedAmmoLifetime: The value of the 'AllowedAmmoLifetime' setting in 'cfg/biatch/main.ini'.