Statistics / Rankings Terms

There are several settings in silEnT that attempt to determine how "good" a player is in terms (hopefully) more meaningful than just XP or XP per unit of time. Here are the terms used and their definitions:

Kill Rating

How good of a killer the player is, based on how many other players the player kills, and their kill rating. In other words, killing players with a high kill rating increases the shooter's kill rating more than killing players with a low kill rating.

Player Rating

This is a measure of how much the player contributes to winning a map. This measure is calculated by seeing how many times this player is on the winning team after every map, and how good the opposing team was. Like kill rating, winning against teams with a high average player rating results in player rating increasing faster.

Win Probability

The probability that a team will win a map (based on the players' player rating, team size, and the map).

These statistics are gathered by silEnT and the data is saved to local files on disk. This feature is originally from ETPub and no alterations have been made to it by silEnT team.

The ETPub development team member responsible for implementing these player rankings and ratings is Josh Menke. He has been kind enough to begin working on an academic write-up to explain the mathematics and statistics methods behind these rankings. Due to time constraints the document is being gradually updated and expanded. The latest version can be seen here.

Hardware Based Identification

Starting from version 0.3.0, the silEnT mod can be configured to enforce bans using hardware based identification. This is not any fool proof system but it is made to be an addition to the already existing ban methods. The hardware identification cannot be seen in human readable form while on the server. The data that is sent to the server can be seen in the client by making /cg_ident in the console. That is a hexadecimal string which changes its value between maps.

The format and data used to create the client Identification may change between the versions of the silEnT mod. The server can be configured with the g_identOptions server cvar. The cvar is bit flagged which means, you can combine the values by adding them together.

g_identOptions:

1 ; Kick clients that are spoofing the client identification to enter the server.

2 ; Kick clients that are not sending the identification to the server.

4 ; Enforce bans using the identification.

8 ; Report all actions taken based on client identification to the adminchat

16 ; If a player is caught of circumventing a ban, a new ban is created for the player. The ban reason will have additional (Automated copy of a ban for xxxxxxxx) where xxxxxxxx is replaced with the 8 character PB GUID of the old ban.

Server admins can use the !finger command to see the status of any players identification.

If the server is configured to kick for spoofed client identification, it can happen legitimately if the client connects directly from one silEnT server to another. Or if the server they are playing shuts down and they instantly reconnect. Instantly reconnecting again after the Spoofed Client Identification kick will work and the spoofed kick is a single event. If you find out more of these cases, please share the information with the silEnT community on forums.

Team Death Match

Starting from the silEnT version 0.3.0, there is a new gametype available. Team Death Match is a gametype where 2 teams score for kills. A TDM map can be
ended by Score limit, time limit or by both. The TDM game type is controlled by 4 server cvars.

g_TDMType
g_TDMOptions
g_TDMScore
g_TDMObjBonus

Weapon Numbers

MOD_UNKNOWN // 0

MOD_MACHINEGUN // 1

MOD_BROWNING // 2

MOD_MG42 // 3

MOD_GRENADE // 4

MOD_ROCKET // 5

MOD_KNIFE // 6

MOD_LUGER // 7

MOD_COLT // 8

MOD_MP40 // 9

MOD_THOMPSON // 10

MOD_STEN

MOD_GARAND

MOD_SNOOPERSCOPE

MOD_SILENCER

MOD_FG42 // 15

MOD_FG42SCOPE

MOD_PANZERFAUST

MOD_GRENADE_LAUNCHER

MOD_FLAMETHROWER

MOD_GRENADE_PINEAPPLE // 20

MOD_CROSS

MOD_MAPMORTAR

MOD_MAPMORTAR_SPLASH

MOD_KICKED

MOD_GRABBER // 25

MOD_DYNAMITE

MOD_AIRSTRIKE

MOD_SYRINGE

MOD_AMMO

MOD_ARTY // 30

MOD_WATER

MOD_SLIME

MOD_LAVA

MOD_CRUSH

MOD_TELEFRAG // 35

MOD_FALLING

MOD_SUICIDE

MOD_TARGET_LASER

MOD_TRIGGER_HURT

MOD_EXPLOSIVE // 40

MOD_CARBINE

MOD_KAR98

MOD_GPG40

MOD_M7

MOD_LANDMINE // 45

MOD_SATCHEL

MOD_TRIPMINE

MOD_SMOKEBOMB

MOD_MOBILE_MG42

MOD_SILENCED_COLT // 50

MOD_GARAND_SCOPE

MOD_CRUSH_CONSTRUCTION

MOD_CRUSH_CONSTRUCTIONDEATH

MOD_CRUSH_CONSTRUCTIONDEATH_NOATTACKER

MOD_K43 // 55

MOD_K43_SCOPE

MOD_MORTAR

MOD_AKIMBO_COLT

MOD_AKIMBO_LUGER

MOD_AKIMBO_SILENCEDCOLT // 60

MOD_AKIMBO_SILENCEDLUGER

MOD_SMOKEGRENADE

MOD_SWAP_PLACES

MOD_SWITCHTEAM

MOD_GOOMBA // 65

MOD_POISON

MOD_FEAR

MOD_THROWN_KNIFE

MOD_REFLECTED_FF // 69

MOD_PPSH // 70

MOD_SHOVE // 71

Mod Setup Questions

Friendly Fire hitsounds

Q: Friendly Fire hitsounds are not working.

A: Please try to enable warning sound of friendly fire using:

set g_hitsounds "9"

XP save not working

Q: How to get XP save and player stats for one year?

A: Try below settings in your server config:
set g_XPSave 21
set g_dbUserMaxAge "365d"
set g_XPSaveMaxAge_xp "365d"
set g_XPSaveMaxAge "365d"

Forcecvar & sv_cvar

Q: How do I make forcecvar or sv_cvar work?

A: silEnT server is able to force client cvars to certain values or ranges by using forcecvar and sv_cvar commands. sv_cvarempty will clear all the sv_cvar commands the server has loaded.

To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.

Player screenshots (PBSS)

Q: How do I take player screenshot? A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot.

Custom command

[command]
command  = pbss
exec     = takess "[1?]" [i]
desc     = take screenshot from someone
syntax   = [name|number]
levels   = 5 6 7 8 9 10