MyGamingTalk - User contributions [en]

Silent Lua

2015-08-30T18:40:21Z

Silencerpl:

silEnT servers support Lua 5.1.4 scripts up till version 0.8.2. 
Since version 0.9.0 silEnT mod supports Lua 5.3.1 compiled to be compatible with Lua version 5.2. 
Starting from version 0.5.1 the Lua interpreter is inbuilt into the server side mod. Before the vesion 0.5.1, the Lua was installed as an external module. A separate build of the silEnT mod is supplied within the download to admins who still want to use separate Lua library. silEnT's Lua API is aiming to be fully compatible to ETPro's Lua API. The origin of the silEnT Lua API is the Lua module in ETPub version 0.9.1.

= Cvars =
== lua_modules ==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules ==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL). If this string is empty, all loaded modules are allowed.

'''Type:''' string

'''Default:''' ""

= Commands =
== lua_status ==

Shows information about the scripts currently loaded by the Lua API server engine. This command works also from the client so that players can check what modules are currently loaded by the server.

= Interface Function Reference =
== Modules ==

=== RegisterModname ===

'''Description'''

Registers a descriptive name for this Lua module.

'''Syntax'''

et.RegisterModname( modname )

*''modname'' is the name to register the Lua module

'''Portability'''

Function is ETPro compatible.

=== FindSelf ===

'''Description'''

Returns a number indicating the VM slot the current mod is loaded into.

'''Syntax'''

vmnumber = et.FindSelf()

'''Portability'''

Function is ETPro compatible.

=== FindMod ===

'''Description'''

Returns the registered module name and the SHA-1 signature of the module loaded in the VM. Do note that each loaded Lua module will have it's own VM.

'''Syntax'''

modname, signature = et.FindMod( vmnumber )

* ''vmnumber'' is the number of the VM in where the Lua module is loaded

* return value (''modname'', ''signature'') is the registered module's name and the SHA-1 signature. Returns (nil, nil) if there is no module loaded into the given VM number

'''Portability'''

Function is ETPro compatible.

=== IPCSend ===

'''Description'''

Inter Process Communication. This function enables communication between different loaded Lua modules.

'''Syntax'''

success = et.IPCSend( vmnumber, message )

* ''vmnumber'' is the number of the loaded module message is sent

* ''message'' is the string to send

* return value ''success'' is 1 if success and 0 if function fails

'''Portability'''

Function is ETPro compatible.

== Printing ==
=== G_Print ===

'''Description'''

Prints text to the server console.

'''Syntax'''

et.G_Print( text )

* ''text'' is the printed string

'''Portability'''

Function is ETPro compatible.

=== G_LogPrint ===

'''Description'''

Prints text to the server console and also to the log.

'''Syntax'''

et.G_LogPrint( text )

* ''text'' is the printed and logged string

'''Portability'''

Function is ETPro compatible.

== Argument Handling ==
=== ConcatArgs ===

''' Description'''

Function concatenates server command arguments into one string.

'''Syntax'''

args = et.ConcatArgs( index )

* ''index'' is the index of the first argument in the concatenated string. First command argument index in general is 1.

* return value ''args'' is the concatenated string

'''Portability'''

Function is ETPro compatible.

=== trap_Argc ===

'''Description'''

Function returns the number of the arguments in the server command.

'''Syntax'''

argc = et.trap_Argc()

* return value ''argc'' is the count of arguments. For example for the command "/m gao message", the function would return 2.

'''Portability'''

Function is ETPro compatible.

=== trap_Argv ===

'''Description'''

Function returns argument in the given index.

'''Syntax'''

arg = et.trap_Argv( index )

* ''index'' is the argument index to return.

* return value ''arg'' is the argument

'''Portability'''

Function is ETPro compatible.

== Cvars ==
=== trap_Cvar_Get ===

'''Description'''

Returns the value of the given cvar.

'''Syntax'''

cvarvalue= et.trap_Cvar_Get( cvar )

* ''cvar'' is the name of the cvar

* return value ''cvarvalue'' is a string containing the value. If there is no cvar with the given name, the returning string has zero length.

'''Portability'''

Function is ETPro compatible.

=== trap_Cvar_Set ===

'''Description'''

Sets value to a cvar.

'''Syntax'''

et.trap_Cvar_Set( name, value )

* ''name'' is the name of the cvar to set

* ''value'' is the new value for the cvar

'''Portability'''

Function is ETPro compatible.

== Configstrings ==
=== trap_GetConfigstring ===

'''Description'''

Returns contents of the configstring at index.

'''Syntax'''

configstringvalue = et.trap_GetConfigstring( index )

* ''index'' is the index of the configstring

* return value ''configstring'' contains the full config string

'''Portability'''

Function is ETPro compatible.

=== trap_SetConfigstring ===

'''Description'''

Function sets the full configstring.

'''Syntax'''

et.trap_SetConfigstring( index, configstringvalue )

* ''index'' is the configstring index

* ''configstringvalue'' is the full configstring to set

'''Portability'''

Function is ETPro compatible.

== Server Console and Client Handling ==
=== trap_SendConsoleCommand ===

'''Description'''

Sends command to the server console.

'''Syntax'''

et.trap_SendConsoleCommand( when, command )

* ''when'' tells when the command is executed. Possible values are
::et.EXEC_NOW - executes instantly
::et.EXEC_INSERT - inserts at the current position but doesn't run yet
::et.EXEC_APPEND - appends at the end of the command buffer
* ''command'' is the full command to execute

'''Portability'''

Function is ETPro compatible.

=== trap_DropClient ===

'''Description'''

Disconnects client from the server.

'''Syntax'''

et.trap_DropClient( clientnum, reason, ban_time )

* ''clientnum'' is the slot number of the client to disconnect
* ''reason'' is the descriptive reason for the kick. This is also displayed to the client.
* ''ban_time'' is optional length of the kick. If this is not set, the g_defaultBanTime is used.

'''Portability'''

Function is ETPro compatible.

=== trap_SendServerCommand ===

'''Description'''

Function sends reliable server command to a client. I.e. the command is acknowledged by the client to ensure it has received it.

'''Syntax'''

et.trap_SendServerCommand( clientnum, command )

* ''clientnum'' is the slot number of the client to send the command. If the number is -1, the command is sent to all connected clients.
* ''command'' is the full command string to send

'''Portability'''

Function is ETPro compatible.

=== ClientNumberFromString ===

'''Description'''

Function finds one matching player name based on the given string.

'''Syntax'''

clientnum = et.ClientNumberFromString( string )

* ''string'' is a pattern to match against client names
* return value ''clientnum'' is the client slot number if one match is found, otherwise -1 is returned

'''Portability'''

ETPro does not implement this function. Function is derived to silEnT from ETPub implementation.

=== G_Say ===

'''Description'''

Writes to chat on behalf of a client.

'''Syntax'''

et.G_Say( clientNum, mode, text )

* ''clientNum'' is the slot number of the client on behalf to write chat
* ''mode'' is the type of chat to write. Possible values are
::et.SAY_ALL - writes to the global chat
::et.SAY_TEAM - writes to the team chat of the client
::et.SAY_BUDDY - writes to the fireteam chat of the client
::et.SAY_TEAMNL - writes to the team chat of the client without position
* ''text'' is the chat message to write

'''Portability'''

Function is ETPro compatible.

=== ClientUserinfoChanged ===

'''Description'''

Loads the new userinfo string of the client and sets the client settings to match it.

'''Syntax'''

et.ClientUserinfoChanged( clientNum )

*''clientNum '' is the slot number of the client who's userinfo is loaded

'''Portability'''

Function is ETPro compatible.

=== trap_GetUserinfo ===

'''Description'''

Returns the userinfo string of a client.

'''Syntax'''

userinfo = et.trap_GetUserinfo( clientnum )

* ''clientnum'' is the slot number of the client who's userinfo is returned
* return value ''userinfo'' is the full userinfo string of that client

'''Portability'''

Function is ETPro compatible.

=== trap_SetUserinfo ===

'''Description'''

Sets the userinfo string of the client to the passed userinfo. To make the changes to take effect in the game, ClientUserinfoChanged must be called after this function.

'''Syntax'''

et.trap_SetUserinfo( clientnum, userinfo )

* ''clientnum'' is the slot number of the client who's userinfo is changed
* ''userinfo'' is the full new userinfo of the client

'''Portability'''

Function is ETPro compatible.

=== G_Damage ===

'''Description'''

Damages target entity on behalf of the attacker entity.

'''Syntax'''

et.G_Damage( target, inflictor, attacker, damage, dflags, mod )

*''target'' is the entity number to damage, value must be 0 or more
*''inflictor'' is the entity number that does the damage, value must be 0 or more
*''attacker'' is the entity number that causes the inflictor entity to cause damage to target, value must be 0 or more
*''damage'' is the amount of damage to inflict
*''dflags'' is the type of damage to inflict, possible values are
::DAMAGE_RADIUS - damage was indirect (from a nearby explosion)
::DAMAGE_NO_ARMOR - armor does not protect from this damage
::DAMAGE_NO_KNOCKBACK - do not affect velocity, just view angles
::DAMAGE_NO_PROTECTION - kills godmode, armor, everything
*''mod'' is the means of death, possible values are:
::0 - MOD_UNKNOWN
::1 - MOD_MACHINEGUN
::2 - MOD_BROWNING
::3 - MOD_MG42
::4 - MOD_GRENADE
::5 - MOD_ROCKET
::6 - MOD_KNIFE
::7 - MOD_LUGER
::8 - MOD_COLT
::9 - MOD_MP40
::10 - MOD_THOMPSON
::11 - MOD_STEN
::12 - MOD_GARAND
::13 - MOD_SNOOPERSCOPE
::14 - MOD_SILENCER
::15 - MOD_FG42
::16 - MOD_FG42SCOPE
::17 - MOD_PANZERFAUST
::18 - MOD_GRENADE_LAUNCHER
::19 - MOD_FLAMETHROWER
::20 - MOD_GRENADE_PINEAPPLE
::21 - MOD_CROSS
::22 - MOD_MAPMORTAR
::23 - MOD_MAPMORTAR_SPLASH
::24 - MOD_KICKED
::25 - MOD_GRABBER
::26 - MOD_DYNAMITE
::27 - MOD_AIRSTRIKE
::28 - MOD_SYRINGE
::29 - MOD_AMMO
::30 - MOD_ARTY
::31 - MOD_WATER
::32 - MOD_SLIME
::33 - MOD_LAVA
::34 - MOD_CRUSH
::35 - MOD_TELEFRAG
::36 - MOD_FALLING
::37 - MOD_SUICIDE
::38 - MOD_TARGET_LASER
::39 - MOD_TRIGGER_HURT
::40 - MOD_EXPLOSIVE
::41 - MOD_CARBINE
::42 - MOD_KAR98
::43 - MOD_GPG40
::44 - MOD_M7
::45 - MOD_LANDMINE
::46 - MOD_SATCHEL
::47 - MOD_TRIPMINE
::48 - MOD_SMOKEBOMB
::49 - MOD_MOBILE_MG42
::50 - MOD_SILENCED_COLT
::51 - MOD_GARAND_SCOPE
::52 - MOD_CRUSH_CONSTRUCTION
::53 - MOD_CRUSH_CONSTRUCTIONDEATH
::54 - MOD_CRUSH_CONSTRUCTIONDEATH_NOATTACKER
::55 - MOD_K43
::56 - MOD_K43_SCOPE
::57 - MOD_MORTAR
::58 - MOD_AKIMBO_COLT
::59 - MOD_AKIMBO_LUGER
::60 - MOD_AKIMBO_SILENCEDCOLT
::61 - MOD_AKIMBO_SILENCEDLUGER
::62 - MOD_SMOKEGRENADE
::63 - MOD_SWAP_PLACES
::64 - MOD_SWITCHTEAM
::65 - MOD_GOOMBA
::66 - MOD_POISON
::67 - MOD_FEAR
::68 - MOD_THROWN_KNIFE
::69 - MOD_REFLECTED_FF
::70 - MOD_PPSH
::71 - MOD_SHOVE

'''Portability'''

Function is implemented in ETPro but some of the mod values may differ.

=== ClientIsFlooding ===

'''Description'''

Tells if ''g_floodthreshold'' has been exceeded for the player. In other words, the client is sending more than a ''g_floodthreshold'' amount of messages per second to the server. Admins with shrubbot flag 2 are excluded.

'''Syntax'''

flooding = et.ClientIsFlooding( clientnum )

*''clientnum'' is the slotnumber of the client that is checked
*return value ''flooding'' is 1 if the clientis flooding, 0 otherwise

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_AddSkillPoints ===
'''Description'''

Adds points to the client's skill.

'''Syntax'''

et.G_AddSkillPoints( clientNum, skill, points )

*''clientNum'' is the slot number of the client
*''skill'' identifies the skill that the points are added, possible values are
::0 - SK_BATTLE_SENSE
::1 - SK_EXPLOSIVES_AND_CONSTRUCTION
::2 - SK_FIRST_AID
::3 - SK_SIGNALS
::4 - SK_LIGHT_WEAPONS
::5 - SK_HEAVY_WEAPONS
::6 - SK_MILITARY_INTELLIGENCE_AND_SCOPED_WEAPONS
::7 - SK_NUM_SKILLS
*''points'' is the amount of points to add

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_LoseSkillPoints ===
'''Description'''

Causes player to lose skill points.

'''Syntax'''

et.G_LoseSkillPoints( clientNum, skill, points )
*''clientNum'' is the slot number of the client
*''skill'' is the skill from where the points are taken, possible values are
::0 - SK_BATTLE_SENSE
::1 - SK_EXPLOSIVES_AND_CONSTRUCTION
::2 - SK_FIRST_AID
::3 - SK_SIGNALS
::4 - SK_LIGHT_WEAPONS
::5 - SK_HEAVY_WEAPONS
::6 - SK_MILITARY_INTELLIGENCE_AND_SCOPED_WEAPONS
::7 - SK_NUM_SKILLS
*''points'' is the amount of points to remove

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_QueryClientCvar ===

Lua scripts can query cvar values from connected players. The values are returned in a different callback function.

'''Syntax'''

et.G_QueryClientCvar( clientNum, cvarName)
*''clientNum'' is the slot number of the player
*''cvarName'' is the name of the cvar that is requested

'''Portability'''

Function was added in silEnT version 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

== String Utility Functions ==
=== Info_RemoveKey ===
'''Description'''

Removes a key and it's associated value from an infostring.

'''Syntax'''

infostring = et.Info_RemoveKey( infostring, key )
*''infostring'' as a passed parameter is the infostring from which to remove the key
*''key'' is the key to remove
*return value ''infostring'' is the infostring without the key

'''Portability'''

Function is ETPro compatible.

=== Info_SetValueForKey ===
'''Description'''

Sets a value in an infostring.

'''Syntax'''

infostring = et.Info_SetValueForKey( infostring, key, value )
*''infostring'' as passed parameter is the original infostring
*''key'' is the key to set
*''value'' is the value to set to the key
*return value ''infostring'' is the modified infostring

'''Portability'''

Function is ETPro compatible.

=== Info_ValueForKey ===
'''Description'''

Returns a value from an infostring.

'''Syntax'''

keyvalue = et.Info_ValueForKey( infostring, key )
*''infostring'' is the infostring from where to search the key
*''key'' is the key which value is returned
*return value ''keyvalue'' is the value from the searched key

'''Portability'''

Function is ETPro compatible.

=== Q_CleanStr ===
'''Description'''

Removes all Enemy Territory color codes and special characters from a string. The returning string will be ASCII characters of the range [32,126] in decimal numbers.

'''Syntax'''

cleanstring = et.Q_CleanStr( string )
*''string'' is the string to clean
*''cleanstring'' is the cleaned string

'''Portability'''

Function is ETPro compatible.

== Filesystem ==
=== trap_FS_FOpenFile ===
'''Description'''

Opens a file in the local file system.

'''Syntax'''

fd, len = et.trap_FS_FOpenFile( filename, mode )
*''filename'' is the name of the file to open. The file is opened under the current working directory and absolute paths will not work.
*''mode'' is the mode the file is opened, possible values are
::et.FS_READ - opens the file for reading only
::et.FS_WRITE - opens the file for writing, truncates the old file if a file with name ''filename'' already exists
::et.FS_APPEND - opens the file for writing at the end of file, the old file is not erased if it already exists
::et.FS_APPEND_SYNC - like et.FS_APPEND but the file buffer is flushed to the file on hard drive directly after every write operation
*return value (''fd'', ''len'') is the descriptor (or handle in Windows terminology) of the file and the length of the file

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Read ===
'''Description'''

Reads from an open file.

'''Syntax'''

filedata = et.trap_FS_Read( fd, count )
*''fd'' is the descriptor of the file to read
*''count'' is the amount of bytes to read
*return value ''filedata'' will have the read bytes

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Write ===
'''Description'''

Writes at the end of an open file.

'''Syntax'''

count= et.trap_FS_Write( filedata, count, fd )
*''filedata'' is a block of bytes to write
*''count'' is the size of the block to write
*''fd'' is the descriptor of the file
*return value ''count'' is the amount of bytes written to the file

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Rename ===
'''Description'''

Renames a file in the loal file system.

'''Syntax'''

et.trap_FS_Rename( oldname, newname )
*''oldname'' is the name of the file to rename
*''newname'' is the name the old file name is changed

'''Portability'''

Function is ETPro compatible.

=== trap_FS_FCloseFile ===
'''Description'''

Closes an opened file.

'''Syntax'''

et.trap_FS_FCloseFile( fd )
*''fd'' is the descriptor of the opened file

'''Portability'''

Function is ETPro compatible.

== Sounds and Models ==
=== G_SoundIndex ===
'''Description'''

Returns the configstring index that includes the searched sound name.

'''Syntax'''

soundindex = et.G_SoundIndex( filename )

*''filename'' is the sound file name that is searched
*return value ''soundindex'' is the config string index that includes the ''filename'' or 0 if the name was not found

'''Portability'''

Function is ETPro compatible.

=== G_ModelIndex ===
'''Description'''

Returns an index to the configstring that include the searched model.

'''Syntax'''

modelindex = et.G_ModelIndex( filename )
*''filename'' is the name that is searched through the config strings
*return value ''modelindex'' is the configstring number that included the ''filename'' or 0 if not found

'''Portability'''

Function is ETPro compatible.

=== G_globalSound ===
'''Description'''

Plays a sound to all connected clients.

'''Syntax'''

et.G_globalSound( sound )
*''sound'' is the name of the sound to play

'''Portability'''

Function is ETPro compatible.

=== G_Sound ===
'''Description'''

Plays a sound originating from position of an entity.

'''Syntax'''

et.G_Sound( entnum, soundindex )
*''entnum'' is the number of the entity which position is used as the sound origin
*''soundindex'' is the index of the sound that is played

'''Portability'''

Function is ETPro compatible.

=== G_ClientSound ===
'''Description'''

Plays a sound originating from a client entity to the team members of that client.

'''Syntax'''

et.G_ClientSound( clientnum, soundindex )
*''clientnum'' is the slot number of the connected player
*''soundindex'' is the index to the sound to play

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub Lua implementation.

== Entities ==
=== G_Spawn ===
'''Description'''

Spawns a new entity.

'''Syntax'''

entnum = et.G_Spawn()
*return value ''entnum'' is the number of the new entity

'''Portability'''

Function is ETPro compatible.

=== G_TempEntity ===
'''Description'''

Spawns a new temp entity to a location.

'''Syntax'''

entnum = et.G_TempEntity( origin, event )
*''origin'' is the location the temp entity is placed
*''event'' is the event type of the entity, this is a number from the range [1, 118]
*return value ''entnum'' is the number of the new entity

'''Portability'''

Function is ETPro compatible, but some event types do differ from mod to mod.

=== G_FreeEntity ===
'''Description'''

Deletes an entity.

'''Syntax'''

et.G_FreeEntity( entnum )
*''entnum'' is the number of the entity to remove

'''Portbility'''

Function is ETPro compatible.

=== G_EntitiesFree ===
'''Description'''
Calculates all free entities. Free client entities (slots) are not counted.

'''Syntax'''

count = et.G_EntitiesFree()
*return value ''count'' is the number of free entities

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub Lua implementation, where it is broken.

=== G_GetSpawnVar ===
'''Description'''

Return a value of a spawnvar.

'''Syntax'''

spawnval = et.G_GetSpawnVar( entnum, key )
*''entnum'' is the entity number of the target
*''key'' is the key for the value to return, possible values are
::classname
::origin
::model
::model2
::spawnflags
::eflags
::svflags
::maxs
::mins
::speed
::closespeed
::target
::targetname
::message
::popup
::book
::team
::wait
::random
::count
::health
::light - ignored
::dmg
::angles
::angle
::duration
::rotate
::degrees
::time
::skin
::_color
::color
::stylestring
::shader
::key
::harc
::varc
::delay
::radius
::missionlevel
::start_size
::end_size
::shard
::spawnitem
::track
::scriptName
::shortname
::constages
::desstages
::partofstage
::override
::damageparent
::contents
::clipmask
::count2
::pos_trType
::pos_trDelta
::apos_trType
::apos_trDelta
::allowteams
*return value ''spawnval'' is the value associated with the ''key'' or nil if the function fails

'''Portability'''

Function is ETPro compatible.

=== G_SetSpawnVar ===
'''Description'''
Sets spawn value to an entity.

'''Syntax'''

et.G_SetSpawnVar( entnum, key, value )
*''entitynum'' is the target entity
*''key'' is the key for the value, the possible keys are the same as in G_GetSpawnVar
*''value'' is the new value for the ''key''

'''Portability'''

Function is ETPro compatible.

=== trap_LinkEntity ===
'''Description'''

Links an entity.

'''Syntax'''

et.trap_LinkEntity( entnum )
*''entnum'' is the entity number to link

'''Portability'''

Function is ETPro compatible.

=== trap_UnlinkEntity ===
'''Description'''

Unlinks an entity.

'''Syntax'''

et.trap_UnlinkEntity( entnum )
*''entnum'' is the entity number to unlink

'''Portability'''

Function is ETPro compatible.

=== gentity_get ===
'''Description'''

Returns a field value associated with an entity.

'''Syntax'''

variable = et.gentity_get( entnum, fieldname, arrayindex )
*''entnum'' is the number of the entity
*''fieldname'' is the name of the field to get, possible values are
::'''Field names for player entities only'''
::"inactivityTime"
::"inactivityWarning"
::"pers.connected" - this is the connection status of the client, possible values are
:::0 - disconnected
:::1 - connecting
:::2 - connected
::"pers.netname" - the name of the client, including color codes
::"pers.localClient" - 1 if the player is from localhost, 0 otherwise
::"pers.initialSpawn" - 1 if the player has not spawned yet, 0 otherwise
::"pers.enterTime" - the level time the player connected
::"pers.connectTime" - the level time the player connected
::"pers.teamState.state" - the state of the player. This value changes on every team change and entering to the server. But it does not change on deaths and revives. Possible values are
:::0 - beginning, spawn at base
:::1 - actively playing
::"pers.voteCount" - the number of failed votes the player has initiated
::"pers.teamVoteCount" - unused
::"pers.complaints" - the number of complaints the player has received
::"pers.complaintClient" - the client number the player who teamkilled, if the complaint is possible
::"pers.complaintEndTime" - the level time the option for complaint ends
::"pers.lastReinforceTime" - time of the previous respawn
::"pers.applicationClient" - the client number of the player who is applying to a fireteam. This value is stored only to the fireteam leader.
::"pers.applicationEndTime" - the level time when the fireteam application expires. This value is stored only to the fireteam leader.
::"pers.invitationClient" - the client number of the player who is inviting a player to the fireteam. This value is stored only to the invited player.
::"pers.invitationEndTime" - the level time when the invitation expires. This data is stored only to the invited player.
::"pers.propositionClient" - the client number of the player who is proposed to the fireteam. This value is stored only to the fireteam leader.
::"pers.propositionClient2" - the client number of the player who is proposing a player to the fireteam. This value is stored only to the fireteam leader.
::"pers.propositionEndTime" - the level time when the proposition ends
::"pers.autofireteamEndTime" - the level time when prompt for making fireteam private expires
::"pers.autofireteamCreateEndTime" - the level time when automatic prompt for creating fireteam expires
::"pers.autofireteamJoinEndTime" - the level time when automatic prompt for joining existing fireteam ends
::"pers.lastSpawnTime" - the level time when the player spawned fresh into the world
::"pers.ready" - 1 if player is ready during intermission, 0 otherwise
:: "ps.stats" - an array of 16 integers for different purposes, the most interesting fields are
::: player health at index 0
::: player sprint time at index 7, this is a read only and changing this does not affect the game in any way
::: player XP at index 8
::: player XP overflow at index 9
::"ps.persistant" - an array of 16 integers for different purposes
::"ps.ping" - the ping of the player. The g_truePing setting does not affect this.
::"ps.powerups" - an array of 16 integers for powerups. The indexes are as follows
:::0 - none
:::1 - invulnerable, level time when the player is vulnerable again
:::2 - unused
:::3 - unused
:::4 - breath, time left with air underwater
:::5 - nofatigue, time left before sprint time starts to reduce
:::6 - red flag, axis flag carried
:::7 - blue flag, allied flag carried
:::8 - disguised, 1 if disguised, 0 otherwise
:::9 - information of the covert op
:::10 - information of the covert op
:::11 - information of the covert op
:::12 - adrenaline, time left of adrenaline
:::13 - unused
:::14 - blackout, specs see only black screen
:::15 - multiview, unused
::"ps.origin" - the player position, this is an array of 3 floats
::"ps.ammo" - an array of 64 integers holding total ammo for each weapon separately
::"ps.ammoclip" - an array of 64 integers holding ammo in the clip for each weapon separately
::"sess.sessionTeam" - the team of the player. Possible values are
:::0 - not in any team
:::1 - axis
:::2 - allies
:::3 - spectators
::"sess.spectatorTime" - the time when the player joined spectator
::"sess.spectatorState" - the state of the player in the specator team. Possible values are
:::0 - not a spectator
:::1 - not following any players
:::2 - following a player
::"sess.spectatorClient" - the client number of the player this player is following
::"sess.playerType" - the class of the player. Possible values are
:::0 - soldier
:::1 - medic
:::2 - engineer
:::3 - fieldops
:::4 - covert ops
::"sess.playerWeapon" - the weapon of the player
::"sess.playerWeapon2" - the sidearm of the player
::"sess.spawnObjectiveIndex" - the player spawn
::"sess.latchPlayerType" - the class of the player after next spawn
::"sess.latchPlayerWeapon" - the weapon of the player after next spawn
::"sess.latchPlayerWeapon2" - the sidearm of the player after next spawn
::"sess.damage_given" - the amount of damage to other team's players this player has inflicted
::"sess.damage_received" - the amount of damage this player has received from the other team
::"sess.deaths" - the amount of deaths
::"sess.game_points" - score
::"sess.kills" - the amount of kills this player has made
::"sess.medals" - an array of 7 integers for medals of each skill
::"sess.muted" and "sess.auto_unmute_time" - both of these point to the same data. This is the seconds left until unmute.
::"sess.rank" - the rank of the player
::"sess.referee" - the players referee/rcon status. Possible values are
:::0 - none
:::1 - referee
:::2 - rcon
::"sess.rounds" - the number of round. This has meaning only when playing stopwatch mode.
::"sess.skill" - an array of 7 integers for the level in each skill. Do note that this doesn't have an effect on the player abilities. Different indexes are
:::0 - battle sense
:::1 - explosives and construction (engineer)
:::2 - first aid (medic)
:::3 - signals (field ops)
:::4 - light weapons
:::5 - heavy weapons (soldier)
:::6 - military intelligence and scoped weapons (covert ops)
::"sess.spec_invite" - the which the player is invited to spectate
::"sess.spec_team" - the team the spectator is allowed to follow
::"sess.suicides" - the amount of suicides of the player. This does not limit to /kill.
::"sess.team_kills" - the amount of team kills made by this player
::"sess.team_damage_given" - the amount of damage to the own team made by this player
::"sess.team_damage_received" - the amount of damage this player has received from his/hers own team.
::"sess.aWeaponStats" - weapon statistics of the player. This is read only.
::"client.inactivityTime" - this is a ETPro compatibility alias for the "inactivityTime" field.
::"client.inactivityWarning" - this is a ETPro compatibility alias for the "inactivityWarning" field.
::"origin" - this is an alias for the "ps.origin" field
::"sess.team_damage" - this is an alias for the "sess.team_damage_given" field
::"sess.team_received" - this is an alias for the "sess.team_damage_received" field
::"sess.guid" - this is the silEnT GUID of the player. This has been validated by the mod. Validation in this context does not mean it can not have been spoofed.
::"sess.ip" - this is the IP address of the player
::"sess.uci" - this is the country flag number of the player
::"sess.ignoreClients" - this is a bitfield of ignored clients
::"sess.skillpoints" - an array of 7 floats for skill points in each skill
::"sess.kstreak" - the killing spree
::"sess.dstreak" - the death spree
::"sess.rstreak" - the revive spree
::"sess.shoutcaster" - 1 if the player is shoutcaster, 0 otherwise
::"sess.rating" - the player win probability rating
::"sess.rating_variance" - the player win probability variance
::"sess.overall_killrating" - the player kill rating
::"sess.overall_killvariance" - the player kill rating variance
::"pers.lastkilled_client" - the client number of the last kill
::"pers.lastrevive_client" - the client number of the player who revived this player last
::"pers.lastkiller_client" - the client number of the player who killed this player last
::"pers.lastammo_client" - the client number of the player who gave ammo to this player last
::"pers.lasthealth_client" - the client number of the player who gave health to this player last
::'''Field names for all entities'''
::never ending list of fields continued later
*''arrayindex'' is the index in an array if the entity field is an array, indexes start from 0

'''Portability'''

Function is ETPro compatible.

=== gentity_set ===
'''Description'''

Sets a value in an entity. See gentity_get for possible values.

'''Syntax'''

et.gentity_set( entnum, fieldname, arrayindex, value )
*''entnum'' is the entity number that is manipulated
*''fieldname'' is the name of the field to manipulate
*''arrayindex'' is either the value that is set or an array index if the field is an array
*''value'' is the new value if arrayindex is used as an array index

'''Portability'''

Function is ETPro compatible.

=== G_AddEvent ===
'''Description'''

Adds an event to the entity event sequence.

'''Syntax'''

et.G_AddEvent( ent, event, eventparm )
*''ent'' is the entity which event sequnce is handled
*''event'' is the event to add
*''eventparm'' is optional parameter for the event

'''Portability'''

Function is ETPro compatible.

== Shrubbot ==
=== G_shrubbot_permission ===
'''Description'''

Tells if the given player has the given shrubbot flag set.

'''Syntax'''

permission = et.G_shrubbot_permission( ent, flag )
*''ent'' is the slot number of the player whos permission is checked
*''flag'' is the flag character that is checked
*return value ''permission'' is 1 if the player has the flag set, 0 otherwise

'''Portability'''

Function is derived from the ETPub Lua API.

=== G_shrubbot_level ===
'''Description'''

Returns the shrubbot level of the player.

'''Syntax'''

level = et.G_shrubbot_level( ent )
*''ent'' is the slot number of the player whos permission is checked
*return value ''level'' is the shrubbot level of the player.

'''Portability'''

Function was derived from the ETPub Lua API.

== Time ==
=== trap_Milliseconds ===
'''Description'''

Returns level time in milliseconds.

'''Syntax'''

milliseconds = et.trap_Milliseconds()

'''Portability'''

'''Note'''

= Callbacks =

Callbacks are functions that are called by the qagame automatically, if function implementations are present in the Lua scripts. Every Lua script needs to implement at least one callback or it will not be run at all.

=== et_InitGame ===
'''Description'''

Called when the server game initializes. Called once after every level change and after warmup.

'''Syntax'''

et_InitGame( levelTime, randomSeed, restart )
*''levelTime'' is the current level time in milliseconds
*''randomSeed'' is a number that can be used to seed random number generators
*''restart'' tells if the function is called due to a map restart

'''Portability'''

Callback is ETPro compatible.

=== et_ShutdownGame ===
'''Description'''

Called when the server game shuts down.

'''Syntax'''

et_ShutdownGame( restart )
*''restart'' indicates if the server is doing map restart

'''Portability'''

Callback is ETPro compatible.

=== et_RunFrame ===
'''Description'''

Called at the end of each server frame.

'''Syntax'''

et_RunFrame( levelTime )
*''levelTime'' is the current level time in milliseconds

'''Portability'''

Callback is ETPro compatible.

=== et_ClientConnect ===
'''Description'''

Called for each connecting client. After the mod has performed most of its own actions. Connecting player can still be refused by this function.

'''Syntax'''

rejectreason = et_ClientConnect( clientNum, firstTime, isBot )
*''clientNum'' is the number of the client entity. Client number range is [0,63].
*''firstTime'' indicates if the player is connecting the first time or as a result of a map change or a map restart.
*''isBot'' indicates if the player is a server bot. Omni-bots do have this set.
*return value ''rejectreason'' is a string describing why the player is refused. If nil is returned, the player is allowed to connect.

'''Portability'''

Callback is ETPro compatible.

=== et_ClientDisconnect ===
'''Description'''

Called everytime a player is disconnected before any actions by the mod to the player data.

'''Syntax'''

et_ClientDisconnect( clientNum )
*''clientNum'' is the entity number of the player.

'''Portability'''

Function is ETPro compatible.

=== et_ClientBegin ===
'''Description'''

Called when the player is ready to be put into the world. After all mod actions. Function is called only once during the map.

'''Syntax'''

et_ClientBegin( clientNum )
*''clientNum'' is the entity number of the player

'''Portability'''

Function is ETPro compatible.

=== et_ClientUserinfoChanged ===
'''Description'''

Called if the player userinfo has changed.

'''Syntax'''

et_ClientUserinfoChanged( clientNum )
*''clientNum'' the entity number of the player

'''Portability'''

Callback is ETPro compatible.

=== et_ClientSpawn ===
'''Description'''

Called when a player is spawned.

'''Syntax'''

et_ClientSpawn( clientNum, revived, teamChange, restoreHealth )
*''clientNum'' is the entity number of the spawned player
*''revive'' is 1 if the player was revived, 0 otherwise
*''teamChange'' is 1 if the player changed team, 0 otherwise
*''restoreHealth'' is 1 if the player health bar is restored to full, 0 otherwise

'''Portability'''

Callback is ETPro compatible.

=== et_ClientCommand ===
'''Description'''

Called when a command is received from a player.

'''Syntax'''

intercepted = et_ClientCommand( clientNum, command )
*''clientNum'' is the entity number of the player
*''command'' is the command as a string
*return value ''intercepted'' must be set to 1 if the command execution is stopped at the Lua script. With value 0 the command is then processed in the server mod binary.

'''Portability'''

Callback is ETPro compatible.

=== et_ConsoleCommand ===
'''Description'''

Called when a command is entered to the server console.

'''Syntax'''

intercepted = et_ConsoleCommand( command )
*''command'' is the command name as a string
*return value ''intercepted'' is set to 1 if the command execution is stopped in the Lua script, 0 if the command is then executed in the server mod binary

'''Portability'''

Callback is ETPro compatible.

=== et_UpgradeSkill ===
'''Description'''

Called when a player receives a skill upgrade.

'''Syntax'''

result = et_UpgradeSkill( cno, skill )
*''cno'' is the entity number of the player
*''skill'' is the skill type that is upgraded
*return value ''result'' will abort the skill upgrade if set to -1, any other value will allow the skill upgrade progress through

'''Portability'''

Callback is in ETPro compatible.

=== et_SetPlayerSkill ===
'''Description'''

Called when a player skill level is set.

'''Syntax'''

intercepted = et_SetPlayerSkill( cno, skill )
*''cno'' is the entity number of the player
*''skill'' is the skil type of the player
*return value ''intercepted'' is set to -1 if the skill set is aborted, with any other value the set is allowed

'''Portability'''

Callback is ETPro compatible.

=== et_Print ===
'''Description'''

Called when server is printing to the console.

'''Syntax'''

et_Print( text )
*''text'' is the full printed text

'''Portability'''

Function is ETPro compatible. Differences may exist between ETPro, ETPub and silEnT.

=== et_Obituary ===
'''Description'''

Called when a player is killed. If a string is returned from the callback, it will replace the obituary message. The custom obituary can be printed to either chat or as a popup. This behaviour is defined with g_logOptions flag 1.

'''Syntax'''

(customObit) = et_Obituary( victim, killer, meansOfDeath )
*''victim'' is the entity number of the killed player
*''killer'' is the entity number of the killer, this can be also 1022 which means that the world was the killer
*''meansOfDeath'' is the means of death number
*return value ''customObit'' can be set to create customary obituary messages. If a custom obituary message is returned, only the custom obituary is printed.

'''Portability'''

Callback is ETPro compatible.

=== et_CvarValue ===

'''Description'''

Called when a client cvar value is ready to be passed to Lua scripts.

'''Syntax'''

et_CvarValue( clientNum, cvar, value )
*''clientNum'' is the slot number of the player
*''cvar'' is the name of the cvar
*''value'' is the value of the cvar

'''Portability'''

Callback was added in silEnT 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

=== et_ClientBinary ===

'''Description'''

Called when a player connects with an unrecognized client executable. Also called if the player connects with a known cheat binary.

'''Syntax'''

et_ClientBinary( clientNum, checksum )
*''clientNum'' is the slot number of the player
*''checksum'' is the 32 character MD5 checksum of the client executable (ET.exe)

'''Portability'''

Callback was added in silEnT 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

=== et_IntermissionStarts ===

'''Description'''

Called one server frame before the game enters intermission.

'''Syntax'''

et_IntermissionStarts( round )
*''round'' is value of the g_currentRound cvar

'''Portability'''

Callback was added in silEnT 0.8.0 and it is not present in ETPro or ETPub Lua APIs.

= References =

* Document was constructed using information at http://wolfwiki.anime.net/index.php/ETPro:Lua_Mod_API as well as reading the mod source.

* Official Lua http://www.lua.org/

Silent Lua

2015-08-30T10:31:20Z

Silencerpl: lua version changes description

silEnT servers support Lua 5.1.4 scripts up till version 0.8.2.
Since version 0.9.0 silEnT mod supports Lua 5.3.1 compiled to be compatible with Lua version 5.2.
Starting from version 0.5.1 the Lua interpreter is inbuilt into the server side mod. Before the vesion 0.5.1, the Lua was installed as an external module. A separate build of the silEnT mod is supplied within the download to admins who still want to use separate Lua library. silEnT's Lua API is aiming to be fully compatible to ETPro's Lua API. The origin of the silEnT Lua API is the Lua module in ETPub version 0.9.1.

= Cvars =
== lua_modules ==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules ==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL). If this string is empty, all loaded modules are allowed.

'''Type:''' string

'''Default:''' ""

= Commands =
== lua_status ==

Shows information about the scripts currently loaded by the Lua API server engine. This command works also from the client so that players can check what modules are currently loaded by the server.

= Interface Function Reference =
== Modules ==

=== RegisterModname ===

'''Description'''

Registers a descriptive name for this Lua module.

'''Syntax'''

et.RegisterModname( modname )

*''modname'' is the name to register the Lua module

'''Portability'''

Function is ETPro compatible.

=== FindSelf ===

'''Description'''

Returns a number indicating the VM slot the current mod is loaded into.

'''Syntax'''

vmnumber = et.FindSelf()

'''Portability'''

Function is ETPro compatible.

=== FindMod ===

'''Description'''

Returns the registered module name and the SHA-1 signature of the module loaded in the VM. Do note that each loaded Lua module will have it's own VM.

'''Syntax'''

modname, signature = et.FindMod( vmnumber )

* ''vmnumber'' is the number of the VM in where the Lua module is loaded

* return value (''modname'', ''signature'') is the registered module's name and the SHA-1 signature. Returns (nil, nil) if there is no module loaded into the given VM number

'''Portability'''

Function is ETPro compatible.

=== IPCSend ===

'''Description'''

Inter Process Communication. This function enables communication between different loaded Lua modules.

'''Syntax'''

success = et.IPCSend( vmnumber, message )

* ''vmnumber'' is the number of the loaded module message is sent

* ''message'' is the string to send

* return value ''success'' is 1 if success and 0 if function fails

'''Portability'''

Function is ETPro compatible.

== Printing ==
=== G_Print ===

'''Description'''

Prints text to the server console.

'''Syntax'''

et.G_Print( text )

* ''text'' is the printed string

'''Portability'''

Function is ETPro compatible.

=== G_LogPrint ===

'''Description'''

Prints text to the server console and also to the log.

'''Syntax'''

et.G_LogPrint( text )

* ''text'' is the printed and logged string

'''Portability'''

Function is ETPro compatible.

== Argument Handling ==
=== ConcatArgs ===

''' Description'''

Function concatenates server command arguments into one string.

'''Syntax'''

args = et.ConcatArgs( index )

* ''index'' is the index of the first argument in the concatenated string. First command argument index in general is 1.

* return value ''args'' is the concatenated string

'''Portability'''

Function is ETPro compatible.

=== trap_Argc ===

'''Description'''

Function returns the number of the arguments in the server command.

'''Syntax'''

argc = et.trap_Argc()

* return value ''argc'' is the count of arguments. For example for the command "/m gao message", the function would return 2.

'''Portability'''

Function is ETPro compatible.

=== trap_Argv ===

'''Description'''

Function returns argument in the given index.

'''Syntax'''

arg = et.trap_Argv( index )

* ''index'' is the argument index to return.

* return value ''arg'' is the argument

'''Portability'''

Function is ETPro compatible.

== Cvars ==
=== trap_Cvar_Get ===

'''Description'''

Returns the value of the given cvar.

'''Syntax'''

cvarvalue= et.trap_Cvar_Get( cvar )

* ''cvar'' is the name of the cvar

* return value ''cvarvalue'' is a string containing the value. If there is no cvar with the given name, the returning string has zero length.

'''Portability'''

Function is ETPro compatible.

=== trap_Cvar_Set ===

'''Description'''

Sets value to a cvar.

'''Syntax'''

et.trap_Cvar_Set( name, value )

* ''name'' is the name of the cvar to set

* ''value'' is the new value for the cvar

'''Portability'''

Function is ETPro compatible.

== Configstrings ==
=== trap_GetConfigstring ===

'''Description'''

Returns contents of the configstring at index.

'''Syntax'''

configstringvalue = et.trap_GetConfigstring( index )

* ''index'' is the index of the configstring

* return value ''configstring'' contains the full config string

'''Portability'''

Function is ETPro compatible.

=== trap_SetConfigstring ===

'''Description'''

Function sets the full configstring.

'''Syntax'''

et.trap_SetConfigstring( index, configstringvalue )

* ''index'' is the configstring index

* ''configstringvalue'' is the full configstring to set

'''Portability'''

Function is ETPro compatible.

== Server Console and Client Handling ==
=== trap_SendConsoleCommand ===

'''Description'''

Sends command to the server console.

'''Syntax'''

et.trap_SendConsoleCommand( when, command )

* ''when'' tells when the command is executed. Possible values are
::et.EXEC_NOW - executes instantly
::et.EXEC_INSERT - inserts at the current position but doesn't run yet
::et.EXEC_APPEND - appends at the end of the command buffer
* ''command'' is the full command to execute

'''Portability'''

Function is ETPro compatible.

=== trap_DropClient ===

'''Description'''

Disconnects client from the server.

'''Syntax'''

et.trap_DropClient( clientnum, reason, ban_time )

* ''clientnum'' is the slot number of the client to disconnect
* ''reason'' is the descriptive reason for the kick. This is also displayed to the client.
* ''ban_time'' is optional length of the kick. If this is not set, the g_defaultBanTime is used.

'''Portability'''

Function is ETPro compatible.

=== trap_SendServerCommand ===

'''Description'''

Function sends reliable server command to a client. I.e. the command is acknowledged by the client to ensure it has received it.

'''Syntax'''

et.trap_SendServerCommand( clientnum, command )

* ''clientnum'' is the slot number of the client to send the command. If the number is -1, the command is sent to all connected clients.
* ''command'' is the full command string to send

'''Portability'''

Function is ETPro compatible.

=== ClientNumberFromString ===

'''Description'''

Function finds one matching player name based on the given string.

'''Syntax'''

clientnum = et.ClientNumberFromString( string )

* ''string'' is a pattern to match against client names
* return value ''clientnum'' is the client slot number if one match is found, otherwise -1 is returned

'''Portability'''

ETPro does not implement this function. Function is derived to silEnT from ETPub implementation.

=== G_Say ===

'''Description'''

Writes to chat on behalf of a client.

'''Syntax'''

et.G_Say( clientNum, mode, text )

* ''clientNum'' is the slot number of the client on behalf to write chat
* ''mode'' is the type of chat to write. Possible values are
::et.SAY_ALL - writes to the global chat
::et.SAY_TEAM - writes to the team chat of the client
::et.SAY_BUDDY - writes to the fireteam chat of the client
::et.SAY_TEAMNL - writes to the team chat of the client without position
* ''text'' is the chat message to write

'''Portability'''

Function is ETPro compatible.

=== ClientUserinfoChanged ===

'''Description'''

Loads the new userinfo string of the client and sets the client settings to match it.

'''Syntax'''

et.ClientUserinfoChanged( clientNum )

*''clientNum '' is the slot number of the client who's userinfo is loaded

'''Portability'''

Function is ETPro compatible.

=== trap_GetUserinfo ===

'''Description'''

Returns the userinfo string of a client.

'''Syntax'''

userinfo = et.trap_GetUserinfo( clientnum )

* ''clientnum'' is the slot number of the client who's userinfo is returned
* return value ''userinfo'' is the full userinfo string of that client

'''Portability'''

Function is ETPro compatible.

=== trap_SetUserinfo ===

'''Description'''

Sets the userinfo string of the client to the passed userinfo. To make the changes to take effect in the game, ClientUserinfoChanged must be called after this function.

'''Syntax'''

et.trap_SetUserinfo( clientnum, userinfo )

* ''clientnum'' is the slot number of the client who's userinfo is changed
* ''userinfo'' is the full new userinfo of the client

'''Portability'''

Function is ETPro compatible.

=== G_Damage ===

'''Description'''

Damages target entity on behalf of the attacker entity.

'''Syntax'''

et.G_Damage( target, inflictor, attacker, damage, dflags, mod )

*''target'' is the entity number to damage, value must be 0 or more
*''inflictor'' is the entity number that does the damage, value must be 0 or more
*''attacker'' is the entity number that causes the inflictor entity to cause damage to target, value must be 0 or more
*''damage'' is the amount of damage to inflict
*''dflags'' is the type of damage to inflict, possible values are
::DAMAGE_RADIUS - damage was indirect (from a nearby explosion)
::DAMAGE_NO_ARMOR - armor does not protect from this damage
::DAMAGE_NO_KNOCKBACK - do not affect velocity, just view angles
::DAMAGE_NO_PROTECTION - kills godmode, armor, everything
*''mod'' is the means of death, possible values are:
::0 - MOD_UNKNOWN
::1 - MOD_MACHINEGUN
::2 - MOD_BROWNING
::3 - MOD_MG42
::4 - MOD_GRENADE
::5 - MOD_ROCKET
::6 - MOD_KNIFE
::7 - MOD_LUGER
::8 - MOD_COLT
::9 - MOD_MP40
::10 - MOD_THOMPSON
::11 - MOD_STEN
::12 - MOD_GARAND
::13 - MOD_SNOOPERSCOPE
::14 - MOD_SILENCER
::15 - MOD_FG42
::16 - MOD_FG42SCOPE
::17 - MOD_PANZERFAUST
::18 - MOD_GRENADE_LAUNCHER
::19 - MOD_FLAMETHROWER
::20 - MOD_GRENADE_PINEAPPLE
::21 - MOD_CROSS
::22 - MOD_MAPMORTAR
::23 - MOD_MAPMORTAR_SPLASH
::24 - MOD_KICKED
::25 - MOD_GRABBER
::26 - MOD_DYNAMITE
::27 - MOD_AIRSTRIKE
::28 - MOD_SYRINGE
::29 - MOD_AMMO
::30 - MOD_ARTY
::31 - MOD_WATER
::32 - MOD_SLIME
::33 - MOD_LAVA
::34 - MOD_CRUSH
::35 - MOD_TELEFRAG
::36 - MOD_FALLING
::37 - MOD_SUICIDE
::38 - MOD_TARGET_LASER
::39 - MOD_TRIGGER_HURT
::40 - MOD_EXPLOSIVE
::41 - MOD_CARBINE
::42 - MOD_KAR98
::43 - MOD_GPG40
::44 - MOD_M7
::45 - MOD_LANDMINE
::46 - MOD_SATCHEL
::47 - MOD_TRIPMINE
::48 - MOD_SMOKEBOMB
::49 - MOD_MOBILE_MG42
::50 - MOD_SILENCED_COLT
::51 - MOD_GARAND_SCOPE
::52 - MOD_CRUSH_CONSTRUCTION
::53 - MOD_CRUSH_CONSTRUCTIONDEATH
::54 - MOD_CRUSH_CONSTRUCTIONDEATH_NOATTACKER
::55 - MOD_K43
::56 - MOD_K43_SCOPE
::57 - MOD_MORTAR
::58 - MOD_AKIMBO_COLT
::59 - MOD_AKIMBO_LUGER
::60 - MOD_AKIMBO_SILENCEDCOLT
::61 - MOD_AKIMBO_SILENCEDLUGER
::62 - MOD_SMOKEGRENADE
::63 - MOD_SWAP_PLACES
::64 - MOD_SWITCHTEAM
::65 - MOD_GOOMBA
::66 - MOD_POISON
::67 - MOD_FEAR
::68 - MOD_THROWN_KNIFE
::69 - MOD_REFLECTED_FF
::70 - MOD_PPSH
::71 - MOD_SHOVE

'''Portability'''

Function is implemented in ETPro but some of the mod values may differ.

=== ClientIsFlooding ===

'''Description'''

Tells if ''g_floodthreshold'' has been exceeded for the player. In other words, the client is sending more than a ''g_floodthreshold'' amount of messages per second to the server. Admins with shrubbot flag 2 are excluded.

'''Syntax'''

flooding = et.ClientIsFlooding( clientnum )

*''clientnum'' is the slotnumber of the client that is checked
*return value ''flooding'' is 1 if the clientis flooding, 0 otherwise

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_AddSkillPoints ===
'''Description'''

Adds points to the client's skill.

'''Syntax'''

et.G_AddSkillPoints( clientNum, skill, points )

*''clientNum'' is the slot number of the client
*''skill'' identifies the skill that the points are added, possible values are
::0 - SK_BATTLE_SENSE
::1 - SK_EXPLOSIVES_AND_CONSTRUCTION
::2 - SK_FIRST_AID
::3 - SK_SIGNALS
::4 - SK_LIGHT_WEAPONS
::5 - SK_HEAVY_WEAPONS
::6 - SK_MILITARY_INTELLIGENCE_AND_SCOPED_WEAPONS
::7 - SK_NUM_SKILLS
*''points'' is the amount of points to add

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_LoseSkillPoints ===
'''Description'''

Causes player to lose skill points.

'''Syntax'''

et.G_LoseSkillPoints( clientNum, skill, points )
*''clientNum'' is the slot number of the client
*''skill'' is the skill from where the points are taken, possible values are
::0 - SK_BATTLE_SENSE
::1 - SK_EXPLOSIVES_AND_CONSTRUCTION
::2 - SK_FIRST_AID
::3 - SK_SIGNALS
::4 - SK_LIGHT_WEAPONS
::5 - SK_HEAVY_WEAPONS
::6 - SK_MILITARY_INTELLIGENCE_AND_SCOPED_WEAPONS
::7 - SK_NUM_SKILLS
*''points'' is the amount of points to remove

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub's Lua module.

=== G_QueryClientCvar ===

Lua scripts can query cvar values from connected players. The values are returned in a different callback function.

'''Syntax'''

et.G_QueryClientCvar( clientNum, cvarName)
*''clientNum'' is the slot number of the player
*''cvarName'' is the name of the cvar that is requested

'''Portability'''

Function was added in silEnT version 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

== String Utility Functions ==
=== Info_RemoveKey ===
'''Description'''

Removes a key and it's associated value from an infostring.

'''Syntax'''

infostring = et.Info_RemoveKey( infostring, key )
*''infostring'' as a passed parameter is the infostring from which to remove the key
*''key'' is the key to remove
*return value ''infostring'' is the infostring without the key

'''Portability'''

Function is ETPro compatible.

=== Info_SetValueForKey ===
'''Description'''

Sets a value in an infostring.

'''Syntax'''

infostring = et.Info_SetValueForKey( infostring, key, value )
*''infostring'' as passed parameter is the original infostring
*''key'' is the key to set
*''value'' is the value to set to the key
*return value ''infostring'' is the modified infostring

'''Portability'''

Function is ETPro compatible.

=== Info_ValueForKey ===
'''Description'''

Returns a value from an infostring.

'''Syntax'''

keyvalue = et.Info_ValueForKey( infostring, key )
*''infostring'' is the infostring from where to search the key
*''key'' is the key which value is returned
*return value ''keyvalue'' is the value from the searched key

'''Portability'''

Function is ETPro compatible.

=== Q_CleanStr ===
'''Description'''

Removes all Enemy Territory color codes and special characters from a string. The returning string will be ASCII characters of the range [32,126] in decimal numbers.

'''Syntax'''

cleanstring = et.Q_CleanStr( string )
*''string'' is the string to clean
*''cleanstring'' is the cleaned string

'''Portability'''

Function is ETPro compatible.

== Filesystem ==
=== trap_FS_FOpenFile ===
'''Description'''

Opens a file in the local file system.

'''Syntax'''

fd, len = et.trap_FS_FOpenFile( filename, mode )
*''filename'' is the name of the file to open. The file is opened under the current working directory and absolute paths will not work.
*''mode'' is the mode the file is opened, possible values are
::et.FS_READ - opens the file for reading only
::et.FS_WRITE - opens the file for writing, truncates the old file if a file with name ''filename'' already exists
::et.FS_APPEND - opens the file for writing at the end of file, the old file is not erased if it already exists
::et.FS_APPEND_SYNC - like et.FS_APPEND but the file buffer is flushed to the file on hard drive directly after every write operation
*return value (''fd'', ''len'') is the descriptor (or handle in Windows terminology) of the file and the length of the file

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Read ===
'''Description'''

Reads from an open file.

'''Syntax'''

filedata = et.trap_FS_Read( fd, count )
*''fd'' is the descriptor of the file to read
*''count'' is the amount of bytes to read
*return value ''filedata'' will have the read bytes

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Write ===
'''Description'''

Writes at the end of an open file.

'''Syntax'''

count= et.trap_FS_Write( filedata, count, fd )
*''filedata'' is a block of bytes to write
*''count'' is the size of the block to write
*''fd'' is the descriptor of the file
*return value ''count'' is the amount of bytes written to the file

'''Portability'''

Function is ETPro compatible.

=== trap_FS_Rename ===
'''Description'''

Renames a file in the loal file system.

'''Syntax'''

et.trap_FS_Rename( oldname, newname )
*''oldname'' is the name of the file to rename
*''newname'' is the name the old file name is changed

'''Portability'''

Function is ETPro compatible.

=== trap_FS_FCloseFile ===
'''Description'''

Closes an opened file.

'''Syntax'''

et.trap_FS_FCloseFile( fd )
*''fd'' is the descriptor of the opened file

'''Portability'''

Function is ETPro compatible.

== Sounds and Models ==
=== G_SoundIndex ===
'''Description'''

Returns the configstring index that includes the searched sound name.

'''Syntax'''

soundindex = et.G_SoundIndex( filename )

*''filename'' is the sound file name that is searched
*return value ''soundindex'' is the config string index that includes the ''filename'' or 0 if the name was not found

'''Portability'''

Function is ETPro compatible.

=== G_ModelIndex ===
'''Description'''

Returns an index to the configstring that include the searched model.

'''Syntax'''

modelindex = et.G_ModelIndex( filename )
*''filename'' is the name that is searched through the config strings
*return value ''modelindex'' is the configstring number that included the ''filename'' or 0 if not found

'''Portability'''

Function is ETPro compatible.

=== G_globalSound ===
'''Description'''

Plays a sound to all connected clients.

'''Syntax'''

et.G_globalSound( sound )
*''sound'' is the name of the sound to play

'''Portability'''

Function is ETPro compatible.

=== G_Sound ===
'''Description'''

Plays a sound originating from position of an entity.

'''Syntax'''

et.G_Sound( entnum, soundindex )
*''entnum'' is the number of the entity which position is used as the sound origin
*''soundindex'' is the index of the sound that is played

'''Portability'''

Function is ETPro compatible.

=== G_ClientSound ===
'''Description'''

Plays a sound originating from a client entity to the team members of that client.

'''Syntax'''

et.G_ClientSound( clientnum, soundindex )
*''clientnum'' is the slot number of the connected player
*''soundindex'' is the index to the sound to play

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub Lua implementation.

== Entities ==
=== G_Spawn ===
'''Description'''

Spawns a new entity.

'''Syntax'''

entnum = et.G_Spawn()
*return value ''entnum'' is the number of the new entity

'''Portability'''

Function is ETPro compatible.

=== G_TempEntity ===
'''Description'''

Spawns a new temp entity to a location.

'''Syntax'''

entnum = et.G_TempEntity( origin, event )
*''origin'' is the location the temp entity is placed
*''event'' is the event type of the entity, this is a number from the range [1, 118]
*return value ''entnum'' is the number of the new entity

'''Portability'''

Function is ETPro compatible, but some event types do differ from mod to mod.

=== G_FreeEntity ===
'''Description'''

Deletes an entity.

'''Syntax'''

et.G_FreeEntity( entnum )
*''entnum'' is the number of the entity to remove

'''Portbility'''

Function is ETPro compatible.

=== G_EntitiesFree ===
'''Description'''
Calculates all free entities. Free client entities (slots) are not counted.

'''Syntax'''

count = et.G_EntitiesFree()
*return value ''count'' is the number of free entities

'''Portability'''

Function is not implemented in the ETPro Lua API. Function was derived to silEnT from the ETPub Lua implementation, where it is broken.

=== G_GetSpawnVar ===
'''Description'''

Return a value of a spawnvar.

'''Syntax'''

spawnval = et.G_GetSpawnVar( entnum, key )
*''entnum'' is the entity number of the target
*''key'' is the key for the value to return, possible values are
::classname
::origin
::model
::model2
::spawnflags
::eflags
::svflags
::maxs
::mins
::speed
::closespeed
::target
::targetname
::message
::popup
::book
::team
::wait
::random
::count
::health
::light - ignored
::dmg
::angles
::angle
::duration
::rotate
::degrees
::time
::skin
::_color
::color
::stylestring
::shader
::key
::harc
::varc
::delay
::radius
::missionlevel
::start_size
::end_size
::shard
::spawnitem
::track
::scriptName
::shortname
::constages
::desstages
::partofstage
::override
::damageparent
::contents
::clipmask
::count2
::pos_trType
::pos_trDelta
::apos_trType
::apos_trDelta
::allowteams
*return value ''spawnval'' is the value associated with the ''key'' or nil if the function fails

'''Portability'''

Function is ETPro compatible.

=== G_SetSpawnVar ===
'''Description'''
Sets spawn value to an entity.

'''Syntax'''

et.G_SetSpawnVar( entnum, key, value )
*''entitynum'' is the target entity
*''key'' is the key for the value, the possible keys are the same as in G_GetSpawnVar
*''value'' is the new value for the ''key''

'''Portability'''

Function is ETPro compatible.

=== trap_LinkEntity ===
'''Description'''

Links an entity.

'''Syntax'''

et.trap_LinkEntity( entnum )
*''entnum'' is the entity number to link

'''Portability'''

Function is ETPro compatible.

=== trap_UnlinkEntity ===
'''Description'''

Unlinks an entity.

'''Syntax'''

et.trap_UnlinkEntity( entnum )
*''entnum'' is the entity number to unlink

'''Portability'''

Function is ETPro compatible.

=== gentity_get ===
'''Description'''

Returns a field value associated with an entity.

'''Syntax'''

variable = et.gentity_get( entnum, fieldname, arrayindex )
*''entnum'' is the number of the entity
*''fieldname'' is the name of the field to get, possible values are
::'''Field names for player entities only'''
::"inactivityTime"
::"inactivityWarning"
::"pers.connected" - this is the connection status of the client, possible values are
:::0 - disconnected
:::1 - connecting
:::2 - connected
::"pers.netname" - the name of the client, including color codes
::"pers.localClient" - 1 if the player is from localhost, 0 otherwise
::"pers.initialSpawn" - 1 if the player has not spawned yet, 0 otherwise
::"pers.enterTime" - the level time the player connected
::"pers.connectTime" - the level time the player connected
::"pers.teamState.state" - the state of the player. This value changes on every team change and entering to the server. But it does not change on deaths and revives. Possible values are
:::0 - beginning, spawn at base
:::1 - actively playing
::"pers.voteCount" - the number of failed votes the player has initiated
::"pers.teamVoteCount" - unused
::"pers.complaints" - the number of complaints the player has received
::"pers.complaintClient" - the client number the player who teamkilled, if the complaint is possible
::"pers.complaintEndTime" - the level time the option for complaint ends
::"pers.lastReinforceTime" - time of the previous respawn
::"pers.applicationClient" - the client number of the player who is applying to a fireteam. This value is stored only to the fireteam leader.
::"pers.applicationEndTime" - the level time when the fireteam application expires. This value is stored only to the fireteam leader.
::"pers.invitationClient" - the client number of the player who is inviting a player to the fireteam. This value is stored only to the invited player.
::"pers.invitationEndTime" - the level time when the invitation expires. This data is stored only to the invited player.
::"pers.propositionClient" - the client number of the player who is proposed to the fireteam. This value is stored only to the fireteam leader.
::"pers.propositionClient2" - the client number of the player who is proposing a player to the fireteam. This value is stored only to the fireteam leader.
::"pers.propositionEndTime" - the level time when the proposition ends
::"pers.autofireteamEndTime" - the level time when prompt for making fireteam private expires
::"pers.autofireteamCreateEndTime" - the level time when automatic prompt for creating fireteam expires
::"pers.autofireteamJoinEndTime" - the level time when automatic prompt for joining existing fireteam ends
::"pers.lastSpawnTime" - the level time when the player spawned fresh into the world
::"pers.ready" - 1 if player is ready during intermission, 0 otherwise
:: "ps.stats" - an array of 16 integers for different purposes, the most interesting fields are
::: player health at index 0
::: player sprint time at index 7, this is a read only and changing this does not affect the game in any way
::: player XP at index 8
::: player XP overflow at index 9
::"ps.persistant" - an array of 16 integers for different purposes
::"ps.ping" - the ping of the player. The g_truePing setting does not affect this.
::"ps.powerups" - an array of 16 integers for powerups. The indexes are as follows
:::0 - none
:::1 - invulnerable, level time when the player is vulnerable again
:::2 - unused
:::3 - unused
:::4 - breath, time left with air underwater
:::5 - nofatigue, time left before sprint time starts to reduce
:::6 - red flag, axis flag carried
:::7 - blue flag, allied flag carried
:::8 - disguised, 1 if disguised, 0 otherwise
:::9 - information of the covert op
:::10 - information of the covert op
:::11 - information of the covert op
:::12 - adrenaline, time left of adrenaline
:::13 - unused
:::14 - blackout, specs see only black screen
:::15 - multiview, unused
::"ps.origin" - the player position, this is an array of 3 floats
::"ps.ammo" - an array of 64 integers holding total ammo for each weapon separately
::"ps.ammoclip" - an array of 64 integers holding ammo in the clip for each weapon separately
::"sess.sessionTeam" - the team of the player. Possible values are
:::0 - not in any team
:::1 - axis
:::2 - allies
:::3 - spectators
::"sess.spectatorTime" - the time when the player joined spectator
::"sess.spectatorState" - the state of the player in the specator team. Possible values are
:::0 - not a spectator
:::1 - not following any players
:::2 - following a player
::"sess.spectatorClient" - the client number of the player this player is following
::"sess.playerType" - the class of the player. Possible values are
:::0 - soldier
:::1 - medic
:::2 - engineer
:::3 - fieldops
:::4 - covert ops
::"sess.playerWeapon" - the weapon of the player
::"sess.playerWeapon2" - the sidearm of the player
::"sess.spawnObjectiveIndex" - the player spawn
::"sess.latchPlayerType" - the class of the player after next spawn
::"sess.latchPlayerWeapon" - the weapon of the player after next spawn
::"sess.latchPlayerWeapon2" - the sidearm of the player after next spawn
::"sess.damage_given" - the amount of damage to other team's players this player has inflicted
::"sess.damage_received" - the amount of damage this player has received from the other team
::"sess.deaths" - the amount of deaths
::"sess.game_points" - score
::"sess.kills" - the amount of kills this player has made
::"sess.medals" - an array of 7 integers for medals of each skill
::"sess.muted" and "sess.auto_unmute_time" - both of these point to the same data. This is the seconds left until unmute.
::"sess.rank" - the rank of the player
::"sess.referee" - the players referee/rcon status. Possible values are
:::0 - none
:::1 - referee
:::2 - rcon
::"sess.rounds" - the number of round. This has meaning only when playing stopwatch mode.
::"sess.skill" - an array of 7 integers for the level in each skill. Do note that this doesn't have an effect on the player abilities. Different indexes are
:::0 - battle sense
:::1 - explosives and construction (engineer)
:::2 - first aid (medic)
:::3 - signals (field ops)
:::4 - light weapons
:::5 - heavy weapons (soldier)
:::6 - military intelligence and scoped weapons (covert ops)
::"sess.spec_invite" - the which the player is invited to spectate
::"sess.spec_team" - the team the spectator is allowed to follow
::"sess.suicides" - the amount of suicides of the player. This does not limit to /kill.
::"sess.team_kills" - the amount of team kills made by this player
::"sess.team_damage_given" - the amount of damage to the own team made by this player
::"sess.team_damage_received" - the amount of damage this player has received from his/hers own team.
::"sess.aWeaponStats" - weapon statistics of the player. This is read only.
::"client.inactivityTime" - this is a ETPro compatibility alias for the "inactivityTime" field.
::"client.inactivityWarning" - this is a ETPro compatibility alias for the "inactivityWarning" field.
::"origin" - this is an alias for the "ps.origin" field
::"sess.team_damage" - this is an alias for the "sess.team_damage_given" field
::"sess.team_received" - this is an alias for the "sess.team_damage_received" field
::"sess.guid" - this is the silEnT GUID of the player. This has been validated by the mod. Validation in this context does not mean it can not have been spoofed.
::"sess.ip" - this is the IP address of the player
::"sess.uci" - this is the country flag number of the player
::"sess.ignoreClients" - this is a bitfield of ignored clients
::"sess.skillpoints" - an array of 7 floats for skill points in each skill
::"sess.kstreak" - the killing spree
::"sess.dstreak" - the death spree
::"sess.rstreak" - the revive spree
::"sess.shoutcaster" - 1 if the player is shoutcaster, 0 otherwise
::"sess.rating" - the player win probability rating
::"sess.rating_variance" - the player win probability variance
::"sess.overall_killrating" - the player kill rating
::"sess.overall_killvariance" - the player kill rating variance
::"pers.lastkilled_client" - the client number of the last kill
::"pers.lastrevive_client" - the client number of the player who revived this player last
::"pers.lastkiller_client" - the client number of the player who killed this player last
::"pers.lastammo_client" - the client number of the player who gave ammo to this player last
::"pers.lasthealth_client" - the client number of the player who gave health to this player last
::'''Field names for all entities'''
::never ending list of fields continued later
*''arrayindex'' is the index in an array if the entity field is an array, indexes start from 0

'''Portability'''

Function is ETPro compatible.

=== gentity_set ===
'''Description'''

Sets a value in an entity. See gentity_get for possible values.

'''Syntax'''

et.gentity_set( entnum, fieldname, arrayindex, value )
*''entnum'' is the entity number that is manipulated
*''fieldname'' is the name of the field to manipulate
*''arrayindex'' is either the value that is set or an array index if the field is an array
*''value'' is the new value if arrayindex is used as an array index

'''Portability'''

Function is ETPro compatible.

=== G_AddEvent ===
'''Description'''

Adds an event to the entity event sequence.

'''Syntax'''

et.G_AddEvent( ent, event, eventparm )
*''ent'' is the entity which event sequnce is handled
*''event'' is the event to add
*''eventparm'' is optional parameter for the event

'''Portability'''

Function is ETPro compatible.

== Shrubbot ==
=== G_shrubbot_permission ===
'''Description'''

Tells if the given player has the given shrubbot flag set.

'''Syntax'''

permission = et.G_shrubbot_permission( ent, flag )
*''ent'' is the slot number of the player whos permission is checked
*''flag'' is the flag character that is checked
*return value ''permission'' is 1 if the player has the flag set, 0 otherwise

'''Portability'''

Function is derived from the ETPub Lua API.

=== G_shrubbot_level ===
'''Description'''

Returns the shrubbot level of the player.

'''Syntax'''

level = et.G_shrubbot_level( ent )
*''ent'' is the slot number of the player whos permission is checked
*return value ''level'' is the shrubbot level of the player.

'''Portability'''

Function was derived from the ETPub Lua API.

== Time ==
=== trap_Milliseconds ===
'''Description'''

Returns level time in milliseconds.

'''Syntax'''

milliseconds = et.trap_Milliseconds()

'''Portability'''

'''Note'''

= Callbacks =

Callbacks are functions that are called by the qagame automatically, if function implementations are present in the Lua scripts. Every Lua script needs to implement at least one callback or it will not be run at all.

=== et_InitGame ===
'''Description'''

Called when the server game initializes. Called once after every level change and after warmup.

'''Syntax'''

et_InitGame( levelTime, randomSeed, restart )
*''levelTime'' is the current level time in milliseconds
*''randomSeed'' is a number that can be used to seed random number generators
*''restart'' tells if the function is called due to a map restart

'''Portability'''

Callback is ETPro compatible.

=== et_ShutdownGame ===
'''Description'''

Called when the server game shuts down.

'''Syntax'''

et_ShutdownGame( restart )
*''restart'' indicates if the server is doing map restart

'''Portability'''

Callback is ETPro compatible.

=== et_RunFrame ===
'''Description'''

Called at the end of each server frame.

'''Syntax'''

et_RunFrame( levelTime )
*''levelTime'' is the current level time in milliseconds

'''Portability'''

Callback is ETPro compatible.

=== et_ClientConnect ===
'''Description'''

Called for each connecting client. After the mod has performed most of its own actions. Connecting player can still be refused by this function.

'''Syntax'''

rejectreason = et_ClientConnect( clientNum, firstTime, isBot )
*''clientNum'' is the number of the client entity. Client number range is [0,63].
*''firstTime'' indicates if the player is connecting the first time or as a result of a map change or a map restart.
*''isBot'' indicates if the player is a server bot. Omni-bots do have this set.
*return value ''rejectreason'' is a string describing why the player is refused. If nil is returned, the player is allowed to connect.

'''Portability'''

Callback is ETPro compatible.

=== et_ClientDisconnect ===
'''Description'''

Called everytime a player is disconnected before any actions by the mod to the player data.

'''Syntax'''

et_ClientDisconnect( clientNum )
*''clientNum'' is the entity number of the player.

'''Portability'''

Function is ETPro compatible.

=== et_ClientBegin ===
'''Description'''

Called when the player is ready to be put into the world. After all mod actions. Function is called only once during the map.

'''Syntax'''

et_ClientBegin( clientNum )
*''clientNum'' is the entity number of the player

'''Portability'''

Function is ETPro compatible.

=== et_ClientUserinfoChanged ===
'''Description'''

Called if the player userinfo has changed.

'''Syntax'''

et_ClientUserinfoChanged( clientNum )
*''clientNum'' the entity number of the player

'''Portability'''

Callback is ETPro compatible.

=== et_ClientSpawn ===
'''Description'''

Called when a player is spawned.

'''Syntax'''

et_ClientSpawn( clientNum, revived, teamChange, restoreHealth )
*''clientNum'' is the entity number of the spawned player
*''revive'' is 1 if the player was revived, 0 otherwise
*''teamChange'' is 1 if the player changed team, 0 otherwise
*''restoreHealth'' is 1 if the player health bar is restored to full, 0 otherwise

'''Portability'''

Callback is ETPro compatible.

=== et_ClientCommand ===
'''Description'''

Called when a command is received from a player.

'''Syntax'''

intercepted = et_ClientCommand( clientNum, command )
*''clientNum'' is the entity number of the player
*''command'' is the command as a string
*return value ''intercepted'' must be set to 1 if the command execution is stopped at the Lua script. With value 0 the command is then processed in the server mod binary.

'''Portability'''

Callback is ETPro compatible.

=== et_ConsoleCommand ===
'''Description'''

Called when a command is entered to the server console.

'''Syntax'''

intercepted = et_ConsoleCommand( command )
*''command'' is the command name as a string
*return value ''intercepted'' is set to 1 if the command execution is stopped in the Lua script, 0 if the command is then executed in the server mod binary

'''Portability'''

Callback is ETPro compatible.

=== et_UpgradeSkill ===
'''Description'''

Called when a player receives a skill upgrade.

'''Syntax'''

result = et_UpgradeSkill( cno, skill )
*''cno'' is the entity number of the player
*''skill'' is the skill type that is upgraded
*return value ''result'' will abort the skill upgrade if set to -1, any other value will allow the skill upgrade progress through

'''Portability'''

Callback is in ETPro compatible.

=== et_SetPlayerSkill ===
'''Description'''

Called when a player skill level is set.

'''Syntax'''

intercepted = et_SetPlayerSkill( cno, skill )
*''cno'' is the entity number of the player
*''skill'' is the skil type of the player
*return value ''intercepted'' is set to -1 if the skill set is aborted, with any other value the set is allowed

'''Portability'''

Callback is ETPro compatible.

=== et_Print ===
'''Description'''

Called when server is printing to the console.

'''Syntax'''

et_Print( text )
*''text'' is the full printed text

'''Portability'''

Function is ETPro compatible. Differences may exist between ETPro, ETPub and silEnT.

=== et_Obituary ===
'''Description'''

Called when a player is killed. If a string is returned from the callback, it will replace the obituary message. The custom obituary can be printed to either chat or as a popup. This behaviour is defined with g_logOptions flag 1.

'''Syntax'''

(customObit) = et_Obituary( victim, killer, meansOfDeath )
*''victim'' is the entity number of the killed player
*''killer'' is the entity number of the killer, this can be also 1022 which means that the world was the killer
*''meansOfDeath'' is the means of death number
*return value ''customObit'' can be set to create customary obituary messages. If a custom obituary message is returned, only the custom obituary is printed.

'''Portability'''

Callback is ETPro compatible.

=== et_CvarValue ===

'''Description'''

Called when a client cvar value is ready to be passed to Lua scripts.

'''Syntax'''

et_CvarValue( clientNum, cvar, value )
*''clientNum'' is the slot number of the player
*''cvar'' is the name of the cvar
*''value'' is the value of the cvar

'''Portability'''

Callback was added in silEnT 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

=== et_ClientBinary ===

'''Description'''

Called when a player connects with an unrecognized client executable. Also called if the player connects with a known cheat binary.

'''Syntax'''

et_ClientBinary( clientNum, checksum )
*''clientNum'' is the slot number of the player
*''checksum'' is the 32 character MD5 checksum of the client executable (ET.exe)

'''Portability'''

Callback was added in silEnT 0.6.2 and it is not present in ETPro or ETPub Lua APIs.

=== et_IntermissionStarts ===

'''Description'''

Called one server frame before the game enters intermission.

'''Syntax'''

et_IntermissionStarts( round )
*''round'' is value of the g_currentRound cvar

'''Portability'''

Callback was added in silEnT 0.8.0 and it is not present in ETPro or ETPub Lua APIs.

= References =

* Document was constructed using information at http://wolfwiki.anime.net/index.php/ETPro:Lua_Mod_API as well as reading the mod source.

* Official Lua http://www.lua.org/

Silent Mod Client Cvar

2014-05-07T08:43:52Z

Silencerpl:

== Cvars ==

=== cg_drawTime ===

;Description
:Decides whether to draw the current local time beneath the FPS display. When set to 1, it will display 24 hour clock, when set to 2, it will display a 12 hour clock, with am/pm
;Usage
:<code>cg_drawTime [0|1|2]</code>

=== cg_drawTimeSeconds  ===

;Description
:When set to 1, will display the seconds as well on the time. Requires cg_drawTime set to either 1 or 2
;Usage
:<code>cg_drawTimeSeconds [0|1]</code>

=== cg_hud ===

;Description
:The name of your current hud, which will be loaded upon startup

=== cg_panzerhack ===

;Description
:Put your SMG in weaponbank 2 (instead of bank 3) when you're a soldier with level 4 Heavy Weapons
;Usage
:<code>cg_panzerhack [0|1]</code>

=== cg_logConsole  ===

;Description
:Log centerprints and/or banners to your console
;Usage
:<code>cg_logConsole [bitmask]</code>
:1 Log Centerprints
:2 Log Banners
:Default : 1

=== cg_gun_fovscale  ===

;Description
:Scale the gun when you use different FOV
;Usage
:<code>cg_gun_fovscale [0|1]</code>
:Default: 1

=== cg_weapaltReloads  ===

;Description
:Hitting altfire (usually right mouse button) when holding a weapon that doesn't have an alternative fire will reload the weapon
;Usage
:<code>cg_weapaltReloads [0|1]</code>
:Default: 0

=== cg_drawRanks  ===

;Description
:When 1 the rank (for example "Private") will be shown in front of the name when you look at a player in your team. When 2 it will only show the short rank ("Pvt" for exmaple) and when 0 it won't show any rank.
;Usage
:<code>cg_drawRanks [0|1|2]</code>
:Default: 1

=== cg_fireteamAlpha  ===

;Description
:Determines the level of transparency of the fireteam window
;Usage
:<code>cg_fireteamAlpha [0.0 - 1.0]</code>
:Default: 0.6

=== cg_lagometerAlpha  ===

;Description
:Determines the level of transparency of the lagometer
;Usage
:<code>cg_lagometerAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_chatAlpha  ===

;Description
:Determines the level of transparency of the chat texts at the bottom of your screen.
;Usage
:<code>cg_chatAlpha [0.0 - 1.0]</code>
:Default: 0.33

=== cg_watermarkAlpha  ===

;Description
:Determines the level of transparency of the watermark, if the server has one. Note that the server might set a transparency themselves. In that case the watermark alpha will be the product of these transparency levels.
;Usage
:<code>cg_watermarkAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_specAlpha  ===

;Description
:Determines the level of transparency of the SPECTATOR text.
;Usage
:

=== cg_dynoCounter  ===

;Description
:Displays a counter in your HUD that will countdown untill a dynamite on an objective explodes. This will not spam the chat/cpm
;Usage
:<code>cg_dynoCounter [0|1|2]</code>
:1 Visual
:2 Textual
:Default: 1

=== cg_maxTeamDynas  ===

;Description
:The number of dynamites of your own team that will be displayed in the counter
;Usage
:<code>cg_maxTeamDynas [0-8]</code>
:Default: 4

=== cg_maxEnemyDynas  ===

;Description
:The number of dynamites of your enemy that will be displayed in the counter
;Usage
:<code>cg_maxEnemyDynas [0-8]</code>
:Default: 4

=== cg_drawClassIcons  ===

;Description
:Changes Classtexts into ClassIcons
;Usage
:<code>cg_drawClassIcons [bitmask]</code>
:1 In crosshair names
:2 In fireteam
:4 On scoreboard
:Default: 7

=== cg_drawCrosshairHP  ===

;Description
:Draw textual HP instead of the healthbar when aiming at someone
;Usage
:<code>cg_drawCrosshairHP [0|1]</code>
:Default: 0

=== cg_autoSelectFTMembers  ===

;Description
:Toggles automatic selection of your fireteam members
;Usage
:<code>cg_autoSelectFTMembers [0|1]</code>
:Default: 0

=== cg_tracers  ===

;Description
:Enables/disables drawing the bullet tracers:
;Usage
:<code>cg_tracers [0|1|2]</code>
:0 No tracers.
:1 All tracers.
:2 All but your own tracers.
:Default: 1

=== cg_countryFlags  ===

;Description
:Show the GeoIP country flags
;Usage
:<code>cg_countryFlags [bitmask]</code>
:1 On scoreboard
:2 In crosshair names
:Default: 3

=== cg_gibs  ===

;Description
:Toggles the display of gib models.
;Usage
:<code>cg_gibs [0|1]</code>
:Default: 1

=== cg_followFT  ===

;Description
:Decides how players are picked up to be followed in spec.
;Usage
:<code>cg_followFT [0|1|2]</code>
:0 disables feature (works as usual then)
:1 follow Fire Team members first when in spec
:2 follow only Fire Team members when in spec.
:Options 1 and 2 work only when the player is in the Fire Team.
:When the player is not in FT then they do not infuence the spec behaviour.
:Default: 0

=== cg_showCountDown  ===

;Description
:Show last 3 secs warmup countdown.
;Usage
:<code>cg_showCountDown [0|1|]</code>
:0 Don't show countdown
:1 Show countdown
:Default: 1

=== cg_wbShowDuration  ===

;Description
:Display time of weapon banks in miliseconds (0 = off)
;Usage
:<code>cg_wbShowDuration [0-5000] in msecs</code>
:0 Don't show weapon banks
:1 to 5000 Other values up to 5000 show weapon banks display
:Default: 1000 (1 sec)

=== cg_wbOrientation  ===

;Description
:Orientation of weapon banks display.
;Usage
:<code>cg_wbOrientation [0|1]</code>
:0 horizontal
:1 vertical
:Default: 1 (vertical)

=== cg_wbWideSlots  ===

;Description
:Should wide slots be used for wide weapon icons.
;Usage
:<code>cg_wbWideSlots [0|1]</code>
:0 Don't use wide slots, use the same size for all weapons
:1 Use wide slots for wide weapon icons
:Default: 1

=== cg_landmineNotifyType  ===

;Description
:Decide which landmine reveal notifications player wants to receive.
:Server can send two types of landmines reveal notification.
:1 Standard one, generated (sent) for each landmine revealed.
:2 Summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.
;Usage
:<code>cg_landmineNotifyType [0|1|2]</code>
:0 only standard notfications (for each landmine revealed).
:1 only single summary notifications for one binocs zoom. New type of notification.
:For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is received. It contains information: 3 mines spotted by "player name" and last one was in location "some location"
:2 Don't receive any landmine notifications.
:Default: 0 (only standard notifications)

=== cg_tdmShow  ===

;Description
:Specify the way the Team Death Match (TDM) score is displayed.
:The TDM score can be displayed in two ways. It can be displayed all the time or it can be displayed when the +tdmScore command is issued in the console or the bound key to that command is pressed.
;Usage
:<code>cg_tdmShow [0|1]</code>
:0 Show only when the bound key is pressed.
:1 Show TDM score all the time.
:Default: 1 (show all the time)

=== cg_tdmTimeBar  ===

;Description
:Specify if the Team Death Match (TDM) time progress bar is to be shown below the TDM score. The TDM time progress bar is shown only when the Team Deatch Match has time limit specified.
;Usage
::0 Don't show time progress bar.
:1 Show TDM time progress bar.
:Default: 1

=== cg_locations  ===

;Description
:Specify the way the map locations are displayed (in Fire Team display for example).
;Usage
:<code>cg_locations [0|1|2]</code>
:0 Display only X,Y coordinates.
:1 Display only location name.
:2 Display X,Y coordinate and location name.
:Default: 1

=== ui_theme ===

;Description
:This cvar allows to switch between silEnT themes. silEnT themes is the UI feature that added new fresh feel to menus and some HUD elements. silEnT mod has 2 themes available to choose from.
;Usage
:<code>ui_theme [1|2]</code>
:1 Use the 1st theme to draw UI.
:2 Use the 2nd theme to draw UI.
:Default: 2

=== cg_themedCMap ===

;Description
:Specify the way the command map should be drawn (themed one or the standard one). Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the command map frame will be drawn differently.
;Usage
:<code>cg_themedCMap [0|1]</code>
:0 Don't use silEnT themes to draw command map frame.
:1 Draw command map with themed frame.
;Default 0

=== cg_themedDraws ===

;Description
:Specifies how draws (time, fps, timer, speedometer), K/D/S display and lagometer are drawn. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the elements mentioned above will be drawn differently.
;Usage
:<code>cg_themedDraws [0|1]</code>
:0 Don't use silEnT themes to draw draws, K/D/S and lagometer.
:1 Use silEnT themes to draw draws, K/D/S and lagometer.
;Default 1

=== ui_themedCursor ===

;Description
:Disables or enables themed mouse cursor. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the mouse cursor will be different.
;Usage
:<code>ui_themedCursor [0|1]</code>
:0 Don't use silEnT themes to draw mouse cursor.
:1 Draw themed mouse cursor.
;Default 1

=== cg_hitSoundType ===

;Description
:Player selection of the hit sounds. Starting from silEnT mod 0.6.0, the players can choose what kind of hit sounds are played. If this cvar is set to 0, the hitsounds are determined by the server g_defaultHitSounds setting and possible overloaded hit sound files in custom pk3 files.
;Usage
:<code>cg_hitSoundType [0|1|2|3]</code>
:0 Use server defined hit sounds.
:1 Use strictly silEnT hit sounds.
:2 Use strictly ETPro hit sounds.
:3 Use strictly ETPub hit sounds.
;Default 0

=== cg_effectDistance ===

;Description
:Players can adjust what is the maximum distance that bullet effects are drawn. This can give slight performance improvement in maps with large open areas by not drawing effects to a distance player can't see them anyway. These effects include trails in the water, splashes, smoke pufs and different impact marks on the surfaces. This setting does not effect the sounds or the tracers.
;Usage
:<code>cg_effectDistance [integer]</code>
;Default 4000

=== cg_killsDisplay ===

;Description
:Defines the shown kill spree counter values.
:<code>cg_killsDisplay [0|1|2|3|4]</code>
:0 Disabled
:1 Show Total Kills and Total deaths
:2 Show Total Kills, Total Deaths and Sprees
:3 Show Total Sprees
:4 Total kills
;Default 0

=== cg_kspreepos ===

;Description
:Controls where the killing spree announcements are displayed.
:<code>cg_kspreepos [0|1|2|3|4]</code>
:0 Disabled
:1 Popup
:2 Chat area
:3 Banners
:4 Center Print
;Default 0

=== cg_objcarry ===

;Description
:Disables or enables drawing of enemy objective carry indicator.
:Draws enemy objective counter when enemy team is carrying objective. In order to make this work server is required to have g_misc 1024 bitflag set.

:<code>cg_objcarry [0|1]</code>

:0 Disabled
:1 Enabled - draw carry indicator.
;Default 1

== Commands ==

=== Private Message ===

; Description
:Send private message to all players matching the partial name.
; Usage
:<code>'''m [partialname] [message]'''</code>

; Description
:Send private message to all players on your team that match the partial name.
; Usage
:<code>'''mt [partialname] [message]'''</code>

=== loadhud ===

; Description
:Used to load a custom hud from a .hud file contained in a pk3 file. Also able to "/loadhud ?" to show a list of available huds, "/loadhud blank" to load a blank hud, or "/loadhud" to load the default ET hud. When loading a hud, the default ET is loaded first, then the custom HUD overwrites any values specified. So if a HUD element isn't specifically disabled in a custom HUD, it will be in ET default position.

=== edithud ===

; Description
:Used to edit the hud in realtime. Can also be used to script a hud so that server admins don't have to package .hud files into pk3
; Usage

'''format:''' ''/edithud elementName [value1] [value2] . . . . [valueX]''

Current ''elementNames'' and ''(values)'' are as follows:

:*ammocount (x, y, scale)
:*chargebar (x, y, width)
:*compass (x, y, size)
:*upperright (y)
:*fireteam (x, y, width)
:*flagcov (x, y)
:*head (x, y, width, height)
:*healthbar (x, y, width)
:*healthtext (x, y, scale)
:*lagometer (x, y)
:*overheat (x, y, width, height)
:*skillbox1 (x, y, size)
:*skillbox2 (x, y, size)
:*skillbox3 (x, y, size)
:*skillpic1 (x, y, size)
:*skillpic2 (x, y, size)
:*skillpic3 (x, y, size)
:*skilltext1 (x, y, scale)
:*skilltext2 (x, y, scale)
:*skilltext3 (x, y, scale)
:*staminabar (x, y, width)
:*weaponcard (x, y, size)
:*xptext (x, y, scale)
:*cpmtext (x, y, scale)
:*chattext (x, y, scale)
:*votefttext (x, y)
:*livesleft (x, y)

All items except skilltextX are part of the original ET hud. skillTextX is a textual representation of the xp levels, i.e. 0, 1, 2, 3, 4. The skill[box,pic,text] elements correspond as follows, 1 = class specific skills, 2 = battle sense, 3 = light weapons

Default ''scale'' values, where used, is 25 in the default ET hud.

''upperright'' represents the spawn counter/game timer, clock, FPS normally displayed on the right side of the screen.

(x,y) are based on a 640 x 480 scale, regardless of the actual screen resolution that ET is running. Therefore (0,0) is upper left, (640,480) is lower right and (320, 240) is crosshairs

To disable an element entirely, set the first value to -1. Currently votefttext CANNOT be disabled

=== dumphud ===

; Description
:Dumps the current hud settings to the console in format used to create a .hud file

=== dropweapon ===

; Description
:Drops the player's primary weapon.

=== Shoutcast Login ===

;Description
:Logs the player into shoutcasting mode.
;Usage
:<code>sclogin [password]</code>
:<code>shoutcastlogin [password]</code>

=== Shoutcast Logout ===

;Description
:Removes the player's own shoutcaster status.
;Usage
:<code>sclogout</code>
:<code>shoutcastlogout</code>

=== timerset ===

;Description
:Sets enemy spawntimer (shown in red). You need to give the value for the timer. Not giving any value will disable the spawntimer.
;Usage
:<code>timerSet [1-60]</code>

=== resetTimer ===

;Description
:Resets the enemy spawn timer to the value which was given when timerSet was called. This command will do nothing if timerSet hasn't been called before.

=== lua_status ===

;Description
:Shows information about the scripts currently loaded by the Lua API engine.

=== silent_version ===

;Description
:Shows information about the running client and server version.

== Autoexec Files/Config ==

The silEnT client now has the ability to automatically execute certain config (*.cfg) files upon certain events:

Executed when you join a team (or become a spectator)

;'''autoexec_allies.cfg, autoexec_axis.cfg, autoexec_spectator.cfg'''
:

Executed when the map switches to <mapname>. autoexec_default.cfg is always executed after the autoexec_<mapname>.cfg file.

'''autoexec_<mapname>.cfg, autoexec_default.cfg'''

Executed when you switch classes

'''autoexec_soldier.cfg, autoexec_medic.cfg, autoexec_engineer.cfg, autoexec_fieldops.cfg, autoexec_covertops.cfg'''

'''''Note1: '''''If any of these files do not exist they simply will not be executed, there will not be any error messages.

'''''Note2''''': These filenames are casesensitive on linux.

Silent Mod Server Cvar

2014-05-07T08:40:19Z

Silencerpl: g_misc added flag 1024

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

'''Type:''' [0|1|2]

'''Parameters:'''

1 Show player AntiCheat status in the !finger output.

2 Automatically ban players with cheats.

'''Default:''' 0

'''Minimum required version:''' 0.8.0

= Announcements and Messages =

== g_privateMessages ==

'''Description:''' 

If set to 1, players can send private messages to one another with the /m playername/slot command.

'''Type:''' [0|1]

'''Parameters:'''

0 Disable Private Messages

1 Enable Private messages

'''Default:''' 0

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description:''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_recognition ==

'''Description:'''

Enables additional recognition notifications for players doing objective, e.g. for planting dynamite, disarming it, destroying objective.

'''Type:''' [0|1]

'''Parameters:'''

0 Additional recognition notifications disabled.

1 Additional recognition notifications enabled.

'''Default:''' 1

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

== g_muteRename ==

'''Description:'''

If this cvar is set to 1 the muted player won't be allowed to change his name while he is muted.

'''Type:''' integer

'''Parameters:'''

0 Disabled. Allow players to change his/her name while he/she is muted. 

1 Don't allow player to change his/her name while he/she is muted. 

'''Default:''' 0

'''Minimium required version:''' 0.8.0

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points.

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_includedMaps ===

'''Description:'''

Used to include map regardless of any other restrictions. Including g_excludedMaps setting. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" or otherwise the map will be ignored in the list.
Only valid when map voting is enabled.

'''Type:''' string

'''Default:''' ""

'''Minimum required version:''' 0.6.2

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_proneDelay ==

'''Description:'''

If set, there will be 1750 ms delay after every prone or getting up before the player can prone or get up again. Also, weapon spread will be maxed for 1 second after proning.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 0

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

1024 Enable the enemy team objective carry indicator.

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

16 Tripmines

32 Completely

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

16384 Admin log will use new format that is more readable.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

0.8.0 - Flag 16384. When this flag is set, the admin log will use new format.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

= Debugging =

== g_debugBullets ==

''' Description:'''

If this cvar is set, server will produce debug information of fired bullets. Enabling g_debugBullets require sv_cheats to be set.

'''Type:''' integer

'''Parameters:'''

If 1 is set as if the cvar was a bitmask, blue lines for the fired shots is enabled. With any positive value, server will print impact area on the hit player to the center of the screen. Possibilities are "Head Shot", "Body Shot", "Leg Shot" and "Arm Shot". If the value is set to 2 or more, the bounding box of the hit player is drawn. If the value is set to 3 or more, the hit player head box is drawn. If the value is set to -2 or smaller, boxes are drawn to impacted surfaces.

'''Default: 0

== g_debugDamage ==

''' Description:'''

If this cvar is set, damage inflicted to players is logged into the server log. Enabling this cvar requiers sv_cheats to be set.

'''Type:''' [0|1]

'''Default:''' 0

== g_debugHitboxes ==

'''Description:'''

If this cvar is enabled, hit boxes around the players are drawn. This cvar does not require sv_cheats. However, do note that if this is enabled, the server will produce constant flow of extra entities, which will make playing impossible on a live server. Test this with only couple players to prevent everyone from lagging out.

'''Type:''' integer

'''Parameters:'''

If this cvar is set to any positive value, boxes are drawn. If the value is set to 8 or more, it will draw only the boxes that are used for the initial trace. Each bullet causes two traces to happen, where the second trace confirms the impact on the more refined area of the player body, such as head or legs.

Silent Mod Client Cvar

2014-05-07T08:38:13Z

Silencerpl: added cg_objcarry cvar

== Cvars ==

=== cg_drawTime ===

;Description
:Decides whether to draw the current local time beneath the FPS display. When set to 1, it will display 24 hour clock, when set to 2, it will display a 12 hour clock, with am/pm
;Usage
:<code>cg_drawTime [0|1|2]</code>

=== cg_drawTimeSeconds  ===

;Description
:When set to 1, will display the seconds as well on the time. Requires cg_drawTime set to either 1 or 2
;Usage
:<code>cg_drawTimeSeconds [0|1]</code>

=== cg_hud ===

;Description
:The name of your current hud, which will be loaded upon startup

=== cg_panzerhack ===

;Description
:Put your SMG in weaponbank 2 (instead of bank 3) when you're a soldier with level 4 Heavy Weapons
;Usage
:<code>cg_panzerhack [0|1]</code>

=== cg_logConsole  ===

;Description
:Log centerprints and/or banners to your console
;Usage
:<code>cg_logConsole [bitmask]</code>
:1 Log Centerprints
:2 Log Banners
:Default : 1

=== cg_gun_fovscale  ===

;Description
:Scale the gun when you use different FOV
;Usage
:<code>cg_gun_fovscale [0|1]</code>
:Default: 1

=== cg_weapaltReloads  ===

;Description
:Hitting altfire (usually right mouse button) when holding a weapon that doesn't have an alternative fire will reload the weapon
;Usage
:<code>cg_weapaltReloads [0|1]</code>
:Default: 0

=== cg_drawRanks  ===

;Description
:When 1 the rank (for example "Private") will be shown in front of the name when you look at a player in your team. When 2 it will only show the short rank ("Pvt" for exmaple) and when 0 it won't show any rank.
;Usage
:<code>cg_drawRanks [0|1|2]</code>
:Default: 1

=== cg_fireteamAlpha  ===

;Description
:Determines the level of transparency of the fireteam window
;Usage
:<code>cg_fireteamAlpha [0.0 - 1.0]</code>
:Default: 0.6

=== cg_lagometerAlpha  ===

;Description
:Determines the level of transparency of the lagometer
;Usage
:<code>cg_lagometerAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_chatAlpha  ===

;Description
:Determines the level of transparency of the chat texts at the bottom of your screen.
;Usage
:<code>cg_chatAlpha [0.0 - 1.0]</code>
:Default: 0.33

=== cg_watermarkAlpha  ===

;Description
:Determines the level of transparency of the watermark, if the server has one. Note that the server might set a transparency themselves. In that case the watermark alpha will be the product of these transparency levels.
;Usage
:<code>cg_watermarkAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_specAlpha  ===

;Description
:Determines the level of transparency of the SPECTATOR text.
;Usage
:

=== cg_dynoCounter  ===

;Description
:Displays a counter in your HUD that will countdown untill a dynamite on an objective explodes. This will not spam the chat/cpm
;Usage
:<code>cg_dynoCounter [0|1|2]</code>
:1 Visual
:2 Textual
:Default: 1

=== cg_maxTeamDynas  ===

;Description
:The number of dynamites of your own team that will be displayed in the counter
;Usage
:<code>cg_maxTeamDynas [0-8]</code>
:Default: 4

=== cg_maxEnemyDynas  ===

;Description
:The number of dynamites of your enemy that will be displayed in the counter
;Usage
:<code>cg_maxEnemyDynas [0-8]</code>
:Default: 4

=== cg_drawClassIcons  ===

;Description
:Changes Classtexts into ClassIcons
;Usage
:<code>cg_drawClassIcons [bitmask]</code>
:1 In crosshair names
:2 In fireteam
:4 On scoreboard
:Default: 7

=== cg_drawCrosshairHP  ===

;Description
:Draw textual HP instead of the healthbar when aiming at someone
;Usage
:<code>cg_drawCrosshairHP [0|1]</code>
:Default: 0

=== cg_autoSelectFTMembers  ===

;Description
:Toggles automatic selection of your fireteam members
;Usage
:<code>cg_autoSelectFTMembers [0|1]</code>
:Default: 0

=== cg_tracers  ===

;Description
:Enables/disables drawing the bullet tracers:
;Usage
:<code>cg_tracers [0|1|2]</code>
:0 No tracers.
:1 All tracers.
:2 All but your own tracers.
:Default: 1

=== cg_countryFlags  ===

;Description
:Show the GeoIP country flags
;Usage
:<code>cg_countryFlags [bitmask]</code>
:1 On scoreboard
:2 In crosshair names
:Default: 3

=== cg_gibs  ===

;Description
:Toggles the display of gib models.
;Usage
:<code>cg_gibs [0|1]</code>
:Default: 1

=== cg_followFT  ===

;Description
:Decides how players are picked up to be followed in spec.
;Usage
:<code>cg_followFT [0|1|2]</code>
:0 disables feature (works as usual then)
:1 follow Fire Team members first when in spec
:2 follow only Fire Team members when in spec.
:Options 1 and 2 work only when the player is in the Fire Team.
:When the player is not in FT then they do not infuence the spec behaviour.
:Default: 0

=== cg_showCountDown  ===

;Description
:Show last 3 secs warmup countdown.
;Usage
:<code>cg_showCountDown [0|1|]</code>
:0 Don't show countdown
:1 Show countdown
:Default: 1

=== cg_wbShowDuration  ===

;Description
:Display time of weapon banks in miliseconds (0 = off)
;Usage
:<code>cg_wbShowDuration [0-5000] in msecs</code>
:0 Don't show weapon banks
:1 to 5000 Other values up to 5000 show weapon banks display
:Default: 1000 (1 sec)

=== cg_wbOrientation  ===

;Description
:Orientation of weapon banks display.
;Usage
:<code>cg_wbOrientation [0|1]</code>
:0 horizontal
:1 vertical
:Default: 1 (vertical)

=== cg_wbWideSlots  ===

;Description
:Should wide slots be used for wide weapon icons.
;Usage
:<code>cg_wbWideSlots [0|1]</code>
:0 Don't use wide slots, use the same size for all weapons
:1 Use wide slots for wide weapon icons
:Default: 1

=== cg_landmineNotifyType  ===

;Description
:Decide which landmine reveal notifications player wants to receive.
:Server can send two types of landmines reveal notification.
:1 Standard one, generated (sent) for each landmine revealed.
:2 Summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.
;Usage
:<code>cg_landmineNotifyType [0|1|2]</code>
:0 only standard notfications (for each landmine revealed).
:1 only single summary notifications for one binocs zoom. New type of notification.
:For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is received. It contains information: 3 mines spotted by "player name" and last one was in location "some location"
:2 Don't receive any landmine notifications.
:Default: 0 (only standard notifications)

=== cg_tdmShow  ===

;Description
:Specify the way the Team Death Match (TDM) score is displayed.
:The TDM score can be displayed in two ways. It can be displayed all the time or it can be displayed when the +tdmScore command is issued in the console or the bound key to that command is pressed.
;Usage
:<code>cg_tdmShow [0|1]</code>
:0 Show only when the bound key is pressed.
:1 Show TDM score all the time.
:Default: 1 (show all the time)

=== cg_tdmTimeBar  ===

;Description
:Specify if the Team Death Match (TDM) time progress bar is to be shown below the TDM score. The TDM time progress bar is shown only when the Team Deatch Match has time limit specified.
;Usage
::0 Don't show time progress bar.
:1 Show TDM time progress bar.
:Default: 1

=== cg_locations  ===

;Description
:Specify the way the map locations are displayed (in Fire Team display for example).
;Usage
:<code>cg_locations [0|1|2]</code>
:0 Display only X,Y coordinates.
:1 Display only location name.
:2 Display X,Y coordinate and location name.
:Default: 1

=== ui_theme ===

;Description
:This cvar allows to switch between silEnT themes. silEnT themes is the UI feature that added new fresh feel to menus and some HUD elements. silEnT mod has 2 themes available to choose from.
;Usage
:<code>ui_theme [1|2]</code>
:1 Use the 1st theme to draw UI.
:2 Use the 2nd theme to draw UI.
:Default: 2

=== cg_themedCMap ===

;Description
:Specify the way the command map should be drawn (themed one or the standard one). Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the command map frame will be drawn differently.
;Usage
:<code>cg_themedCMap [0|1]</code>
:0 Don't use silEnT themes to draw command map frame.
:1 Draw command map with themed frame.
;Default 0

=== cg_themedDraws ===

;Description
:Specifies how draws (time, fps, timer, speedometer), K/D/S display and lagometer are drawn. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the elements mentioned above will be drawn differently.
;Usage
:<code>cg_themedDraws [0|1]</code>
:0 Don't use silEnT themes to draw draws, K/D/S and lagometer.
:1 Use silEnT themes to draw draws, K/D/S and lagometer.
;Default 1

=== ui_themedCursor ===

;Description
:Disables or enables themed mouse cursor. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the mouse cursor will be different.
;Usage
:<code>ui_themedCursor [0|1]</code>
:0 Don't use silEnT themes to draw mouse cursor.
:1 Draw themed mouse cursor.
;Default 1

=== cg_hitSoundType ===

;Description
:Player selection of the hit sounds. Starting from silEnT mod 0.6.0, the players can choose what kind of hit sounds are played. If this cvar is set to 0, the hitsounds are determined by the server g_defaultHitSounds setting and possible overloaded hit sound files in custom pk3 files.
;Usage
:<code>cg_hitSoundType [0|1|2|3]</code>
:0 Use server defined hit sounds.
:1 Use strictly silEnT hit sounds.
:2 Use strictly ETPro hit sounds.
:3 Use strictly ETPub hit sounds.
;Default 0

=== cg_effectDistance ===

;Description
:Players can adjust what is the maximum distance that bullet effects are drawn. This can give slight performance improvement in maps with large open areas by not drawing effects to a distance player can't see them anyway. These effects include trails in the water, splashes, smoke pufs and different impact marks on the surfaces. This setting does not effect the sounds or the tracers.
;Usage
:<code>cg_effectDistance [integer]</code>
;Default 4000

=== cg_killsDisplay ===

;Description
:Defines the shown kill spree counter values.
:<code>cg_killsDisplay [0|1|2|3|4]</code>
:0 Disabled
:1 Show Total Kills and Total deaths
:2 Show Total Kills, Total Deaths and Sprees
:3 Show Total Sprees
:4 Total kills
;Default 0

=== cg_kspreepos ===

;Description
:Controls where the killing spree announcements are displayed.
:<code>cg_kspreepos [0|1|2|3|4]</code>
:0 Disabled
:1 Popup
:2 Chat area
:3 Banners
:4 Center Print
;Default 0

=== cg_objcarry ===

;Description
:Draw enemy objective counter when enemy team is carrying objective.
:<code>cg_objcarry [0|1]</code>
:0 Disabled
:1 Enabled
;Default 1

== Commands ==

=== Private Message ===

; Description
:Send private message to all players matching the partial name.
; Usage
:<code>'''m [partialname] [message]'''</code>

; Description
:Send private message to all players on your team that match the partial name.
; Usage
:<code>'''mt [partialname] [message]'''</code>

=== loadhud ===

; Description
:Used to load a custom hud from a .hud file contained in a pk3 file. Also able to "/loadhud ?" to show a list of available huds, "/loadhud blank" to load a blank hud, or "/loadhud" to load the default ET hud. When loading a hud, the default ET is loaded first, then the custom HUD overwrites any values specified. So if a HUD element isn't specifically disabled in a custom HUD, it will be in ET default position.

=== edithud ===

; Description
:Used to edit the hud in realtime. Can also be used to script a hud so that server admins don't have to package .hud files into pk3
; Usage

'''format:''' ''/edithud elementName [value1] [value2] . . . . [valueX]''

Current ''elementNames'' and ''(values)'' are as follows:

:*ammocount (x, y, scale)
:*chargebar (x, y, width)
:*compass (x, y, size)
:*upperright (y)
:*fireteam (x, y, width)
:*flagcov (x, y)
:*head (x, y, width, height)
:*healthbar (x, y, width)
:*healthtext (x, y, scale)
:*lagometer (x, y)
:*overheat (x, y, width, height)
:*skillbox1 (x, y, size)
:*skillbox2 (x, y, size)
:*skillbox3 (x, y, size)
:*skillpic1 (x, y, size)
:*skillpic2 (x, y, size)
:*skillpic3 (x, y, size)
:*skilltext1 (x, y, scale)
:*skilltext2 (x, y, scale)
:*skilltext3 (x, y, scale)
:*staminabar (x, y, width)
:*weaponcard (x, y, size)
:*xptext (x, y, scale)
:*cpmtext (x, y, scale)
:*chattext (x, y, scale)
:*votefttext (x, y)
:*livesleft (x, y)

All items except skilltextX are part of the original ET hud. skillTextX is a textual representation of the xp levels, i.e. 0, 1, 2, 3, 4. The skill[box,pic,text] elements correspond as follows, 1 = class specific skills, 2 = battle sense, 3 = light weapons

Default ''scale'' values, where used, is 25 in the default ET hud.

''upperright'' represents the spawn counter/game timer, clock, FPS normally displayed on the right side of the screen.

(x,y) are based on a 640 x 480 scale, regardless of the actual screen resolution that ET is running. Therefore (0,0) is upper left, (640,480) is lower right and (320, 240) is crosshairs

To disable an element entirely, set the first value to -1. Currently votefttext CANNOT be disabled

=== dumphud ===

; Description
:Dumps the current hud settings to the console in format used to create a .hud file

=== dropweapon ===

; Description
:Drops the player's primary weapon.

=== Shoutcast Login ===

;Description
:Logs the player into shoutcasting mode.
;Usage
:<code>sclogin [password]</code>
:<code>shoutcastlogin [password]</code>

=== Shoutcast Logout ===

;Description
:Removes the player's own shoutcaster status.
;Usage
:<code>sclogout</code>
:<code>shoutcastlogout</code>

=== timerset ===

;Description
:Sets enemy spawntimer (shown in red). You need to give the value for the timer. Not giving any value will disable the spawntimer.
;Usage
:<code>timerSet [1-60]</code>

=== resetTimer ===

;Description
:Resets the enemy spawn timer to the value which was given when timerSet was called. This command will do nothing if timerSet hasn't been called before.

=== lua_status ===

;Description
:Shows information about the scripts currently loaded by the Lua API engine.

=== silent_version ===

;Description
:Shows information about the running client and server version.

== Autoexec Files/Config ==

The silEnT client now has the ability to automatically execute certain config (*.cfg) files upon certain events:

Executed when you join a team (or become a spectator)

;'''autoexec_allies.cfg, autoexec_axis.cfg, autoexec_spectator.cfg'''
:

Executed when the map switches to <mapname>. autoexec_default.cfg is always executed after the autoexec_<mapname>.cfg file.

'''autoexec_<mapname>.cfg, autoexec_default.cfg'''

Executed when you switch classes

'''autoexec_soldier.cfg, autoexec_medic.cfg, autoexec_engineer.cfg, autoexec_fieldops.cfg, autoexec_covertops.cfg'''

'''''Note1: '''''If any of these files do not exist they simply will not be executed, there will not be any error messages.

'''''Note2''''': These filenames are casesensitive on linux.

Silent Mod Server Cvar

2014-03-05T11:39:37Z

Silencerpl: /* g_classWeapons */

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

'''Type:''' [0|1|2]

'''Parameters:'''

1 Show player AntiCheat status in the !finger output.

2 Automatically ban players with cheats.

'''Default:''' 0

'''Minimum required version:''' 0.8.0

= Announcements and Messages =

== g_privateMessages ==

'''Description:''' 

If set to 1, players can send private messages to one another with the /m playername/slot command.

'''Type:''' [0|1]

'''Parameters:'''

0 Disable Private Messages

1 Enable Private messages

'''Default:''' 0

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description:''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_recognition ==

'''Description:'''

Enables additional recognition notifications for players doing objective, e.g. for planting dynamite, disarming it, destroying objective.

'''Type:''' [0|1]

'''Parameters:'''

0 Additional recognition notifications disabled.

1 Additional recognition notifications enabled.

'''Default:''' 1

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

== g_muteRename ==

'''Description:'''

If this cvar is set to 1 the muted player won't be allowed to change his name while he is muted.

'''Type:''' integer

'''Parameters:'''

0 Disabled. Allow players to change his/her name while he/she is muted. 

1 Don't allow player to change his/her name while he/she is muted. 

'''Default:''' 0

'''Minimium required version:''' 0.8.0

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points.

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_includedMaps ===

'''Description:'''

Used to include map regardless of any other restrictions. Including g_excludedMaps setting. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" or otherwise the map will be ignored in the list.
Only valid when map voting is enabled.

'''Type:''' string

'''Default:''' ""

'''Minimum required version:''' 0.6.2

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_proneDelay ==

'''Description:'''

If set, there will be 1750 ms delay after every prone or getting up before the player can prone or get up again. Also, weapon spread will be maxed for 1 second after proning.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 0

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

16 Tripmines

32 Completely

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

16384 Admin log will use new format that is more readable.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

0.8.0 - Flag 16384. When this flag is set, the admin log will use new format.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Server Cvar

2014-03-05T11:39:19Z

Silencerpl: /* g_classWeapons */

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

'''Type:''' [0|1|2]

'''Parameters:'''

1 Show player AntiCheat status in the !finger output.

2 Automatically ban players with cheats.

'''Default:''' 0

'''Minimum required version:''' 0.8.0

= Announcements and Messages =

== g_privateMessages ==

'''Description:''' 

If set to 1, players can send private messages to one another with the /m playername/slot command.

'''Type:''' [0|1]

'''Parameters:'''

0 Disable Private Messages

1 Enable Private messages

'''Default:''' 0

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description:''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_recognition ==

'''Description:'''

Enables additional recognition notifications for players doing objective, e.g. for planting dynamite, disarming it, destroying objective.

'''Type:''' [0|1]

'''Parameters:'''

0 Additional recognition notifications disabled.

1 Additional recognition notifications enabled.

'''Default:''' 1

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

== g_muteRename ==

'''Description:'''

If this cvar is set to 1 the muted player won't be allowed to change his name while he is muted.

'''Type:''' integer

'''Parameters:'''

0 Disabled. Allow players to change his/her name while he/she is muted. 

1 Don't allow player to change his/her name while he/she is muted. 

'''Default:''' 0

'''Minimium required version:''' 0.8.0

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points.

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_includedMaps ===

'''Description:'''

Used to include map regardless of any other restrictions. Including g_excludedMaps setting. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" or otherwise the map will be ignored in the list.
Only valid when map voting is enabled.

'''Type:''' string

'''Default:''' ""

'''Minimum required version:''' 0.6.2

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class.
'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_proneDelay ==

'''Description:'''

If set, there will be 1750 ms delay after every prone or getting up before the player can prone or get up again. Also, weapon spread will be maxed for 1 second after proning.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 0

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

16 Tripmines

32 Completely

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

16384 Admin log will use new format that is more readable.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

0.8.0 - Flag 16384. When this flag is set, the admin log will use new format.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Client Cvar

2013-10-06T13:26:10Z

Silencerpl: /* cg_kspreepos */

== Cvars ==

=== cg_drawTime ===

;Description
:Decides whether to draw the current local time beneath the FPS display. When set to 1, it will display 24 hour clock, when set to 2, it will display a 12 hour clock, with am/pm
;Usage
:<code>cg_drawTime [0|1|2]</code>

=== cg_drawTimeSeconds  ===

;Description
:When set to 1, will display the seconds as well on the time. Requires cg_drawTime set to either 1 or 2
;Usage
:<code>cg_drawTimeSeconds [0|1]</code>

=== cg_hud ===

;Description
:The name of your current hud, which will be loaded upon startup

=== cg_panzerhack ===

;Description
:Put your SMG in weaponbank 2 (instead of bank 3) when you're a soldier with level 4 Heavy Weapons
;Usage
:<code>cg_panzerhack [0|1]</code>

=== cg_logConsole  ===

;Description
:Log centerprints and/or banners to your console
;Usage
:<code>cg_logConsole [bitmask]</code>
:1 Log Centerprints
:2 Log Banners
:Default : 1

=== cg_gun_fovscale  ===

;Description
:Scale the gun when you use different FOV
;Usage
:<code>cg_gun_fovscale [0|1]</code>
:Default: 1

=== cg_weapaltReloads  ===

;Description
:Hitting altfire (usually right mouse button) when holding a weapon that doesn't have an alternative fire will reload the weapon
;Usage
:<code>cg_weapaltReloads [0|1]</code>
:Default: 0

=== cg_drawRanks  ===

;Description
:When 1 the rank (for example "Private") will be shown in front of the name when you look at a player in your team. When 2 it will only show the short rank ("Pvt" for exmaple) and when 0 it won't show any rank.
;Usage
:<code>cg_drawRanks [0|1|2]</code>
:Default: 1

=== cg_fireteamAlpha  ===

;Description
:Determines the level of transparency of the fireteam window
;Usage
:<code>cg_fireteamAlpha [0.0 - 1.0]</code>
:Default: 0.6

=== cg_lagometerAlpha  ===

;Description
:Determines the level of transparency of the lagometer
;Usage
:<code>cg_lagometerAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_chatAlpha  ===

;Description
:Determines the level of transparency of the chat texts at the bottom of your screen.
;Usage
:<code>cg_chatAlpha [0.0 - 1.0]</code>
:Default: 0.33

=== cg_watermarkAlpha  ===

;Description
:Determines the level of transparency of the watermark, if the server has one. Note that the server might set a transparency themselves. In that case the watermark alpha will be the product of these transparency levels.
;Usage
:<code>cg_watermarkAlpha [0.0 - 1.0]</code>
:Default: 1.0

=== cg_specAlpha  ===

;Description
:Determines the level of transparency of the SPECTATOR text.
;Usage
:

=== cg_dynoCounter  ===

;Description
:Displays a counter in your HUD that will countdown untill a dynamite on an objective explodes. This will not spam the chat/cpm
;Usage
:<code>cg_dynoCounter [0|1|2]</code>
:1 Visual
:2 Textual
:Default: 1

=== cg_maxTeamDynas  ===

;Description
:The number of dynamites of your own team that will be displayed in the counter
;Usage
:<code>cg_maxTeamDynas [0-8]</code>
:Default: 4

=== cg_maxEnemyDynas  ===

;Description
:The number of dynamites of your enemy that will be displayed in the counter
;Usage
:<code>cg_maxEnemyDynas [0-8]</code>
:Default: 4

=== cg_drawClassIcons  ===

;Description
:Changes Classtexts into ClassIcons
;Usage
:<code>cg_drawClassIcons [bitmask]</code>
:1 In crosshair names
:2 In fireteam
:4 On scoreboard
:Default: 7

=== cg_drawCrosshairHP  ===

;Description
:Draw textual HP instead of the healthbar when aiming at someone
;Usage
:<code>cg_drawCrosshairHP [0|1]</code>
:Default: 0

=== cg_autoSelectFTMembers  ===

;Description
:Toggles automatic selection of your fireteam members
;Usage
:<code>cg_autoSelectFTMembers [0|1]</code>
:Default: 0

=== cg_tracers  ===

;Description
:Enables/disables drawing the bullet tracers:
;Usage
:<code>cg_tracers [0|1|2]</code>
:0 No tracers.
:1 All tracers.
:2 All but your own tracers.
:Default: 1

=== cg_countryFlags  ===

;Description
:Show the GeoIP country flags
;Usage
:<code>cg_countryFlags [bitmask]</code>
:1 On scoreboard
:2 In crosshair names
:Default: 3

=== cg_gibs  ===

;Description
:Toggles the display of gib models.
;Usage
:<code>cg_gibs [0|1]</code>
:Default: 1

=== cg_followFT  ===

;Description
:Decides how players are picked up to be followed in spec.
;Usage
:<code>cg_followFT [0|1|2]</code>
:0 disables feature (works as usual then)
:1 follow Fire Team members first when in spec
:2 follow only Fire Team members when in spec.
:Options 1 and 2 work only when the player is in the Fire Team.
:When the player is not in FT then they do not infuence the spec behaviour.
:Default: 0

=== cg_showCountDown  ===

;Description
:Show last 3 secs warmup countdown.
;Usage
:<code>cg_showCountDown [0|1|]</code>
:0 Don't show countdown
:1 Show countdown
:Default: 1

=== cg_wbShowDuration  ===

;Description
:Display time of weapon banks in miliseconds (0 = off)
;Usage
:<code>cg_wbShowDuration [0-5000] in msecs</code>
:0 Don't show weapon banks
:1 to 5000 Other values up to 5000 show weapon banks display
:Default: 1000 (1 sec)

=== cg_wbOrientation  ===

;Description
:Orientation of weapon banks display.
;Usage
:<code>cg_wbOrientation [0|1]</code>
:0 horizontal
:1 vertical
:Default: 1 (vertical)

=== cg_wbWideSlots  ===

;Description
:Should wide slots be used for wide weapon icons.
;Usage
:<code>cg_wbWideSlots [0|1]</code>
:0 Don't use wide slots, use the same size for all weapons
:1 Use wide slots for wide weapon icons
:Default: 1

=== cg_landmineNotifyType  ===

;Description
:Decide which landmine reveal notifications player wants to receive.
:Server can send two types of landmines reveal notification.
:1 Standard one, generated (sent) for each landmine revealed.
:2 Summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.
;Usage
:<code>cg_landmineNotifyType [0|1|2]</code>
:0 only standard notfications (for each landmine revealed).
:1 only single summary notifications for one binocs zoom. New type of notification.
:For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is received. It contains information: 3 mines spotted by "player name" and last one was in location "some location"
:2 Don't receive any landmine notifications.
:Default: 0 (only standard notifications)

=== cg_tdmShow  ===

;Description
:Specify the way the Team Death Match (TDM) score is displayed.
:The TDM score can be displayed in two ways. It can be displayed all the time or it can be displayed when the +tdmScore command is issued in the console or the bound key to that command is pressed.
;Usage
:<code>cg_tdmShow [0|1]</code>
:0 Show only when the bound key is pressed.
:1 Show TDM score all the time.
:Default: 1 (show all the time)

=== cg_tdmTimeBar  ===

;Description
:Specify if the Team Death Match (TDM) time progress bar is to be shown below the TDM score. The TDM time progress bar is shown only when the Team Deatch Match has time limit specified.
;Usage
::0 Don't show time progress bar.
:1 Show TDM time progress bar.
:Default: 1

=== cg_locations  ===

;Description
:Specify the way the map locations are displayed (in Fire Team display for example).
;Usage
:<code>cg_locations [0|1|2]</code>
:0 Display only X,Y coordinates.
:1 Display only location name.
:2 Display X,Y coordinate and location name.
:Default: 1

=== ui_theme ===

;Description
:This cvar allows to switch between silEnT themes. silEnT themes is the UI feature that added new fresh feel to menus and some HUD elements. silEnT mod has 2 themes available to choose from.
;Usage
:<code>ui_theme [1|2]</code>
:1 Use the 1st theme to draw UI.
:2 Use the 2nd theme to draw UI.
:Default: 2

=== cg_themedCMap ===

;Description
:Specify the way the command map should be drawn (themed one or the standard one). Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the command map frame will be drawn differently.
;Usage
:<code>cg_themedCMap [0|1]</code>
:0 Don't use silEnT themes to draw command map frame.
:1 Draw command map with themed frame.
;Default 0

=== cg_themedDraws ===

;Description
:Specifies how draws (time, fps, timer, speedometer), K/D/S display and lagometer are drawn. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the elements mentioned above will be drawn differently.
;Usage
:<code>cg_themedDraws [0|1]</code>
:0 Don't use silEnT themes to draw draws, K/D/S and lagometer.
:1 Use silEnT themes to draw draws, K/D/S and lagometer.
;Default 1

=== ui_themedCursor ===

;Description
:Disables or enables themed mouse cursor. Corresponds to ui_theme cvar. Depending on the theme specified by the ui_theme cvar the mouse cursor will be different.
;Usage
:<code>ui_themedCursor [0|1]</code>
:0 Don't use silEnT themes to draw mouse cursor.
:1 Draw themed mouse cursor.
;Default 1

=== cg_hitSoundType ===

;Description
:Player selection of the hit sounds. Starting from silEnT mod 0.6.0, the players can choose what kind of hit sounds are played. If this cvar is set to 0, the hitsounds are determined by the server g_defaultHitSounds setting and possible overloaded hit sound files in custom pk3 files.
;Usage
:<code>cg_hitSoundType [0|1|2|3]</code>
:0 Use server defined hit sounds.
:1 Use strictly silEnT hit sounds.
:2 Use strictly ETPro hit sounds.
:3 Use strictly ETPub hit sounds.
;Default 0

=== cg_effectDistance ===

;Description
:Players can adjust what is the maximum distance that bullet effects are drawn. This can give slight performance improvement in maps with large open areas by not drawing effects to a distance player can't see them anyway. These effects include trails in the water, splashes, smoke pufs and different impact marks on the surfaces. This setting does not effect the sounds or the tracers.
;Usage
:<code>cg_effectDistance [integer]</code>
;Default 4000

=== cg_killsDisplay ===

;Description
:Defines the shown kill spree counter values.
:<code>cg_killsDisplay [0|1|2|3|4]</code>
:0 Disabled
:1 Show Total Kills and Total deaths
:2 Show Total Kills, Total Deaths and Sprees
:3 Show Total Sprees
:4 Total kills
;Default 0

=== cg_kspreepos ===

;Description
:Controls where the killing spree announcements are displayed.
:<code>cg_kspreepos [0|1|2|3|4]</code>
:0 Disabled
:1 Popup
:2 Chat area
:3 Banners
:4 Center Print
;Default 0

== Commands ==

=== Private Message ===

; Description
:Send private message to all players matching the partial name.
; Usage
:<code>'''m [partialname] [message]'''</code>

; Description
:Send private message to all players on your team that match the partial name.
; Usage
:<code>'''mt [partialname] [message]'''</code>

=== loadhud ===

; Description
:Used to load a custom hud from a .hud file contained in a pk3 file. Also able to "/loadhud ?" to show a list of available huds, "/loadhud blank" to load a blank hud, or "/loadhud" to load the default ET hud. When loading a hud, the default ET is loaded first, then the custom HUD overwrites any values specified. So if a HUD element isn't specifically disabled in a custom HUD, it will be in ET default position.

=== edithud ===

; Description
:Used to edit the hud in realtime. Can also be used to script a hud so that server admins don't have to package .hud files into pk3
; Usage

'''format:''' ''/edithud elementName [value1] [value2] . . . . [valueX]''

Current ''elementNames'' and ''(values)'' are as follows:

:*ammocount (x, y, scale)
:*chargebar (x, y, width)
:*compass (x, y, size)
:*upperright (y)
:*fireteam (x, y, width)
:*flagcov (x, y)
:*head (x, y, width, height)
:*healthbar (x, y, width)
:*healthtext (x, y, scale)
:*lagometer (x, y)
:*overheat (x, y, width, height)
:*skillbox1 (x, y, size)
:*skillbox2 (x, y, size)
:*skillbox3 (x, y, size)
:*skillpic1 (x, y, size)
:*skillpic2 (x, y, size)
:*skillpic3 (x, y, size)
:*skilltext1 (x, y, scale)
:*skilltext2 (x, y, scale)
:*skilltext3 (x, y, scale)
:*staminabar (x, y, width)
:*weaponcard (x, y, size)
:*xptext (x, y, scale)
:*cpmtext (x, y, scale)
:*chattext (x, y, scale)
:*votefttext (x, y)
:*livesleft (x, y)

All items except skilltextX are part of the original ET hud. skillTextX is a textual representation of the xp levels, i.e. 0, 1, 2, 3, 4. The skill[box,pic,text] elements correspond as follows, 1 = class specific skills, 2 = battle sense, 3 = light weapons

Default ''scale'' values, where used, is 25 in the default ET hud.

''upperright'' represents the spawn counter/game timer, clock, FPS normally displayed on the right side of the screen.

(x,y) are based on a 640 x 480 scale, regardless of the actual screen resolution that ET is running. Therefore (0,0) is upper left, (640,480) is lower right and (320, 240) is crosshairs

To disable an element entirely, set the first value to -1. Currently votefttext CANNOT be disabled

=== dumphud ===

; Description
:Dumps the current hud settings to the console in format used to create a .hud file

=== dropweapon ===

; Description
:Drops the player's primary weapon.

=== Shoutcast Login ===

;Description
:Logs the player into shoutcasting mode.
;Usage
:<code>sclogin [password]</code>
:<code>shoutcastlogin [password]</code>

=== Shoutcast Logout ===

;Description
:Removes the player's own shoutcaster status.
;Usage
:<code>sclogout</code>
:<code>shoutcastlogout</code>

=== timerset ===

;Description
:Sets enemy spawntimer (shown in red). You need to give the value for the timer. Not giving any value will disable the spawntimer.
;Usage
:<code>timerSet [1-60]</code>

=== resetTimer ===

;Description
:Resets the enemy spawn timer to the value which was given when timerSet was called. This command will do nothing if timerSet hasn't been called before.

=== lua_status ===

;Description
:Shows information about the scripts currently loaded by the Lua API engine.

=== silent_version ===

;Description
:Shows information about the running client and server version.

== Autoexec Files/Config ==

The silEnT client now has the ability to automatically execute certain config (*.cfg) files upon certain events:

Executed when you join a team (or become a spectator)

;'''autoexec_allies.cfg, autoexec_axis.cfg, autoexec_spectator.cfg'''
:

Executed when the map switches to <mapname>. autoexec_default.cfg is always executed after the autoexec_<mapname>.cfg file.

'''autoexec_<mapname>.cfg, autoexec_default.cfg'''

Executed when you switch classes

'''autoexec_soldier.cfg, autoexec_medic.cfg, autoexec_engineer.cfg, autoexec_fieldops.cfg, autoexec_covertops.cfg'''

'''''Note1: '''''If any of these files do not exist they simply will not be executed, there will not be any error messages.

'''''Note2''''': These filenames are casesensitive on linux.

Silent Shrubbot

2013-10-06T13:20:07Z

Silencerpl: /* g_countryFlags */

= What Is Shrubbot=
Shrubbot is an invention of Ryan Mannion. Shrubbot is an admin system that identifies the admin leveled players from PunkBuster GUIDs without the need for passwords. Shrubbot is also very flexible and allows creating many different admin levels with entirely different command sets. ETPub tries to clone shrubbot as accurately as possible, both in user interface and in the shrubbot configuration file called "shrubbot.cfg". silEnT shrubbot is based on the work of the ETPub team. silEnT extends the functionality of the shrubbot where ever it is needed. Including user database that holds all the players that have visited the server. To access this database, new commands have been added to the original shrubbot command set. Some commands have been renamed to ease their use and so that they resemble commands from other ET mods that have advanced admin systems.

If you want to use shrubbot, the cvar g_dbDirectory must be set. If it is not set, the shrubbot will not be in use. If you want to edit the default levels, you must create or copy existing shrubbot.cfg file to the folder defined by g_dbDirectory setting. In case shrubbot command like !ban is used against a player and shrubbot.cfg file does not already exist, a new shrubbot.cfg file is created to store the needed data.

The created file will also have the default level settings written to it. This file can be freely edited by hand and then after !readconfig command has been issued, the changes take effect on the server.

= Shrubbot Commands =

== !admintest ==

Prints out player's current shrubbot admin level in global chat. When the NAME or SLOT are added and the user has the right shrubbot permission, the level of another player will be shown. However, if the target has incognito shrubbot flag, then 0 level is displayed regardless who does !admintest on him/her.

'''Syntax:''' !admintest [NAME|SLOT]

'''Permission Flag:''' a

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !aliases ==

Prints out player's stored aliases. Aliases are printed in the last seen first order.If there are more stored aliases then fit in one page, optional page parameter can be used to access different pages. The number of stored aliases depends of the g_dbMaxAliases cvar.

'''Syntax:''' !alises [NAME|SLOT]

'''Permission Flag:''' e

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.6.0

== !ban ==

Kicks the player in slot number SLOT or with name containing NAME off the server and will not let them connect again for SECONDS seconds, or, if a modifier (m, h, d, or w) is used, a given amount of time. For example:

90 = 90 seconds

15m = 15 minutes

3h = 3 hours

5d = 5 days

1w = 1 week

'''Syntax:''' !ban (NAME|SLOT) (SECONDS|TIME_WITH_MODIFIER) REASON

'''Permission Flag:''' b

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !baninfo ==

Shows detailed information of a ban in the ban list. Find the ban number with !showbans command.

'''Syntax:''' !baninfo (BAN NUMBER)

'''Permission Flag:''' e

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.3.0

== !burn ==

Sets the player in slot number SLOT or with name containing NAME on fire. REASON will be center-printed to the victim.

'''Syntax:''' !burn (NAME|SLOT) [REASON]

'''Permission Flag:''' U

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !cancelvote ==

Makes a vote in progress fail.

'''Syntax:''' !cancelvote

'''Permission Flag:''' c

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !country ==

Displays the country of the player. This command works only if GeoIP is enabled on server [http://mygamingtalk.com/wiki/index.php/Silent_Mod_Server_Cvar#g_countryFlags g_countryFlags]

'''Syntax:''' !country

'''Permission Flag:''' i

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.8.0

== !crazygravity ==

Enables random g_gravity changes with 30 second interval. If enabled, the crazy gravity is automatically disabled at map end.

'''Syntax:''' !crazygravity (ON|OFF)

'''Permission Flag:''' C

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.6.2

== !crazyspeed ==

Enables random g_speed changes with 30 second interval. If enabled, the crazy speed is automatically disabled at map end.

'''Syntax:''' !crazyspeed (ON|OFF)

'''Permission Flag:''' C

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.6.2

== !dewarn ==

Shows all the warnings of a user. When warning number is used, the warning with that number will be removed.

'''Syntax:''' !dewarn (NAME|SLOT) [WARNING#]

'''Permission Flag:''' R

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !disorient ==

Turns the view upside down for the client in slot number SLOT or with name containing NAME. If REASON is specified it is printed to the client.

'''Syntax:''' !disorient (NAME|SLOT) [REASON]

'''Permission Flag:''' d

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !finger ==

Display the slot, partial guid, ip and clientversion of a player.

NOTE: This command should be available only to the highest server admins!

'''Syntax:''' !finger (NAME|SLOT)

'''Permission Flag:''' e

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !freeze ==

Freezes the client in slot number SLOT or with name containing NAME. If no parameter is provided it freezes all players. Frozen player(s) cannot receive damage during this time. If REASON is specified it is printed to the client.

'''Syntax:''' !freeze [NAME|SLOT] [REASON]

'''Permission Flag:''' F

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !gib ==

Kills and gibs the player in slot number SLOT or with name containing NAME. If name is -1 or all or if no name is entered, everybody will be gibbed.

'''Syntax:''' !gib (NAME|SLOT|-1|all)

'''Permission Flag:''' g

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !giba ==

Kills and gibs all players.

'''Syntax:''' !giba

'''Permission Flag:''' Q

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !help ==

Lists all the available shrubbot commands. If COMMAND is given, then prints the help of that specific command. !help is always available to all clients.

'''Syntax:''' !help [COMMAND]

'''Permission Flag:''' None

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !howfair ==

Prints a simple summary to everyone on the chat of team fairness based on player kill rating.

'''Syntax:''' !howfair

'''Permission Flag:''' I

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !kick ==

Kicks the player in slot number SLOT or with name containing NAME off of the server. REASON is given to the client as the drop message. The client will be banned for 2 minutes.

'''Syntax:''' !kick (NAME|SLOT) REASON

'''Permission Flag:''' k

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !levinfo ==

Lists all the details of the specific admin level. The listed information includes The name of the level, the greeting, the greeting sound path and the privilege flags for the level.

'''Syntax:''' !levinfo (Admin Level)

'''Permission Flag:''' s

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.5.2

== !levlist ==

Lists all the admin levels loaded from the shrubbot.cfg.

'''Syntax:''' !levlist

'''Permission Flag:''' s

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.5.2

== !list ==

Prints out a list of information about the connected players. The columns are:

* slot number

* team R=axis B=allies S=spectator C=connecting

* first letter of fireteam name

* admin level (and level name)

* last 8 digits of guid

* M if muted

* W if warned

* name

'''Syntax:''' !list

'''Permission Flag:''' i

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !listteams ==

Prints out a list of statistical information about each team. This lists ends with ratings information based on how likely each team is to win the current map. The team with more points is LESS likely to win, therefore a good way to balance the teams is to join the team with more points, or move people to that team, until the points are about even.

'''Syntax:''' !listteams

'''Permission Flag:''' I

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !lock ==

Locks the specified team. Recognized values are r=AXIS b=ALLIES s=SPECTATORS all=ALL.

'''Syntax:''' !lock (r|b|s|all)

'''Permission Flag:''' K

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !lol ==

Makes all players drop grenades. If NAME or SLOT is provided only that player will drop grenades. GRENADES is the number of grenades to be dropped (default is 1, maximum is 16).

'''Syntax:''' !lol [NAME|SLOT] [GRENADES]

'''Permission Flag:''' x

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !mute ==

Mutes a player in a slot number SLOT or with a name containing NAME. TIME and REASON are optional. See !ban for more information on modifiers

'''Syntax:''' !mute (NAME|SLOT) [SECONDS|TIME_WITH_MODIFIER] REASON

'''Permission Flag:''' m

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !news ==

Plays the map specific news audio to all players if it is available.

'''Syntax:''' !news

'''Permission Flag:''' W

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !nextmap ==

Moves to the next map in campaign or in the objective cycle end game intermission is skipped. With mapvoting gametype it is possible to go to the intermission if g_mapVoteFlags flag 16 is set.

'''Syntax:''' !nextmap

'''Permission Flag:''' n

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog'''
* 0.4.0 The !nextmap will go to the intermission map voting when the gametype is set to 7 and the g_mapVoteFlags bitmask has flag 16 set.

== !orient ==

Reverses the action of !disorient for the client in slot number SLOT or with name containing NAME.

'''Syntax:''' !orient (NAME|SLOT)

'''Permission Flag:''' d

'''Requires g_tryanny:''' Yes

'''Minimum required version:''' 0.2.0

== !panzerwar ==

Enables panzerwar game mode. All the players will have their main weapon changed to panzerfaust.

'''Syntax:''' !panzerwar [on|off]

'''Permission Flag:''' q

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !passvote ==

Makes a vote in progress pass.

'''Syntax:''' !passvote

'''Permission Flag:''' V

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !pause ==

Pauses the match.

'''Syntax:''' !pause

'''Permission Flag:''' Z

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !pip ==

Draws sparks (pixie dust) around the player in slot number SLOT or with name containing NAME. Does it to all players if NAME/SLOT is not providied.

'''Syntax:''' !pip [NAME|SLOT]

'''Permission Flag:''' z

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !pop ==

Pops the helmet off from a player in a slot number SLOT or with a name containing NAME. If no parameter is provided, it pops the helmets off from all the players.

'''Syntax:''' !pop [NAME|SLOT]

'''Permission Flag:''' z

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !putteam ==

Moves a player in a slot number SLOT or with a name containing NAME to the indicated team.

* r - Allies

* b - Axis

* s - Spectators

'''Syntax:''' !putteam (NAME|SLOT) (r|b|s)

'''Permission Flag:''' p

'''Requires g_tryanny:''' No

'''Minimum required version:''' 0.2.0

== !readconfig ==

Reads shrubbot.cfg file from the directory set by g_dbDirectory cvar.

'''Syntax:''' !readconfig

'''Permission Flag:''' G

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !rename ==

Sets the player in slot number SLOT or with name containing NAME to NEWNAME. The name change will not be persistent. The user database will store the renamed name for the player.

'''Syntax:''' !rename (NAME|SLOT) NEWNAME

'''Permission Flag:''' N

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !reset ==

Resets the match.

'''Syntax:''' !reset

'''Permission Flag:''' r

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !resetmyxp ==

Clears all XP and skillpoints for the player who runs this command.

'''Syntax:''' !resetmyxp

'''Permission Flag:''' M

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !resetxp ==

Clears all XP and skillpoints for the player in the slot number SLOT or with the name containing NAME. If reason is provided it is printed to the client.

'''Syntax:''' !resetxp (NAME|SLOT) [REASON]

'''Permission Flag:''' X

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !restart ==

Restarts the match.

'''Syntax:''' !restart

'''Permission Flag:''' r

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !riflewar ==

Enables riflewar game mode. All the players will have their main weapon changed to either K43 or Garand.

'''Syntax:''' !riflewar [on|off]

'''Permission Flag:''' q

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !rmsubnetban ==

Removes subnet ban. The given subnet ban number can be found using !subnets command.

'''Syntax:''' !rmsubnetban [ban number]

'''Permission Flag:''' .

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.4.0

== !setlevel ==

Sets the connected player in the slot number SLOT or with name containing NAME to the level indicated by LEVEL. A player cannot !setlevel another player to a lever higher than him/herself.

'''Syntax:''' !setlevel (NAME|SLOT) LEVEL

'''Permission Flag:''' s

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !showbans ==

Lists up to 30 shrubbot bans currently in effect. The columns are:

* ban number

* banned player's name

* date of the ban

* name of the banning admin

* when the ban will expire

* reason for the ban

If SKIP is provided, that number of bans are skipped before printing starts. SKIP can also be negative (e.g. '!showbans -10' would display the last 10 bans.

'''Syntax:''' !showbans [SKIP]

'''Permission Flag:''' B

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !shuffle ==

Shuffles teams, but does NOT restart (see !restart).

'''Syntax:''' !shuffle

'''Permission Flag:''' S

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !slap ==

Does DAMAGE (default 20) damage to player in slot SLOT or with name containing NAME. If REASON is specified it's center-printed to the victim.

'''Syntax:''' !slap (NAME|SLOT) [DAMAGE] [REASON]

'''Permission Flag:''' A

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !sniperwar ==

Enables sniperwar game mode. All the players will have their main weapon changed to sniper rifles.

'''Syntax:''' !sniperwar [on|off]

'''Permission Flag:''' q

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !spec999 ==

Moves all the players with a ping of 999 to the spectators team.

'''Syntax:''' !spec999

'''Permission Flag:''' P

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !spree ==

Show the players current killing spree count.

'''Syntax:''' !spree

'''Permission Flag:''' E

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !spreerecord ==

Displays the map and the overall spreerecord.

'''Syntax:''' !spreerecord

'''Permission Flag:''' E

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !stats ==

Displays the Thompson, MP40 and PPSh total kills and deaths, kills and deaths during the map and accuracy, headshotratio and headshot distance during the map. Lists all connected players.

'''Syntax:''' !stats

'''Permission Flag:''' t

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !subnets ==

This command displays all the issued subnet bans.

'''Syntax:''' !subnets (start at)

'''Permission Flag:''' B

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.4.0

== !subnetban ==

With this command admin can issue subnet ban. Subnet ban is a ban where the connecting player IP is matched against a larger IP range. The command accepts only subnets between range x.* - x.x.x.*. If the admin attempts to issue subnet ban that would ban himself the command refuses to add the subnet. This can be circumvented using rcon commands. If admin wants to add a subnet that would ban himself he must first whitelist himself with !userwl command. If silEnT can confirm the admin can connect the subnet ban is added. The command accepts full IP as it's parameter in which case the subnet is created to the x.x.x.* address. To remove subnet bans admin can use the !rmsubnetban command. The syntax with this commnd is the same kind with ban and userban commandand reason andtime can be given. The reason should be given so that any player connecting would know the reason for not being able to connect.

'''Syntax:''' !subnetban [subnet] (time) (reason)

'''Permission Flag:''' .

'''Require g_tyranny:''' No

'''Minimum required version:''' 0.4.0

'''Changelog:'''

0.6.2 - Octets can be cut from inside with 'x'. For example, "!subnetban 12x" will ban all IP addresses matching 12x.xxx.xxx.xxx.

== !swap ==

Swaps the players to the opposite team.

'''Syntax:''' !swap

'''Permission Flag:''' w

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !time ==

Prints out localtime of the client in the chat. No other client can see this time message. The command doesn't have a flag but it is available to all clients always.

'''Syntax:''' !time

'''Permission Flag:''' No permission required

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !throw ==

Send the player in slot number SLOT or with name containing NAME flying.

'''Syntax:''' !throw (NAME|SLOT)

'''Permission Flag:''' l

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !tspree ==

Show the top n current killing spree (default top 5).

'''Syntax:''' !tspree [amount]

'''Permission Flag:''' E

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !unban ==

Removes the ban that !showbans lists as BAN_NUMBER.

'''Syntax:''' !unban BAN_NUMBER

'''Permission Flag:''' b

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !unfreeze ==

Unfreezes the client in slot number SLOT or with name containing NAME. If no parameter is provided it unfreezes all players.

'''Syntax:''' !unfreeze [NAME|SLOT]

'''Permission Flag:''' F

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !unpause ==

Unpauses the match.

'''Syntax:''' !unpause

'''Permission Flag:''' Z

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !unmute ==

Unmutes the player in slot number SLOT or with name containing NAME.

'''Syntax:''' !unmute (NAME|SLOT)

'''Permission Flag:''' m

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !unlock ==

Unlocks the team specified. Recognized values are r=AXIS b=ALLIES s=SPECTATORS all=ALL.

'''Syntax:''' !unlock (r|b|s|all)

'''Permission Flag:''' K

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !uptime ==

Show how long the server has been up and running.

'''Syntax:''' !uptime

'''Permission Flag:''' u

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !fling ==

Send the player in slot number SLOT or with name containing NAME flying.

'''Syntax:''' !fling (NAME|SLOT)

'''Permission Flag:''' l

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !launch==

Send the player in slot number SLOT or with name containing NAME flying.

'''Syntax:''' !launch(NAME|SLOT)

'''Permission Flag:''' l

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !throwa ==

Sends all players flying.

'''Syntax:''' !throwa

'''Permission Flag:''' L

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !flinga==

Sends all players flying.

'''Syntax:''' !flinga

'''Permission Flag:''' L

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !launcha==

Sends all players flying.

'''Syntax:''' !launcha

'''Permission Flag:''' L

'''Requires g_tyranny:''' Yes

'''Minimum required version:''' 0.2.0

== !warn ==

Plays the whistle sound and center-prints WARNING to the player in slot number SLOT or with name containing NAME.

'''Syntax:''' !warn (NAME|SLOT) [WARNING]

'''Permission Flag:''' R

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

= User Database =

User database is intended to store information of all the players that connect to the server. To enable user database g_dbDirectory must be set. The database stores information to identify different players and also XP data, rating data, overall stats data and shrubbot admin data. PunkBuster GUIDs are used to identify single players. If a player joining the server doesn't have a PB GUID, data about that player can not be saved. However, the user database can still be used to store data of those players who have enabled punkbuster on the client side.

Shrubbot includes functionality for server admins to handle database userdata. All commands that handle users in the database will take the last 8 characters of the player PunkBuster GUID to identify the player to edit. This is not an unique identification but because EvenBalance has seen this to have enough uniqueness, it is good for the use of the database commands. Internally, the full GUID is used to identify the players.

= User Database Commands =

== !aliasesdel ==

Command removes all the aliases from the player identified by the 8 character silEnT ID.

'''Syntax:''' !aliasesdel [silEnT ID]

'''Permission Flag:''' [

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.6.0

== !aliassearch ==

This command searches the whole aliases database for the pattern in the names. Note, this command is the most resource intensive shrubbot command of all commands, and it is not recommended to be used without a reason. How fast it performs in practice depends of the aliases database size.

For each player the following information is shown:

:* identity information (silEnT ID)

:* each used alias that fits the search pattern

:* for each alias when it was first seen

:* for each alias when it was last seen

:* for each alias the total playtime with it

To see all the aliases of the found player, you can use "!userinfo aliases" command. In the case of all the data not fitting in one page, you can give an optional start parameter. The start parameter corresponds to the numbers shown in the first column of the results. So that each player has its own number and under that number, all the matching aliases from that player are printed.

'''Syntax:''' !aliassearch [name] [start]

'''Permission Flag:''' ]

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.6.0

== !confirm ==

Confirms the player identity with a protected admin level. As a result, the confirmed player and the server will transfer authentication information allowing the player to use admin commands from thereafter. Unconfirmed players are players with admin level that is protected but the server can not ensure the identity. This usually happens when players admin level changes with offlinecommands or the protected levels are extended. This command does not give the player admin levels, it only confirms the identity of a player whos admin level is already set. Also, if the player loses his admin level identification, this command can not be used to reinstate it.

This command is safe to be given even to the lower levels of admins.

'''Syntax:''' !confirm [SLOT]

'''Permission Flag:''' :

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.5.0

== !userlist ==

Lists all users in the database. If PAGE is given, the list starts from that page. If PAGE is not given the first page of the database is printed. The command prints all users, including clients that have connected during the level time and are not yet in the database. The connected clients are always printed first and then the rest of the userbase.

The printed rows have the following columns:
:*'#' ; This is the serial number of the user in the printout. The number doesn't correspond to anything in the database.

:*'silEnT ID' ; This is the 8 character silEnT GUID of the player. This is used to identify different players in the database.

:*'PBGUID' ; This is the 8 character PB GUID of the user. This is used to identify different users in the database.

:*'Last Seen' ; This tells how long time ago the user was last seen on the server. For connected clients, this will print "connected".

:*'IP' ; This tells the last IP address user has had on the server.

:*'Ban' ; This is the ban number if the player is banned from the server. If the player is whitelisted from IP bans, this column reads white capital W.

:*'Name' ; This tells the last name with user has been saved on the server.

With userlist command an admin can list all the users saved in the database and those that are connected page by page. Optional page number can be given to the command to tell which page is to be displayed about the users. One page can have up to 20 players printed.

'''Syntax:''' !userlist [PAGE]

'''Permission Flag:''' ]

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:* 0.4.0 - New column 'Ban' is added to the output.

:* 0.5.0 - New column 'silEnT ID' is added to the output.

== !userinfo ==

Displays all information that is stored about the user in the database.

This information includes:

:*identity information (name, IP, 8 character PunkBuster GUID, silEnT ID, Client Identification)

:*admin level

:*personal greeting

:*personal greeting sound

:*personal shrubbot flags

:*saved XP per skill

:*rating values

:*total kills and deaths with SMG weapons

:*the ban number of the player or whitelisting

:*list of stored aliases if the aliases database is enabled on the server

Command can optionally print player's stored aliases if the optional aliases parameter is given and the aliases database is enabled by setting g_dbMaxAliases to a positive integer. If printed aliases don't fit in one page, optional page parameter can be used to access different pages.

Command requires the last 8 characters of the player silEnT GUID. This GUID can be found with !userlist or !usersearch commands. This command works for both online and offline players.

'''Syntax:''' !userinfo [silEnT ID] [aliases [page]]

'''Permission Flag:''' ]

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:0.4.0 - Information of possible ban and whitelisting is added.

:0.5.0 - silEnT ID is added.

:0.6.0 - Aliases option is added.

== !useredit ==

Command is used to edit explicit userdata in the database. The command format is:

!useredit [silEnT ID] [add|remove|level|greeting|sound] [new value]

The command parameters in detail:

:*silEnT ID - This is the last 8 characters of the silEnT GUID of the player. This is needed to identify the player to edit.

:*add - If the command is given this parameter, the value(s) in the [new value] field will be added to the player's personal flags.

:*remove - If the command is given this parameter, the value(s) in the [new value] field will be removed from the player's personal flags.

:*level - If the command is given this parameter, the value in the [new value] field will be set as the players new level. The level may not be higher then the level of the player executing the command.

:*greeting - If the command is given this parameter, the value in the [new value] field will be the players new personal greeting. If the [new value] field is empty, the personal greeting is cleared.

:*sound - If the command is given this parameter, the value in the [new value] field will be the file path to the players new personal greeting sound. If the [new value] field is empty, the personal greeting sound is cleared.

:*new value - This field is used to give values to the command.

If the optional new value field is not set with greeting or sound parameter, the value will be set to empty and level values will be used again with these players.

This command works with online and offline players.

'''Syntax:''' !useredit [silEnT ID] [add|remove|level|greeting|sound] [new value]

'''Permission Flag:''' [

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:* 0.5.0 - The command now uses the silEnT GUID instead of the PB GUID. The backward compatible version of the command is named !usereditpb.

== !givexp==

Command gives the online or offline player identified by PBGUID a defined amount of XP points to the selected skill.

'''Syntax:''' !givexp [silEnT ID] [sold|med|eng|fops|cov|light|battle] [amount to add]

'''Permission Flag:''' [

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:* 0.5.0 - The command now uses the last 8 characters of the silEnT GUID instead of the PB GUID. The backward compatible version of the command is named !givexppb.

== !userban ==

Command bans user indentified by the 8 character silEnT GUID from the server. The data required for ban is taken from the database and the banned user does not need to be online when the command is given. Bot's cannot be banned with this command. Note that the bans are written in the human readable config file and you can still write the bans by hand if desired. Also, removing of the bans can be done by hand if desired.

'''Syntax:''' !userban [silEnT ID] [time] [reason]

'''Permission Flag:''' ]

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:* 0.5.0 - The command now uses the last 8 characters of the silEnT GUID instead of the PB GUID. The backward compatible version of the command is named !userbanpb.

== !userwl ==

With this command admin can whitelist or remove whitelisting from any player. Whitelisting means that the player IP is not checked against any IP bans. Including subnet bans and individual bans.

'''Syntax:''' !userwl [silEnT GUID] [add|remove]

'''Permission Flag:''' .

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.4.0

== !userdelete ==

Command removes the user identified by the 8 character silEnT GUID from the database. The actual actions are taken at the level end if needed. However, once the !userdelete command has been issued to the user, the information of the user is no longer available and after the shutdown game, it is permanently lost.

If the removed player is connected to the server while removing, a new entry is written to that player.

'''Syntax:''' !userdelete [silEnT ID]

'''Permission Flag:''' [

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

'''Changelog:'''

:* 0.5.0 - The command now uses the last 8 characters of the silEnT GUID instead of the PB GUID. The backward compatible version of the command is named !userdeletepb.

== !usersearch ==

With this command an admin can search the database for players with specific parameters. Arguments to the command can be pattern in the name, user admin system level and the beginning of the IP address. Additional page number can be given when the amount of found results exceed what can be shown in one page. All the arguments can be given in one command in any order. Any one of the arguments can be omitted, but each time when command is given at least one argument on top of the optional page number must be given. This command searches stored information only from the database. Connected players are not included unless they are already stored into the database.

This command can be performance intensive and it is not recommended to use it only for maintenance operations. The command will internally always try to optimise itself. If the command is given repeatedly with same arguments but only changing the page number, new searches are not performed but only different pages of the already found results are displayed. The optimisations include that the silEnT will try to use the already found results as the basis for the new search (e.g. "!usersearch name gao" followed by "!usersearch name gaoe" will first search the whole db to find all users with the pattern gao in their names and the follow up search will refine the already found results for gaoe). The maximum amount of results one search can return is 256 users. Users are displayed in the console in pages with 20 users on each page.

'''Syntax:''' !usersearch [name (name)]|&[level (level)]|&[IP (IP)] [page]

'''Permission Flag:''' ]

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.2.0

== !updatepbguid ==

Updates the PB GUID that is stored in the database to the one which the player is currently using. With the exception that empty, invalid or dublicated PB GUIDs are not saved to the database.

'''Syntax:''' !updatepbguid [Name|Slot]

'''Permission Flag:''' ,

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.5.2

== !readadmins ==

With this command an admin can read admin definitions from a specific admins.cfg file. The file must be placed in the directory pointed by g_dbDirectory server cvar. The file may have only admin definition blocks.
Admin definitions use always the following syntax. The syntax is exactly the same used by the ETPub.

[admin]

name = name of the admin (can be left empty)

sguid = full 32 character silEnT GUID (this field is used to identify players in the database)

guid = full 32 character PB GUID (this field is used to identify players in the database)

level = level number

flags = personal admin flags (can be left empty)

greeting = personal greeting (can be left empty)

greeting_sound = path to personal greeting sound (can be left empty)

If the database doesn't yet have the player, it will be added there. Those players will have the last seen field reading NEVER with !userlist and !usersearch command outputs. If the player already exists in the database, the admin values will be overwritten with the ones in read from the admins.cfg file.

'''Syntax:''' !readadmins

'''Permission Flag:''' )

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.3.0

'''Change Log:'''

:* Starting from silEnT 0.5.0, the field sguid was added to the admin blocks. This allows adding admins using the silEnT GUIDs to identify them.

:* In versions between 0.5.0 and 0.5.2 this command was partially broken. The command is fixed from the version 0.6.0 onwards.

== !resetpls ==

With this command an admin can reset all stored statistics from an online or an offline player. The stored statistics include total SMG kills and deaths, the player K/D rating and PRW rating.

'''Syntax:''' !resetpls [silEnT ID]

'''Permission Flag:''' (

'''Requires g_tyranny:''' No

'''Minimum required version:''' 0.3.0

'''Changelog:'''

:* 0.5.0 - the command was changed to use silEnT ID instead of the last 8 characters of the PB GUID. There is no backward compatible command for PB GUIDs.

= List of Permission Flags =

'''Flags to privileges'''

:1 - Cannot be vote kicked, vote muted, or complained against.
:2 - Cannot be censored.
:3 - Can run commands silently with /!COMMAND in the console.
:4 - Can see Axis/Allies team chats as a spectator.
:5 - Can switch teams any time, regardless of balance.
:6 - Does not need to specify a reason for !mute, !kick or !ban.
:7 - Can call a vote at any time (regardless of disabled voting or voting limitations).
:8 - Does not need to specify a duration for a ban (defaults to PERMANENT).
:9 - Can do shrubbot commands via team and fireteam chats.
:0 - Is immune to g_inactivity and g_spectatorInactivity settings.
:! - Is immune to all shrubbot commands (useful for server admins). Note, this flag must be specified explicitly the * flag does not grant it.
:@ - "incognito" flag shows the admin as level 0 with no a.k.a info in the output of !listplayers. Note, this flag must be specified explicitly the * flag does not grant it.
:$ - Can do !admintest on other players.
:~ - Can read and write the adminchat with the /ma command. All referees and all other players with the ~ flag will be able to read this chat.
:& - Can rename himself regardless of g_maxNameChanges limit.
:? - Can see all private messages while being in spectators. g_tyranny must be set for this flag to take effect.
:/ - Cannot send private messages. Otherwise normal privileges.
: # - Cannot call votes.
: : - Can confirm admin identity.

'''Flags to commands'''

:A - !slap
:a - !admintest
:B - !showbans, !subnets
:b - !ban, !unban
:C - !crazygravity, !crazyspeed
:c - !cancelvote
:d - !disorient, !orient
:E - !spree, !spreerecord, !tspree
:e - !baninfo, !finger, !aliases
:F - !freeze, !unfreeze
:G - !readconfig
:g - !gib
:I - !howfair, !listteams
:i - !list
:K - !lock, !unlock
:k - !kick
:L - !flinga, !launcha, !throwa
:l - !fling, !launch, !throw
:M - !resetmyxp
:m - !mute, !unmute
:N - !rename
:n - !nextmap
:P - !spec999
:p - !putteam
:R - !warn, !dewarn
:r - !reset, !restart
:S - !shuffle
:s - !setlevel, !levlist, !levinfo
:t - !stats
:U - !burn
:u - !uptime
:Q - !giba
:q - !panzerwar, !riflewar, !sniperwar
:V - !passvote
:W - !news
:w - !swap
:X - !resetxp
:x - !lol
:Z - !pause, !unpause
:z - !pip, !pop
:] - !userlist, !userinfo, !userban, !usersearch, !aliassearch
:[ - !useredit, !givexp, !userdelete, !aliasesdel
:) - !readadmins
:( - !resetpls
:. - !userwl, !rmsubnetban, !subnetban
:, - !updatepbguid

= Shrubbot Files =

To use shrubbot the g_dbDirectory must be set. All the shrubbot files are placed into that directory.

== shrubbot.cfg ==

Shrubbot.cfg is the file that holds all the level definitions, custom commands, bans, warns and subnetbans for the server shrubbot. These configuration settings are hand editable. If the shrubbot.cfg file does not exists when !ban or!setlevel is used, a new one with default settings is created. The settings in the shrubbot.cfg are divided into following data blocks.

'''[level]'''

level = The level number.

name = The nameof the level used in e.g. !list command.

flags = The permission flags for the level.

greeting = The greetingtext that is displayed to every player joining the server with this level.

greeting_sound = The greeting sound played for every playerjoining the server with this level.

'''[command]'''

command = The name of the command.

exec = The executed command. These must be commands available to /rcon and these will be executed with rcon privileges.

desc = The help description of the cmmand.

levels = Space separated list of levels this command is allowed.

* The exec field in the command block can use all the shortcuts that silEnT support. The shortcut is substituted as the command would have been a say from the player who issued the command. In addition to normal shortcuts, it is possible to use [i] which is replaced with the client number of the player who did the command.
* The exec field in the command block can additionally use parameter placeholders. These are [1] - [9] where the number is the n:th parameter given to the custom command. When these are used, the server will substitute the placeholder with the n:th parameter given to the command.
* Starting from silEnT 0.2.1, it is possible to add '?' to the parameter placeholders. This will make the server substitute the given string to a player name if only one player matches the string. For example:

[command]

command = crybaby

exec = playsound path/to/sound.wav; chat ^7[1?]^7 is crying like a little baby!

desc = Make someone cry

levels = 0 1 2 3 4 5

'''[ban]'''

name = The name of the banned player.

guid = The PunkBuster GUID of the banned player.

sguid = The silEnT GUID if the banned player.

ip = The IP address of the banned player.

reason = The reason for the ban.

made = The time and date when the ban was issued.

expires = When the ban will expire.

banner = The name of the admin who banned the player.

ident = The silEnT ident if available.

'''[subnetban]'''

subnet = The subnet of the ban.

reason = The reason for the ban.

made = The time and date when the subnet ban was created.

expires = When the ban will expire.

banner = The name of the admin who created the ban.

'''[warning]'''

name = The name of the warned player.

guid = The silEnT GUID of the warned player.

ip = The IP addressof the warned player.

warning = The reason of the warning.

made = The time when the warning was made.

warner = The name of the player who warned.

== userdb.db ==

This is a file where the silEnT stores information of the players. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify this file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be always stored at the g_dbDirectory location with a _vxx added to it's name.

If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.

== userxdb.db ==

This is a file where the silEnT stores information of the players which is not needed for the most players. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify this file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be always stored at the g_dbDirectory location with a _vxx added to it's name.

If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.

== useradb.db ==

Starting from silEnT 0.6.0, this file holds the optional aliases database. To enable the database, g_dbMaxAliases cvar must be set to a positive integer. The aliases database can be disabled by setting g_dbMaxAliases to 0 value at any time and then re-enable the database by setting the value back to a positive integer without any effect to the file. However, if the g_dbMaxAliases cvar is set to a smaller value then it was before, the aliases that exceed the threshold will be lost unrecoverably.

This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify this file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be always stored at the g_dbDirectory location with a _vxx added to it's name.

If silEnT finds this file to be corrupted or unusable, it will not overwrite it. The error messages in the log are usually very descriptive about the erros.

= Shrubbot Limitations =

'''Maximum number of levels:''' 31

'''Maximum length of shrubbot level name:''' 35 (includes color codes)

'''Maximum number of players in the database:''' Unlimited

'''Maximum number of player bans:''' 1023

'''Maximum number of subnet bans:''' 128

'''Maximum length of ban reason:''' 1023

'''Maximum number of admin-defined commands:''' 63

'''Maximum admin-defined command name length:''' 63 characters

'''Maximum admin-defined command length (executable part):''' 1023 characters

'''Maximum admin-defined command length (help string):''' 1023 characters

'''Maximum number of warnings:''' 1023

Silent Mod Server Cvar

2013-10-06T10:32:28Z

Silencerpl: g_muteRename added

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

;Parameters
: Type: bitmask
:1 Show player AntiCheat status in the !finger output.
:2 Automatically ban players with cheats.
: Default: '''0'''

= Announcements and Messages =

== g_privateMessages ==

;Description
If set to 1, players can send private messages to one another with the /m playername/slot command.
;Parameter
: Type: '''[0|1]'''

:0 Disable Private Messages
:1 Enable Private messages

:Default: '''0'''

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_recognition ==

'''Description:'''

Enables additional recognition notifications for players doing objective, e.g. for planting dynamite, disarming it, destroying objective.

'''Type:''' [0|1]

'''Parameters:'''

0 Additional recognition notifications disabled.

1 Additional recognition notifications enabled.

'''Default:''' 1

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

== g_muteRename ==

'''Description:'''

If this cvar is set to 1 the muted player won't be allowed to change his name while he is muted.
Minimium required version: silEnT 0.8.0

'''Type:''' integer

'''Default:''' 0

'''Parameters:'''

0 Disabled. Allow players to change his/her name while he/she is muted. 

1 Don't allow player to change his/her name while he/she is muted. 

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points. Kill rating also takes into account the weapon used (less for arty, more for knife).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 16 The !nextmap command and a passed nextmap vote will start the intermission and lets players vote which map should be played next. NOTE: this makes the game end as a tie. 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class. So far, only PPSH enablement is implemented.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Server Cvar

2013-10-06T10:23:41Z

Silencerpl: g_recognition

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

;Parameters
: Type: bitmask
:1 Show player AntiCheat status in the !finger output.
:2 Automatically ban players with cheats.
: Default: '''0'''

= Announcements and Messages =

== g_privateMessages ==

;Description
If set to 1, players can send private messages to one another with the /m playername/slot command.
;Parameter
: Type: '''[0|1]'''

:0 Disable Private Messages
:1 Enable Private messages

:Default: '''0'''

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_recognition ==

'''Description:'''

Enables additional recognition notifications for players doing objective, e.g. for planting dynamite, disarming it, destroying objective.

'''Type:''' [0|1]

'''Parameters:'''

0 Additional recognition notifications disabled.

1 Additional recognition notifications enabled.

'''Default:''' 1

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points. Kill rating also takes into account the weapon used (less for arty, more for knife).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 16 The !nextmap command and a passed nextmap vote will start the intermission and lets players vote which map should be played next. NOTE: this makes the game end as a tie. 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class. So far, only PPSH enablement is implemented.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Server Cvar

2013-10-06T10:17:19Z

Silencerpl: /* g_enableDemolition */

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

;Parameters
: Type: bitmask
:1 Show player AntiCheat status in the !finger output.
:2 Automatically ban players with cheats.
: Default: '''0'''

= Announcements and Messages =

== g_privateMessages ==

;Description
If set to 1, players can send private messages to one another with the /m playername/slot command.
;Parameter
: Type: '''[0|1]'''

:0 Disable Private Messages
:1 Enable Private messages

:Default: '''0'''

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points. Kill rating also takes into account the weapon used (less for arty, more for knife).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 16 The !nextmap command and a passed nextmap vote will start the intermission and lets players vote which map should be played next. NOTE: this makes the game end as a tie. 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class. So far, only PPSH enablement is implemented.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Enable Improvised Demolition weapon for soldier class.
Improvised Demolition weapon was introduced in 0.8.0 version of the silEnT mod.
As mentioned in the original WWII Tank-destruction manual, a big charge could be made of 6 stickgrenade heads around one complete grenade, fixed with wire or rope.
The central grenade would make the other 6 grenade detonate as well causing an explosion which could damage the light armoured vehicles.

In silEnT mod this weapon is designed to suit exactly the purpose described above.
To gain the weapon player has to gain 3rd engineer level and 4th soldier level.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Server Cvar

2013-10-06T10:15:07Z

Silencerpl: added g_enableDemolition

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

;Parameters
: Type: bitmask
:1 Show player AntiCheat status in the !finger output.
:2 Automatically ban players with cheats.
: Default: '''0'''

= Announcements and Messages =

== g_privateMessages ==

;Description
If set to 1, players can send private messages to one another with the /m playername/slot command.
;Parameter
: Type: '''[0|1]'''

:0 Disable Private Messages
:1 Enable Private messages

:Default: '''0'''

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points. Kill rating also takes into account the weapon used (less for arty, more for knife).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 16 The !nextmap command and a passed nextmap vote will start the intermission and lets players vote which map should be played next. NOTE: this makes the game end as a tie. 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class. So far, only PPSH enablement is implemented.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== g_enableDemolition ==

'''Description:'''

Disables/enables Improvised Demolition. Improvised Demolition is available only for soldier class.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""

Silent Mod Server Cvar

2013-10-06T10:12:35Z

Silencerpl: added g_dmgDemolition and g_dmgDemolitionRadius

= silEnT Mod Anti Cheat =

== g_silentac ==

;Description
Enables actions based on silEnT AntiCheat. The g_cheatLog will always have one line telling if a player is found with cheats. The cheat detection's are based mostly on heuristically detecting hacking techniques. If you suspect a false positive, please supply the silEnT team a method to reproduce it. Do note that this feature has been in extensive testing well before the 0.8.0 version. When silEnT AC is set to autoban, sv_sac cvar is set to 1. This cvar can be used by external server trackers to enable/disable server anti cheat status on their lists. We recommend setting the value to 2.

;Parameters
: Type: bitmask
:1 Show player AntiCheat status in the !finger output.
:2 Automatically ban players with cheats.
: Default: '''0'''

= Announcements and Messages =

== g_privateMessages ==

;Description
If set to 1, players can send private messages to one another with the /m playername/slot command.
;Parameter
: Type: '''[0|1]'''

:0 Disable Private Messages
:1 Enable Private messages

:Default: '''0'''

'''Note:''' Clients can reject private message from other individual clients with the /ignore client command. Also, private messages can be disabled from individuals/levels using shrubbot flag '/'.

== g_spreeOptions ==

'''Description:''' 

Options to control the display of killingsprees.

'''Type''': bitmask

'''Parameters:'''

1 Enable killingsprees

2 Enable killingspree ends

4 Enable multikills

8 When set, a top 3 current killing sprees message will be printed every minute, similar to binoc masters, and a map's longest killing spree will be printed every two minutes

16 At the beginning of the intermission the highest spree and the 3 highest sprees which are still active will be shown

32 /kill will end a spree

64 Teamswitching will end a spree

128 Multikill messages will be delayed g_multikillTime milliseconds, to prevent the doublekill -> multikill -> megakill -> etc. flooding

256 Killing bots doesn't count for multikills or killingsprees (Note: they DO count for ending kill/deathsprees)

512 Display the map and overall spree record when entering intmission

1024 Summary: don't enable this flag if you don't have enabled g_spreeOptions flag 512 OR g_XPSave flag 16 or Shrubbot flag t

Spree records are automatically saved into XPSave file when a map ends. By enabling this flag, you also store the spreerecord at the points where g_XPSave flag 16 would store XP. When you don't have set XPSave flag 16 and g_spreeOptions flag 512 and not allow users to use !spreerecord you should NOT set this flag as it takes some extra resources. When XPSave flag 16 is set this doesn't matter (it actually takes much less resources then). When only g_spreeOptions flag 512 or shrubbot flag t is set it won't do much harm anyway (your server won't explode)

2048 Enable revivesprees

'''Default''': 0

== g_multikillTime ==

'''Description''' 

The time (in milliseconds) in which two kills should be made in order to count them as multikills. 

'''Type:''' integer '''Default:''' 1000

== g_obituary ==

'''Description:''' 

This cvar controls will the server send obituary events to the clients. If this is set to 0, no obituary events will be sent. If set to any nonzero value, obituary events will be sent.

'''Type:''' [0|1]

'''Default:''' 1

== g_dropMsg ==

'''Description:''' 

Message to add to the drop screen when a client is kicked or banned.  

'''Type:''' String 

'''Default:''' " "

'''Example:''' g_dropMsg "Please protest ban on forums"

== g_landmineNotifyType ==

'''Description:'''

Decide which landmine reveal notifications server should send. 

Server can send two types of landmines reveal notification. Standard one, generated (sent) for each landmine revealed and summary one, which is sent after player spotting landmines stops using binoculars. It's generated after each binculars zoom.

'''Type:''' [0|1|2|3] 

'''Parameters:'''

0 Only standard notfications (for each landmine revealed).

1 Only single summary notifications for one binocs zoom. New type of notification. For example: during one binocs zoom, 3 mines were revealed, but only 1 summary notification is sent. It contains information: 3 mines spotted by "player name" and last one was in location "some location".

2 Don't send any landmine notifications.

3 Send all notifications. For example: for 3 spotted landmines send 4 notifications (3 for each landmine + 1 summary notification).

'''Default:''' 3

'''Recommended:''' 1

== g_banners ==

'''Description:''' 

This should be set to the name of your banners.cfg file if you want to enable banners. See settings documentation for more information about this file. 

'''Type:''' string

'''Default:''' ""

'''Example:''' set g_banners "banners.cfg" 

'''Minimum required version:''' 0.4.0

== g_defaultHitSounds ==

'''Description:'''

Selects the default hit sounds on the server. Starting from silEnT 0.6.0, it is possible for the players to choose what kind of hit sounds are played. If the client cvar cg_hitSoundType is 0, the g_defaultHitSounds determines what type of hit sounds are used. Also, if the client cvar cg_hitSoundType is 0, the server may also add custom hit sound files in a custom pk3 file. These sounds are automatically loaded if available. However, if the client cvar cg_hitSoundType is 1, 2 or 3, the client will use strictly the hit sounds they have selected. Custom hit sounds are placed to the root folder "sounds/hitsounds" in the custom pk3. They must never overload any of the files in the subfolders, silent, etpro or etpub.

'''Type:''' [0|1|2|3]

'''Parameters:'''

0 No selection, will default to silEnT in the client end.

1 Defaults silEnT hitsounds.

2 Defaults ETPro hitsounds.

3 Defaults ETPub hitsounds.

'''Default:''' 1

'''Minimum required version:''' 0.6.0

= User Database, XP Save, Shrubbot and Bans =

== g_dbDirectory ==

'''Description:'''

If set the server stores various information about server statistics, map information, sprees, users, bans and XP save. To use any of the functionalities, this must be set. The cvar defines a directory and only a directory that is relative to fs_game. All the used filenames are predefined and cannot be changed. For security reasons, this cvar must be set during server initialisation. (i.e. It may not be changed when the server is running.) In this directory there can be 5 files, depending of other server settings.

* userdb.db is a binary format file that contain all the required information about shrubbot users and also all saved XP if the server is set to save XP
* userxdb.db is a binary format file that contain related to players playing on the server
* serverstat.cfg is a human readable file that contain server statistics and map sprees if the server is set to store them
* shrubbot.cfg is a human readable file that contain level configurations, custom commands and bans
* mapvoteinfo.cfg This file contains information relating g_gametype 6, which is map voting.

All the required files will be created automatically to the folder when needed if there aren't any suitable files already present.

You can freely edit the human readable files by hand as long as their correct format remains and the server is notified of the changes using appropriate shrubbot commands. With the exceptions of serverstat.cfg and mapvoteinfo.cfg that will be overwritten by the server. If you want to hand edit the values of these files, the server be shutdown.

'''Type:''' string

'''Default:''' "database"

'''Note:'''

The server reads the value of this cvar only from the config file or from the command line. It cannot be edited using RCON. If you want to store all the files in the same root directory where all the pk3 files and binaries are, you can set this cvar to value ".". It will then use the fs_game directory.

== g_dbUserMaxAge ==

'''Description:'''

The number of seconds that player is saved to the database since the player has last visited on the server.

The database cleaning is done during intermission so this should not cause any performance problems when actions are taken. However, by setting this value to 0 or not setting the value at all, will disable the feature.
For servers with high database sizes, this can improve performance since users that are not needed will be removed automatically.

You can use a modifiers with this value. Here are some examples:

set g_dbUserMaxAge "1o" - 1 month

set g_dbUserMaxAge "2w" - 2 weeks

set g_dbUserMaxAge "5d" - 5 days

set g_dbUserMaxAge "36h" - 36 hours

set g_dbUserMaxAge "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 0

'''Note:'''

The server reads the value of this cvar only from the config file executed before the mod launches the first time or from the command line. It cannot be edited using RCON.

== g_dbMaxAliases ==

'''Description:'''

The silEnT mod can store player aliases in an additional database. To enable this database, set this value to higher then 0. If this value is a positive integer, it defines how many aliases are stored in the database for one player. If the player has more aliases then this value, the oldest aliases are deleted.

'''Type:''' integer

'''Default:''' 0

'''Minumum required version:''' 0.6.0

'''Note:'''

This cvar can be set only at startup, before the mod launches. It cannot be changed on a live server using rcon.

== g_XPSave ==

'''Description:'''

Controls XP save behaviours.

'''Type:''' bitmask

'''Parameters:'''

1 Store xp when a client disconnects. This is always required for the XP save to work.

2 Don't reset xp to the pre-map start values on a map restart, shuffle, etc.

4 Never reset xp (ever).

8 Force the disconnection of clients with the same GUID as the connecting client. This is useful in saving the stored XP of players with unreliable network connections since they should still get their stored XP even if reconnecting immediately with a new IP address.
This feature is enabled by default unless you have sv_wwwDlDisconnected enabled. sv_wwwDlDisconnected seems to interfere with this feature, so do not enable this flag if you change pk3's on your server often because stored XP will be lost over disconnected downloads.

16 Store the XP at restarts, nextmaps, mapvotes, campaignvotes and similar cases.

'''Default:''' 0

== g_XPSaveMaxAge_xp ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her xp skills. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier with this value. Here are some examples:

set g_XPSaveMaxAge_xp "1o" - 1 month

set g_XPSaveMaxAge_xp "2w" - 2 weeks

set g_XPSaveMaxAge_xp "5d" - 5 days

set g_XPSaveMaxAge_xp "36h" - 36 hours

set g_XPSaveMaxAge_xp "120m" - 120 minutes

'''Type:''' integer

'''Default:''' 1d

'''Note:''' If g_XPSaveMaxAge is less than g_XPSaveMaxAge_xp, g_XPSaveMaxAge will be used.

== g_XPSaveMaxAge ==

'''Description:'''

The number of seconds that must pass without saving XP from this player before XPSave forgets his/her skills/killrating/playerrating/mute status. Admins can adjust the amount of required XP to save with g_XPSaveMinXP server cvar.

You can use a modifier for this value. Here are some examples:

set g_XPSaveMaxAge "1o" - 1 month

set g_XPSaveMaxAge "2w" - 2 weeks

set g_XPSaveMaxAge "5d" - 5 days

set g_XPSaveMaxAge "36h" - 36 hours

set g_XPSaveMaxAge "120m" - 120 minutes

See also g_XPSaveMaxAge_xp

'''Type:''' integer

'''Default:''' 1w

== g_XPSaveMinXP ==

'''Description:'''

The increment of XP during one map that is required for the XP gained during the map to get saved and the time of the latest XP save to get updated. The silEnT mod separates the XP save and the connection times so that players who visit spectators without playing will not be removed by the g_dbUserMaxAge but can still lose their stored XP if they do not play. Admins can adjust the requirement with this value. Using -1 will disable the requirement and XP save will consider every connection valid for the XP save. Using value 0, will consider XP save valid if the player has gained even 1 XP point during the map. Please note that the value is only for one map and using high values may cause some players to not achieve enough XP to get their XP updated. Also note, that this does not prevent SMG weapon statistics or rating values to get updated into the database.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_maxXP ==

'''Description:'''

This is a vicious cvar that will reset a players XP once their overall XP score reaches it.

Set this to -1 to disable it.

'''Type:''' integer

'''Default:''' -1

== g_maxXPResetWarn ==

'''Description:'''

Displays a message warning players whose XP is close to being reset due to the g_maxXP setting. The warning is displayed every thirty seconds once the warning threshold is passed.

This setting can have an integer value (eg, 950), in which case it means that the player will be warned every thirty seconds once he has more than 950 XP.

This setting can also have percentage value (eg, "90%"), and that will cause the warnings to start when the player reaches 90% of g_maxXP XP.

If you specify a negative value, players will be warned when that offset is hit. For example:

For a value of -75, warnings will to display then players have g_maxXP - 75 XP

For a value of -2%, warnings will display when players have 98% of g_maxXP

Set this to 0 to disable it.

'''Type:''' integer

'''Default:''' 0

== g_damageXP ==

'''Description:'''

Optionally enables the awarding of XP based upon the amount of damage a player has done to the opposing team.

'''Type:''' [0|1|2]

'''Parameters:'''

0 Disabled: use normal ET XP awarding methods

1 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the skill category of the weapon used. When this mode is enabled, kills (regardless of method) are awarded a fixed value of 1 point of XP.

2 1 point of XP is awarded per g_damageXPLevel points of damage done. The XP is placed in the Battle Sense category. Normal XP amounts are awarded for kills (typically 3-5 XP).

'''Default:''' 0

== g_damageXPLevel ==

'''Description:'''

This setting determines the amount of damage that a player must do to earn 1 point of XP. See g_damageXP for additional information.

'''Type:''' integer

'''Default:''' 50

== g_XPDecay ==

'''Description:'''

This is a bitmask that controls the XP decay feature.

See also g_XPDecayRate.

'''Type:''' bitmask

'''Parameters:'''

1 Enable XP Decay

2 Do not decay a player's XP when they are disconnected from the server

4 Do not decay a player's XP for the class they are currently playing as (e.g. Medic).

8 Do not decay a player's XP while they are spectating

16 Do not decay a player's XP during warmup/intermission

32 Do not decay a player's XP when he/she is playing. This means that they are on a Allies or Axis and the game is active.

64 Do not decay a player's Battle Sense XP when he/she is playing.

128 Do not decay a player's Light Weapons XP when he/she is playing.

'''Default:''' 0

== g_XPDecayRate ==

'''Description:'''

This is the rate (in skillpoints per second) that XP skill points for each skill will decay when g_XPDecay is enabled.

Setting this to 0.1 would result in a player losing 6 points per minute IN ALL SKILLS, so up to 42XP per minute if the player has skill points for each skill.

You can use a modifier with this value. Here are some examples:

set g_xpDecayRate "5000/o" - Decay 5000xp per skill per month

set g_xpDecayRate "1000/w" - Decay 1000xp per skill per week

set g_xpDecayRate "500/d" - Decay 500xp per skill per day

set g_xpDecayRate "40/h" - Decay 40xp per skill per hour

set g_xpDecayRate "2/m" - Decay 2xp per skill per minute

'''Type:''' float

'''Default:''' 0.0

== g_XPDecayFloor ==

'''Description:'''

This is the minimum that any particular skill can be reduced to by g_XPDecay.

For example, setting this to 140.0 will ensure that no player will ever lose rank or skill levels due to g_XPDecay.

'''Type:''' float

'''Default:''' 0.0

== g_minCommandWaitTime ==

'''Description:'''

Time you have to wait between using 2 shrubbot commands in milliseconds.

'''Type:''' integer

'''Default:''' 0

== g_tyranny ==

'''Description:'''

This cvar controls the use of administrator commands that could be used by admins to cheat or abuse players. If it is set to 0 you will not be able to use commands on your server such as !gib, !slap, !burn, etc.

Also, you will not be able to use g_logOptions flag 256 (log private messages) unless g_tyranny is enabled.

g_tyranny must also be enabled in order to specify a client in using the 'playsound' server command.

'g_tyranny' and its value appear in the serverInfo string to serve as a warning for perspective players.

'''Type:''' [0|1]

'''Default:''' 1

'''Note:'''

If you enable this, you MUST do so immediately when the server starts (before the first map is loaded). This means putting "set g_tyranny 1" in the .cfg file that is exec'ed on server start. If you try to change this on a running server, you will get the message "g_tyranny is read only."

== g_warningOptions ==

'''Description:'''

This cvar changes the behaviour of the shrubbot !warn command. By setting flag 1 or 2 you activate the advanced warning (storage) system

'''Type:''' bitmask

'''Parameters:'''

1 Link stored warnings to the guid of a player

2 Link stored warnings to the ip of the player

4 Remove the oldest warning when the total maximum ammount of warnings is reached

8 Auto-kick a player for 2 minutes when he has more than g_maxWarnings warnings

16 Allow clients to see their own warnings with the /warnings command

'''Default:''' 0

== g_maxWarnings ==

'''Description:'''

The ammount of warnings that can be stored for 1 player.

'''Type:''' integer

'''Default:''' 3

== g_warningDecay ==

'''Description:'''

The time in hours that a warning will be stored.

'''Type:''' integer

'''Default:''' 24

== g_autoTempBan ==

'''Description:'''

When set, anyone kicked for the reasons you specify, will be temporarily banned for g_autoTempBanTime seconds.

'''Type:'''bitmask

'''Parameters:'''

1 Tempban when reaching g_teamDamageRestriction

2 Tempban when someone is kicked by a shrubbot admin (using the !kick command). A normal shrubbot !kick kicks for 120 seconds

4 Tempban when someone is kicked by the advanced warning system. A normal kick by the warning system lasts 120 seconds

'''Default:''' 0

'''Changelog:'''

Specifically in version 0.5.0, this feature is bugged and can cause broken shrubbot.cfg.

== g_autoTempBanTime ==

'''Description:'''

The number of seconds kicked for when g_autoTempBan is set.

'''Type:''' integer

'''Default:''' 1800

== g_minConnectLevel ==

'''Description:'''

The minimum shrubbot adminlevel required for players to be able to connect.

'''Type:''' integer

'''Default:''' 0

'''Note:'''

This only works for positive levels, any value <= 0 will allow everyone to connect. Bots won't be able to connect either.

== g_greetingPos ==

'''Description:'''

Location where the shrubbot greetings are displayed.

'''Type:''' [0|1|2|3|4]

'''Parameters:'''

0 Chat area

1 Center of screen

2 Left notification area

3 Top of the screen

4 Console only

'''Default:''' 0

== g_identOptions ==

'''Description:'''

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 by admins while on the server. The data that is sent to the server can be seen in the client by writing /cg_ident to the console. The result is a hexadecimal string that changes its value between maps. The format and data used to create the client identification may change between different versions of the silEnT mod. The server can be configured with the g_identOptions server cvar.

'''Type:''' bitmask

'''Parameters:'''

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 with for it. 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.

'''Default:''' 0

== g_adminProtection ==

'''Description:'''

Starting from silEnT 0.5.0, admins levels can be protected against spoofing. The protection works by establishing trust between the client and the server. The trust must be confirmed by an online human admin for the new trusted admins to gain access to their assigned level. Specific command !confirm is used for it. Do note that establishing the trust between the server and the player is not the same as assigning admin level. In fact, anyone who is capable of recognizing the real admin can be safely allowed to use the !confirm command. The !setlevel command will automatically establish the trust if the admin level protection is enabled and the level is above or equal to the g_protectMinLevel. The admin protection is designed so that only the important admin levels are protected. This mean that levels above the g_protectMinLevel require established trust between the server and the client. Normal guests do not need this. It is also advisable to not set the g_protectMinLevel too low to avoid server load with these admins.

'''Type:''' bitmask

'''Parameters:'''

1 Log succesfull authentications to the cheat log

2 Log admin spoofing attempts to the cheat log

4 Report admins waiting for confirmation on their level to the admin chat

'''Default:''' 7

'''Minimum required version:''' 0.5.0

== g_protectMinLevel ==

'''Description:'''

Starting from silEnT 0.5.0, admins can be protected against spoofing. The protection works by establishing trust between the client and the server if the admin level is higher then the g_protectMinLevel. Setting this to -1 will disable the freature. Do note that when you enable the feature, noone has yet established trust with the server and the first one to have it, must be confirmed by an rcon command. Either !setlevel if the database still doesn't have admins or !confirm if the admin has been set in the database already.

'''Type:''' integer

'''Default:''' -1

'''Minimum required version:''' 0.5.0

== g_clientBinaries ==

'''Description:'''

silEnT mod can be configured to not allow players with unknown client binaries to play on the server. This cvar controls the server behaviour when the client binary is not one of the recognized ones.

'''List of recognized binaries:'''
*Official client binaries
*Binary edited executables from etmaster.net
*Equivalent to etmaster.net binary edited executables from BigBear
*ETPatchSelector binaries
*Official ET Legacy b4
*Official ET Legacy b5
*Many ET Legacy binaries including RC1 versions.

'''Type:''' bitmask

'''Parameters:'''

1 Don't allow players with unknown client executables. 
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message. 
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat. 

'''Default:''' 0

'''Minimum required version:''' 0.5.2

'''Changelog:'''

0.6.2 - If the flag 4 is set, known cheat binaries are clearly reported to the admin chat.

= Flood Protection =

== g_floodprotect ==

'''Description:'''

Enable/disable silEnT flood protect. Flooding means that a client is sending too many messages to the server (vsays, callvotes, etc...). Enabling g_floodprotect disables the engine's sv_floodprotect functionality. If you enable g_floodprotect, make sure you set a value for g_floodthreshold.

'''Type:''' [0|1]

'''Default: '''1

== g_floodthreshold ==

'''Description:'''

The number of messages per second before ignoring the client's messages. Only in effect when g_floodprotect is turned on.

'''Type:''' Integer 

'''Default:''' 6

== g_floodWait ==

'''Description:''' 

The minimum number of milliseconds between two messages when g_floodprotect is enabled. This is a hard limit so admins aren't allowed to override it. 1000 milliseconds copies sv_floodprotect behaviour. This CVAR should not have a value below 500 in order to keep a public server playable. 

'''Type:''' integer 

'''Default:''' 1000

== g_voiceChatsAllowed ==

'''Description:''' 

The number of voicechats allowed in minute. 

'''Type:''' integer 

'''Default:''' 4

= Player Statistics, Rating and Team Balance =

== g_stats ==

'''Description:''' 

This is a bitflag cvar used to control the way statistics are handled. 

'''Type:''' bitmask

'''Parameters:''' 1 When shooting a corpse to gib, do not count it as a hit. 2 When shooting a corpse to gib, do not count it as a shot. 

'''Default:''' 0 '''Note:''' Set this to 3 to use the behaviour of etmain and shrubet.

== g_playerRating_minplayers ==

'''Description:''' 

The minimum number of players that must participate in a map in order for it to count towards each player's player rating.

'''Type:''' integer 

'''Default:''' 8

== g_shuffle_rating ==

'''Description:''' 

Sets the rating system used by shuffle. 

'''Type:''' [ 1 | 2 | 3 | 4 | 5 ] 
'''Parameters:'''

1 Use player XP 2 Use the rate at which players have gained XP since connecting. 3 Use the killRating (g_killRating must be nonzero) 4 Use the playerRating (g_playerRating must be nonzero) 5 Use the playerRating (g_playerRating must be nonzero), but take the map into account and give the teams closest to 50/50 

'''Default:''' 3

== g_killRating ==

'''Description:''' 

When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points. Kill rating also takes into account the weapon used (less for arty, more for knife).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it. 2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall. 4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier. 8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.

'''Default:''' 3

== g_playerRating ==

'''Description:''' 

When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).

''See also g_shuffle_rating.''

'''Type:''' bitmask 

'''Parameters:'''

1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it. 2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player. 4 Put player rating on the scoreboard instead of the XP. 8 Print out extra info at the end of a round that can be used to further refine the playerrating model. 16 The same as flag 8 except a lot more info is output. 

'''Default:''' 3

== g_unevenTeamDiff ==

'''Description:''' 

If g_teamForceBalance is set, setting g_unevenTeamDiff will notify all players when team numbers are off by g_unevenTeamDiff or more.

''See also g_unevenTeamFreq''

'''Type:''' integer 

'''Default:''' 0 

'''Example''': Set to 0 to disable this feature 

== g_unevenTeamFreq ==

'''Description:''' 

How often the team disparity notification occurs. Only valid when g_unevenTeamDiff is set to a positive value. Value is in seconds. 

''See also g_unevenTeamDiff''

'''Type:''' integer 

'''Default:''' 30

= Class and Player Restrictions =

== team_maxPanzers ==

'''Description:''' 

Server cvars team_maxPanzers, team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMortars ==

'''Description:''' 

Server cvars team_maxMortars, team_maxFlamers, team_maxMG42s, team_maxGrenLaunchers have identical behaviour. Limits the number of the given weapon per team. 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMortars "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMortars "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMortars "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxFlamers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxFlamers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxFlamers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxFlamers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMG42s ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxMG42s "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxMG42s "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxMG42s "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxGrenLaunchers ==

'''Description:''' 

You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can also use a number such as "20%-" for this setting, in which case partial values will be rounded down

Only use integer values like 1 or 2 and NOT 1.0 or 2.5. If you refuse to do this and use a . in your cvar, the client will not display the restriction in the right way and people might not be able to use heavy weapons while they actually are available!

'''Example: '''set team_maxGrenLaunchers "2"

                This will limit each team to 2 flamethrowers, regardless of how many players are on the team

'''Example: '''set team_maxGrenLaunchers "10%"

                This will limit each team to having only 10% of their players as flamethrowers, and a team with few players (for example, 5) will be able to have 1 flamethrower. They will be able to have their second flamethrower when they have 11 players on the team.

'''Example: '''set team_maxGrenLaunchers "10%-"

                This will limit each team to having only 10% of their players as flamethrowers, and a team will not be able to have any flamethrowers until there are 10 players in the team. They will be able to have their second flamethrower when there are 20 players on the team.

''Set this to -1 to disable limits''

'''Type:''' integer '''Default:''' -1

== team_maxMedics ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxMedics "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxMedics "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxMedics "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxEngineers ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxEngineers "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxEngineers "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxEngineers "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxFieldOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxFieldOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxFieldOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxFieldOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== team_maxCovertOps ==

'''Description:'''

Restricts the number of players that can play a specific class / team. You can either set it to a whole number to set a hard limit, or you can set it to a percentage value using the % symbol to limit based on the number of players on the team. When using percentage values, any partial values are rounded up. 

You can use a number such as "20%-" for this setting, in which case partial values will be rounded down

'''Example: '''set team_maxCovertOps "5"

                This will limit each team to 5 medics, regardless of how many players are on the team

'''Example:''' set team_maxCovertOps "15%"

                This will limit each team to having only 15% of their players as medics, and a team with few players (for example, 3) will be able to have 1 medic. They will be able to have their second medic when they have 7 players on the team.

'''Example: '''set team_maxCovertOps "15%-"

                This will limit each team to having only 15% of their players as medics, and a team will not be able to have medics until there are 7 players in the team. They will be able to have their second medic when there are 14 players on the team.

''Set this to -1 to disable limits.''

'''Type:''' string 

'''Default:''' -1

== g_teamDamageRestriction ==

'''Description:'''

When greater than 0, anybody that has this percentage of hits inflicted on a teammate will automatically be kicked. A minimum of g_minhits hits total required before this is calculated. Client can see current stats for themselves by doing a /damage in console. Implemented to mimic shrub behavior as much as is possible, there are other ways to implement this feature, which may be implemented in addition to current manner.

'''Type:''' integer 

'''Default:''' 0

== g_minHits ==

'''Description:''' 

Minimum number of damaging hits required before calculating if player has reached g_teamDamageRestriction threshold. Flamethrower and landmine hits are adjusted similar to shrub. Medics get -2 hits for every revive. 

'''Type:''' integer 

'''Default:''' 6

== g_minAirstrikeTime ==

'''Description:''' 

The time (in seconds) that must elapse between airstrikes PER TEAM. 

'''Type:''' integer 

'''Default:''' 10

== g_minArtyTime ==

'''Description:''' 

The time (in seconds) that must elapse between airtillery strikes PER TEAM. Attempts to do airstrike before the timeout will get "Insuffient fire support" message. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamLandmines ==

'''Description:''' 

Sets the maximum number of landmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 10

== g_maxTeamTripmines ==

'''Description:''' 

Sets the maximum number of tripmines a team can have planted at any given time. This value should be 0 or greater. 

'''Type:''' integer 

'''Default:''' 3

== g_minGameClients ==

'''Description:''' 

The number of clients needed to start a match. 

'''Type:''' integer 

'''Default:''' 0

== g_maxGameClients ==

'''Description:''' 

The maximum allowed amount of active clients.

'''Type:''' integer

'''Default:''' 0

= Gametypes =

== Campaign ==

== Objective ==

== Last Stand ==

== Map Voting ==

This gametype allows for the players to decide on the map that is played next. When g_gametype is set to 6 a new screen is introduced during intermission. This screen list, depending on server configuration, a list of up to 32 maps that are loaded on the server, and that all players can vote on. Once intermission ends, the server totals the votes, and plays the next map based upon the vote results

;;Miscellaneous notes about mapvoting:
:

Total maps allowed is 32. If server admin has more than 32 .bsp files, only the first 32 are used Tie breaker. The default tie-breaker is such that if 2 or more maps are tied with the same number of votes, the map that was played most recently is selected. Bots and connecting players do NOT count for mapvoting, everyone else (including spectators) does. If no maps are voted for, the default "nextmap" cvar is used, so server admins have to specify a default map cycle of sort, usually in the following format:
<blockquote>set d1 "set g_gametype 6 ; map oasis ; set nextmap vstr d2" set d2 "set g_gametype 6 ; map battery ; set nextmap vstr d3" set d3 "set g_gametype 6 ; map goldrush ; set nextmap vstr d1" vstr d1 </blockquote>
This means that the default map, upon server start, will be oasis. From there, map voting will be used. If at any point, no map is voted for, battery will be played, etc

 

=== g_mapVoteFlags ===

'''Description:''' This cvar controls the behaviour of the map voting.

'''Type:''' bitmask 

'''Parameters:'''

1 Changes the tie breaker so that the map not played in the longest wins 2 Intermission doesn't end until g_intermissionReadyPercent people have voted. If there are no players connected to the server, intermission will end at the timeout. (WARNING: This means that if there are spectators connected and not voting, the next map will not load until those spectators either vote, disconnect, or get kicked by the system) 4 Multi vote: Allows everybody to vote for 3 maps instead of one, first choice map gets 3 votes, second choice gets 2, third choice gets one 8 Don't randomize the maps, so they will always appear in the same order 16 The !nextmap command and a passed nextmap vote will start the intermission and lets players vote which map should be played next. NOTE: this makes the game end as a tie. 

'''Default:''' 0

=== g_maxMapsVotedFor ===

'''Description:''' How many maps are available to players for voting upon during intermission. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 6

=== g_minMapAge ===

'''Description:''' 

How long a map is ineligible for voting during intermission, after it is played last time. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 3

=== g_resetXPMapCount ===

'''Description:''' 

How many maps occur before XP is reset. If g_XPSave flag 4 is set, g_resetXPMapCount is ignored. Similarly, if g_resetXPMapCount is set to 0, it is the same as setting g_XPSave flag 4 ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' integer 

'''Default:''' 0

=== g_excludedMaps ===

'''Description:''' 

Used to exclude map that would otherwise be listed in the map voting list. The format is ":map1:map2:map3:", where mapX is the .bsp name. Note that each mapname must be fully surrounded by ":" otherwise the map will not be excluded. ''Only valid when g_gametype is 6 (see Map Voting)'' 

'''Type:''' string 

'''Default:''' ""

'''Example:''' To exclude railgun and battery maps from map voting use below command: 
set g_excludedMaps ":railgun:battery:"

== Team Death Match (TDM) ==

=== g_TDMType ===

'''Description:'''

The type of the played Team Death Match.

'''Type:''' [ 1 | 2 | 3 ]

'''Parameters:'''

1 Map ends only when timelimit hits

2 Map ends when either the target score is reached or the timelimit hits

3 Map ends only when the target score is reached

'''Default:''' 0

=== g_TDMOptions ===

'''Description:'''

Possible options for the played Team Death Match.

'''Type:''' bitmask

'''Parameters:'''

1 Map voting is enabled during the intermission (i.e. The players vote for the next map to play during the intermission.)

2 Completing the map objective will give the team score bonus that is controlled by the g_TDMObjBonus server cvar

4 Teams get negative points when they do selfkills or teamkills

8 Players cannot selfkill during the TDM. Regardless of other selfkill settings the server has configured

'''Default:''' 5

=== g_TDMScore===

'''Description:'''

This is the target score the teams attempt to make to win the game in TDM game types 2 and 3.

'''Type:''' integer

'''Default:''' 100

=== g_TDMObjBonus===

'''Description:'''

This is the value that is added to the team score if the team completes the map objective. Adding the bonus does not depend of the TDM type.

'''Type:''' integer

'''Default:''' 20

= Mapconfigs and Mapscripts =

== g_mapConfigs ==

'''Description:'''

On each map load, the silEnT server will execute 2 configs if possible. The default.cfg and after that a map specifig config file [mapname].cfg. For example if you set g_mapConfigs to 'mapcfg', when the map fueldump starts, the server will try to exec 'mapcfg/fueldump.cfg'.

Set this to "" to disable it.

Set this to "." to look for the cfg file in the current directory (fs_homepath).

Starting from silEnT version 0.5.2, admins can add settings that are executed for specific player amounts. The commands are enclosed in [players low-high] ... [/players] blocks. The low is the lowest amount of players for those settings and high is the maximum amount of players for those settings. For example:

[players 0-10] 
set team_maxPanzers 0 
[/players] 
will disable panzerfaust when player amount is less or equal to 10. The blocks can be placed anywhere in the map config files. If the block is closed with [/players], the following commands do not depend on the player amounts. The player blocks can not be nested. If two player blocks follow each other, the second definition opens a new one and the old one closes. For example: 
[players 0-15] 
set g_excludedMaps ":mlb_temple:" 
[players 16-*] 
set g_excludedMaps ":adlernest:" 
[/players] 
will exclude map MLB Temple if the player amount is less or equal to 15 and exclude map Adlernest if the player amount is 16 or more. The player amount counting is controlled with g_playerCounting server cvar. 

When in g_gametype 6 mode (Map Voting) and g_resetXPMapCount is set, an additional file named vote_X.cfg is also exec'ed. X indicates the position of the next map in the campaign. For example, vote_2.cfg will exec'ed such that when map 1 ends, any cvars in vote_2.cfg will affect map voting for map 2. Player blocks are not used with vote_X.cfg files. 

'''Type:''' string

'''Default:''' ""

== g_mapScriptDirectory ==

'''Description:'''

Similar to ETPro's b_mapscriptsdirectory. Set it to the name of a directory in your fs_path that contains custom map scripts. For example you can copy the 'etpromapscripts' directory from the ETPro distribution to your 'silent' directory and add: set g_mapScriptDirectory "etpromapscripts" to your cfg. Setting g_mapScriptDirectory to "" disables any use of map .script files.

'''Note:'''

It is strongly recommended that you use the map scripts distributed with silEnT or ETPub since these updated scripts fix very important bugs in some of the original map scripts.

'''Type:''' string

'''Default:''' ""

== g_campaignFile ==

'''Description:'''

If you set this to the name of a file in your fs_path it will be interpreted as a .campaign script and all other .campaign scripts in your pk3 files will be ignored. This is useful for making custom campaigns since you don't need to offer a pk3 file containing a custom .campaign script for all clients to download. However, if the client has not downloaded this .campaign file in a pk3, they will not see information about the campaign.

Such information includes:

*will not display in the VOTE -> MAP list
*map locations will not draw on the map of Europe.
*campaign description will not draw in the right panel
*total number of maps and current maps order in the campaign
*will not be shown in the intermission screens.

Also, even though the built-in campaigns cmpgn_centraleurope and cmpgn_northafrica will not be valid, they will still appear in the client's VOTE -> MAP menu. If a vote for one of them passes, nothing will happen.

Setting this to "" disables it.

'''Type:''' string

'''Default:''' ""

== g_playerCounting ==

'''Description'''

This cvar controls how the player amount is calculated for the mapconfigs. The player amount value is the highest number of simultaneously fully connected players during the map or warmup. The player counting can be disabled from the warmup period. If the player counting is enabled during the warmup, the players are counted right at the end of the warmup. This allows the teams to stabilize after intermission. Similarly the counting is triggered always with a 3 second delay from the change in the teams. Team changes include players joining the server and staying
in the spectators.

'''Type:''' bitmask

'''Parameters:'''

1 Enable filtering. This will add the 2 latest values together and divide them by 2.

2 No player counting during warmup.

4 Count spectators into players. Without this flag, only players in the playing teams are counted.

8 Bots are not included into the player count.

'''Default:''' 1

= Censoring =

== g_censor==

'''Description:'''

A comma delimited string of words that will be censored from the chat.

'''Type:''' string

'''Default:''' ""

== g_censorNames==

'''Description:'''

A comma delimited string of words that will be censored from the player names.

'''Type:''' string

'''Default:''' ""

== g_censorPenalty==

'''Description:'''

This controls the censoring behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kill the player

2 Kick players with names containing words in g_censorNames

4 Kill, but don't gib

8 Auto-mute for g_censorMuteTime [60] seconds

16 Lose the amount of xp specified in g_censorXP

32 Burn

'''Default:''' 0

'''Note:'''

If you use both 1 and 4, it will gib (like shrub did).

== g_censorNeil==

'''Description:'''

Use Neil Toronto's censor filter. It'll catch some symbol and number replacements,
and spaces now. It also adds some common words and common words with "swears" in them
that should really be OK. For example, it will not censor "assassin" but it will
censor "ass".

'''Type:''' [0|1]

'''Default:''' 0

== g_censorNeilNames==

'''Description:'''

Use Neil Toronto's censor filter for player names. See g_censorNeil description for
details.

'''Type:''' [0|1]

'''Default:''' 0

== g_censorMuteTime==

'''Description:'''

The number of seconds to auto-mute as a censor penalty. Only works if bitflag 8 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 60

== g_censorXP==

'''Description:'''

The amount of XP to lose as a censor penalty. Only works if bitflag 16 is added to g_censorPenalty.

'''Type:''' integer

'''Default:''' 5

= Voting =

== g_voting ==

'''Description:'''

Control's voting behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Votes will pass on the number of votes cast rather than total eligible voters.

2 Votes that pass do not count against the vote_limit for the caller.

4 " (called by NAME)" is appended to the vote description where NAME is the name of the player that called the vote.

8 Show the number of YES and NO votes after a votes has passed or failed. This also shows if a vote is canceled or passed by an admin.

'''Default:''' 0

== vote_limit==

'''Description:'''

This value defines how many votes one player can invoke during one map.

'''Type:''' integer

'''Default:''' 5

== vote_percent==

'''Description:'''

The required percentage of yes votes for the vote to pass.

'''Type:''' integer

'''Default:''' 50

== vote_allow_comp==

'''Description:'''

Allows voting for competition settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_gametype==

'''Description:'''

Allows voting for gametype.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_kick==

'''Description:'''

Allows voting for kicking a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_map==

'''Description:'''

Allows voting for map to be played.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_matchreset==

'''Description:'''

Allows voting for restarting the match.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_mutespecs==

'''Description:'''

Allows voting for muting spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextmap==

'''Description:'''

Allows voting for starting the next map in the map rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_pub==

'''Description:'''

Allows voting for public game settings.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_referee==

'''Description:'''

Allows voting for making a player a referee.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shuffleteamsxp==

'''Description:'''

Allows voting for shuffling teams based on XP.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_swapteams==

'''Description:'''

Allows voting for swapping the teams. Allied players go to the axis team and axis players go to the allied team.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_friendlyfire==

'''Description:'''

Allows voting for enabling/disabling friendly fire.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_timelimit==

'''Description:'''

Allows voting for changing the map time.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_warmupdamage==

'''Description:'''

Allows voting for enabling/disabling/enemies only warmup damage.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_antilag==

'''Description:'''

Allows voting for enabling/disabling antilag.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_balancedteams==

'''Description:'''

Allows voting for enabling/disabling balanced teams enforcing.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_muting==

'''Description:'''

Allows voting for muting/unmuting a player.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_surrender==

'''Description:'''

Allows voting for surrendering the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_restartcampaign==

'''Description:'''

Allows voting for restarting the campaign.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_nextcampaign==

'''Description:'''

Allows voting for changing the campaign to the next one in the campaign rotation.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_poll==

'''Description:'''

Allows making freely written polls using the vote system.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_maprestart==

'''Description:'''

Allows voting for restarting the played map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_shufflenorestart==

'''Description:'''

Allows voting for shuffling teams without restarting the map.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_cointoss==

'''Description:'''

Allows voting for doing cointoss.

'''Type:''' [0|1]

'''Default:''' 1

== vote_allow_putspec==

'''Description:'''

Allows voting for moving a player to the spectators.

'''Type:''' [0|1]

'''Default:''' 1

== vote_block_maprestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_matchreset==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the match allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shuffleteamsxp==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_shufflenorestart==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for shuffling the teams without restarting the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextmap==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for starting the next map in the map rotation allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_swapteams==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for swapping the teams allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_surrender==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for surrendering the map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_map==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for played map allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_timelimit==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for changing the map time allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_poll==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for polls allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_nextcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for next campaign allowed.

'''Type:''' integer

'''Default:''' 300

== vote_block_restartcampaign==

'''Description:'''

Defines how many seconds from the beginning of the map is the voting for restarting the campaign allowed.

'''Type:''' integer

'''Default:''' 300

== g_noVoteTime==

'''Description:'''

Defines how many seconds must pass between two votes.

'''Type:''' integer

'''Default:''' 0

== g_voteResultsMinLevel==

'''Description:'''

Defines the minimum admin level for the players to see the results of the votes.

'''Type:''' integer

'''Default:''' -1

== g_votedMuteLength==

'''Description:'''

Defines the length in seconds of the mute issued by a passed mute vote. You can use modifiers with this value.

'''Type:''' integer

'''Default:''' 3h

= Weapons, Classes and Skills =

== g_poison ==

'''Description:'''

Gives medics the ability to poison enemies by sticking with their medic
syringe. Enemies will be damaged at g_poison/second when g_poison is
set to a value more than 0. Setting to 0 will disable poison needles.

'''Type:''' integer

'''Default:''' 0

== g_poisonFlags ==

'''Description:'''

Controls the effects of g_poison.

'''Type:''' bitmask

'''Parameters:'''

1 Poisoned player's screen shakes.

2 Other players see the poisoned player's head shaking.

4 Poisoned player appears to bend over (hurl) every 2 seconds. (poisoned player does not see this happen.)

8 Poisoned player cannot use +attack. NOTE: because of client side prediction, the client may see the gun firing occasionally if they hold down +attack, but no shots are fired.

16 Poisoned player is disoriented (view turned upside down).

'''Default:''' 7

== g_medics ==

'''Description:'''

Controls various aspects of the medic, to nerf or otherwise change their behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Medics can't pick up their own health packs to cure themselves of poison needle effects.

2 Medics can't pick up their own health packs at all.

4 A level 4 medic will always be revived to full health (no matter what the level of the reviving medic is).

8 Value is not in use.

16 Medics do not spawn with akimbo pistols, regardless of their light weapons skill.

32 Medics spawn with pistol only, and can't pick up SMG of either team. However, any class can steal a medics uniform, if the g_classChange is set to 1, and receive the medic benefits while retaining their current weapons, including akimbos and SMG.

64 Medics can use syringes to heal living teammates as an alternative to the tk/revive cycle.

128 Level 4 medics can inject other players with their adrenaline. This can be done when holding the revive needle by pressing the alt-fire button, or with the /adrenother client command.

256 Level 4 medics cannot adrenaline self. If this flag is on, Medics will not receive adrenaline upon reaching level 4. (This won't affect flag 128)

512 Adrenaline use takes only half of the chargebar.

'''Default:''' 0

== g_adrenDmgReduction ==

'''Description:'''
The percentage damage reduction after injecting adrenaline. g_adrenDmgReduction is now independent percentage of the caused damage that is inflected when the adrenaline is on. 0 means no damage and 100 means full damage from the weapon.

'''Type:''' Integer

'''Default:''' 50

== g_medicHealthRegen==

'''Description:'''

The rate at which medics regenerate health (in HP per second). This rate is divided into two parts: The first is from 1 to 110-125 HP (depending on the number of medics per team), and then above that. The system default is 3/2 (3 HP per second, then 2 HP per second).

'''Type:''' [ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 ]

'''Parameters:'''

0 3/2

1 2/2

2 2/1

3 2/0

4 1/1

5 1/0

6 0/0

7 0/1

8 0/2

'''Default:''' 0

== g_throwableKnives ==

'''Description:'''

Enable knife throwing. The amount of throwable knives is g_maxKnives - 1. Any non zero value will enable knife throwing.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxKnives ==

'''Description:'''

Maximum number of knives a player can posses. Take note that if g_throvableKnives is enabled, the last knife cannot be thrown.

'''Type:''' integer

'''Default:''' 5

== g_knifeChargeTime ==

'''Description:'''

How long it takes in milliseconds for the "knife" to charge to the maximum throw speed/force.

'''Type:''' integer

'''Default:''' 800

== g_constructibleXPSharing==

'''Description:'''

When multiple engineers help build a constructible, each gets his share of XP
once the constructible is build. The share of gained XP is proportional to
how much the engineer built.

'''Type:''' [0|1]

'''Default:''' 0

== g_asblock ==

'''Description:'''

Airstrike blocking.

'''Type:''' bitmask

'''Parameters:'''

1 Make an announcement whenever an airstrike is blocked.

2 A player may easily block an airstrike by crouching, standing, or proning over the enemy's canister to block the airstrike.

4 Reserved.

8 Lvl 3 FieldOPs and higher cannot have the airstrikes blocked by players.

16 Disables teammates blocking airstrikes.

32 Give 2 Battle Sense XP to player that blocks the air strike. No XP given for blocking teammates or your own air strike.

'''Default:''' 0

== g_panzersSpeed ==

'''Description:'''

Speed of the panzers. Normal panzer speed is 2500.

'''Type:''' integer

'''Default:''' 2500

== g_panzersGravity ==

'''Description:'''

If set to 1, panzer trajectory will be affected by gravity.

'''Type:''' [0|1]

'''Default:''' 0

== g_dyno==

'''Description:'''

Dynamite Behaviour.

'''Type:''' bitmaks

'''Parameters:'''

1 Sudden Death Dynamites enabled. If there is 30 seconds or less on the clock and dynamite is planted on an objective, the clock will continue to run past zero. The match will not end until the dynamite either explodes, or is disarmed. You are not allowed to plant additional dynamite during sudden death.

2 Dynamite chaining enabled. Dynamite will cause other similar dynamites to explode when exploding (only if within blast radius). Dynamites not planted on an objective will blow any other dynamite not on an objective. Dynamite planted on an objective will only blow dynamite on the same objective.

4 Adds a dynamite symbol with the location and the time remaining to all the players on the team of the player who plants the dynamite. This will only happen when dynamite is placed on an objective. The players in the other team will see the dynamite symbol too, but they won't see the time remaining.

8 Dynamite cannot be disarmed by your team (inlcuding yourself), so only the other team can defuse it.

16 Enable dynamite ID. You can see the owner of a dynamite when you point at it.

'''Default:''' 0

== g_canisterKick ==

'''Description:'''

Canister and grenade kicking.

Allows players to kick smoke, and air strike canisters, along with grendaes. The integer adjust the amount of force put behind the kick. 75 is a good value, anything below 60 is about useless, and above about 125 is probably too much.

'''Type:''' integer

'''Default:''' 0

== g_canisterKickOwner ==

'''Description:'''

Kicked Canister Ownership.

'''Type:''' [0|1]

'''Parameters:'''

0 Kicker does not take ownership of the canister.

1 Kicker takes ownership of the canister.

'''Default:''' 0

== g_reflectFriendlyFire ==

'''Description:'''

Similar to Shrub's g_friendlyfire 2 cvar. A multiplier value that determines how much friendly-fire damage, if any, is reflected back to the player that caused the damage. This setting is independent of g_friendlyfire, so damage can be set to reflect on both FF and non-FF servers.

A value of 1.0 would reflect full damage.

A value of 0.5 would reflect half damage.

Set to 0 to disable reflected friendly fire.

'''Type:''' float

'''Default:''' 0.0

== g_reflectFFWeapons==

'''Description:'''

Selects which category of weapon will reflect when g_reflectFriendlyFire is non-zero.

'''Type:''' bitmask

'''Parameters:'''

1 Enable reflected damage for Firearms (all types of guns)

2 Enable reflected damage for Grenades and grenade launchers

4 Enable reflected damage for Knives (includes thrown knives)

8 Enable reflected damage for Panzers

16 Enable reflected damage for Flamethrowers

32 Enable reflected damage for Mortars

64 Enable reflected damage for Satchel Charges

128 Enable reflected damage for Artillery and Air Strikes

256 Enable reflected damage for Dynamite and Construction Damage

512 Enable reflected damage for Landmines

'''Default:''' 31

'''Note:'''

Setting this value to zero will override any multiplier set via g_reflectFriendlyFire, effectively disabling reflecting damage.

== g_friendlyFire ==

'''Description:'''

To enable / disable friendly fire on server. 

'''Type''': [0|1]

'''Default''': 0

== g_friendlyFireOpts ==

'''Description:'''

Allows greater control over friendly fire events.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines ALWAYS damage teammates regardless of g_friendlyfire setting

2 Allow 'grenade boosting' when friendly fire is off

4 Non-engineer players do not trigger landmines on their own team

8 Players do not trigger trip mines on their own team

16 Tripmines ALWAYS damage teammates regardless of g_friendlyfire setting

32 Only engineer that planted the landmine can trigger/defuse it (concerns team landmines only). This flag requires that the flag 4 is set.

'''Default:''' 0

'''Changelog:'''

Flag 32 was added in version 0.5.1.

== g_staminaRecharge ==

'''Description:'''

Multiplies the rate at which stamina is rebuilt. Setting this value to zero will cause players to not regain any stamina once it is used except through the use of adrenalin.

'''Type:''' float

'''Default:''' 1.0

== g_mineid ==

'''Description:'''

Turns on identification of your teammates landmines.

'''Type:''' [0|1]

'''Default:''' 0

== g_medicSelfhealTime==

'''Description:'''

The time in milliseconds that a medic cannot heal himself after being hit.

'''Type:''' integer

'''Default:''' 0

== g_maxPanzerSuicides ==

'''Description:'''

When set, a player can kill himself g_maxPanzerSuicides times with a panzerfaust. The next panzerselfkill will result in a panzer shooting medpacks.

The amount of suicides is reset every map.

Set to -1 to disable, -2 to always enable (no normal panzers anymore)

'''Type:''' integer

'''Default:''' -1

== g_panzerPackDistance ==

'''Description:'''

Set the g_packDistance for the medpacks fired by the panzerfaust when g_maxPanzerSuicides is enabled.

Set to 0 to use default (etmain)

'''Type:''' integer

'''Default:''' 0

== g_weapons ==

'''Description:'''

This is meant to match the shrubmod g_weapons cvar.

'''Type:''' bitmask

'''Parameters:'''

1 Level 0 field ops doesn't get binoculars (unless he has >= level 1 Battle Sense)

2 Syringes work underwater

4 Pliers work underwater

8 Fully restore Field ops charge bar if airstrike is aborted

16 Half restore FIeld ops charge bar if airstrike is aborted

32 Ammo packs restore helmets

64 Drop binoculars if player has them

128 Soldiers with level 4 heavy weapons don't lose their pistols

256 Garands can reload when clip is not empty

512 Balance the clip size between the allies and axis rifles. allied rifles get same clip sizes and max ammo as the k43.

1024 Creates a hitbox for mortar shells. This reduces (or eliminates in some cases) the ability to fire mortars through smaller windows and bunker slits.

2048 Knives will always gib a body (not a player, use g_dmgKnife instead if you want that)

4096 Extra ammo is included with dropped weapons.

8192 "Ammo"/"No ammo" icon is shown for dropped weapons.

16384 Enable fast shooting for Thompson, MP40, PPSh and Sten. 110 ms between shots.

32768 Kill by the shot tripmine is counted for the shooter not the player that planted it.

'''Default:''' 0

'''Changelog:'''

Flag 16384 was added in version 0.6.2.

== g_classWeapons==

'''Description:'''

This cvar enables certain weapons per class. So far, only PPSH enablement is implemented.

'''Type:''' bitmask

'''Parameters:'''

1 Enable PPSH for soldiers

2 Enable PPSH for engineers

4 Enable PPSH for fieldops

8 Enable MP40 and Thompson to be available to both teams in limbo menu

16 Enable MP40 for soldiers.

32 Enable Thompson for soldiers.

'''Default:''' 63

'''Changelog:'''

Flag 8 was added in version 0.6.0.

Flags 16 and 32 were added in version 0.6.2. Also the default value was changed from 15 to 63.

== g_mg42 ==

'''Description:'''

This cvar controls optional machine gun behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Machine Guns can make headshots

2 Machine Guns can reload when clip is not empty

'''Default:''' 0

== g_coverts ==

'''Description:'''

Controls various aspects of the Covert Op class.

'''Type:''' bitmask

'''Parameters:'''

1 Level 4 Coverts have more accurate scoped weapons.

2 Disguised coverts can only be identified with the "crosshair name" by level 4 Field Ops.

4 After detonating a satchel charge, the primary weapon will be selected instead of satchel again.

8 Coverts in disguise take half the normal combat damage.

16 Coverts in disguise take no splash damage.

32 Coverts do not automatically lose their uniform if an enemy sees them firing a weapon.

64 Coverts do not automatically lose their uniform if they fire a non-silent weapon.

128 Coverts do not automatically lose their uniforms if they attach to an emplaced MG weapon. Note that this flag has nothing to do with firing.

256 Coverts are awarded xp for constructive use of smoke.

512 Coverts will lose their uniform if an enemy sees him using ANY weapon (otherwise knife/satchel/smoke/binoc will never lose uni).

1024 A disguised covert can still steal enemy uniforms.

'''Default:''' 0

== g_enableTMines ==

'''Description:'''

Disables/enables tripmines. Tripmines are available only for engineers.

'''Type:''' [0|1]

'''Default:''' 1

== skill_soldier==

'''Description:'''

Customizes the experience points necessary to go up in soldier ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_medic ==

'''Description:'''

Customizes the experience points necessary to go up in medic ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_engineer ==

'''Description:'''

Customizes the experience points necessary to go up in engineer ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_fieldops ==

'''Description:'''

Customizes the experience points necessary to go up in fieldop ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_covertops==

'''Description:'''

Customizes the experience points necessary to go up in covert op ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_battlesense ==

'''Description:'''

Customizes the experience points necessary to go up in battle sense ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== skill_lightweapons ==

'''Description:'''

Customizes the experience points necessary to go up in light weapon ranks. The setting consist of four space-separated integers indicating the number of XP required to reach a rank.

A string such as "3 10 10 10" indicates that 3 points are required to go up the first rank, and the next three ranks are granted when the player has 10 points.

You can also grant levels upon connection by using a value like "0 0 20 100". This would mean that the first two ranks would be granted upon connection, and the third and fourth ranks would be granted at 20 and 100 points, respectively.

Starting from silEnT 0.6.0, this cvar also allows disabling skills. Also, 0 value will always enable skill regardless of the order. For example, a string "0 -1 0 -1" always enables the skill from the first and the third level and completely disables the skills on the second and the fourth level. The only limitation is, that the values other then 0 and -1 must be ordered from the smaller to the higher. For example "0 20 -1 50" always enables the first skill, second skill takes 20 points to unlock, third skill is always disabled and the fourth skill requires 50 points to unlock. Furthermore, the g_noSkillUpgrades now locks skills to any always enabled levels. Meaning skills that are set to require 0 points to unlock.

'''Type:''' string

'''Default:''' "20 50 90 140"

== g_panzersVulnerable==

'''Description:'''

If set to 1, panzers that are shot in mid-air will explode.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxMarkers ==

'''Description:'''

Defines how many danger zones can be marked by the covert ops.

Danger zones were introduced in 0.7.0 version of the silEnT mod. They can be marked by Covert Ops to indicate that some area can be considered dangerous. Such area is then visible on the command map as the red circle zone. Additionally, when the Command Post is built, players are notified by sound and visual signs about entering the danger zone. Players can customize the way they are notified via the HUD editor and the silEnT customize HUD menu.

To mark the danger zone Covert Ops needs to look through his binoculars and press the left mouse button (attack button). The same way Field Ops calls for an airstrike.

To disable the feature set the g_maxMarkers to 0.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

= Weapon Damage and Radius Settings =

== g_dmgKnife ==

'''Description:'''

Amount of damage done by the knife.

'''Type:''' integer

'''Default:''' 10

== g_dmgSten ==

'''Description:'''

Amount of damage done by the sten.

'''Type:''' integer

'''Default:''' 14

== g_dmgFG42 ==

'''Description:'''

Amount of damage done by the FG-42.

'''Type:''' integer

'''Default:''' 15

== g_dmgPistol==

'''Description:'''

Amount of damage done by the pistol weapons.

'''Type:''' integer

'''Default:''' 18

== g_dmgSMG ==

'''Description:'''

Amount of damage done by the SMG weapons (Thompson and MP-40).

'''Type:''' integer

'''Default:''' 18

== g_dmgMG42 ==

'''Description:'''

Amount of damage done by the MG42.

'''Type:''' integer

'''Default:''' 18

== g_dmgMG ==

'''Description:'''

Amount of damage done by an emplaced MG.

'''Type:''' integer

'''Default:''' 20

== g_dmgFG42Scope==

'''Description:'''

Amount of damage done by the FG-42 when scoped.

'''Type:''' integer

'''Default:''' 30

== g_dmgInfRifle ==

'''Description:'''

Amount of damage done by unscoped rifles (K43 and Garand).

'''Type:''' integer

'''Default:''' 34

== g_dmgSniper ==

'''Description:'''

Amount of damage done by a scoped Garand or K43.

'''Type:''' integer

'''Default:''' 50

== g_dmgFlamer ==

'''Description:'''

Amount of damage done by the a flamethrower. Also controls the per-tick damage done to a player who has been set on fire by a flamethrower and is still burning.

'''Type:''' integer

'''Default:''' 5

== g_dmgGrenade==

'''Description:'''

Amount of damage done by a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGrenadeRadius ==

'''Description:'''

Blast radius of a grenade.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncher ==

'''Description:'''

Amount of damage done by an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgGLauncherRadius ==

'''Description:'''

Blas radius of an engineer's grenade-launcher grenades.

'''Type:''' integer

'''Default:''' 250

== g_dmgTMine==

'''Description:'''

Amount of damage done by a tripmine.

'''Type:''' integer

'''Default:''' 260

== g_dmgLandmine ==

'''Description:'''

Amount of damage done by a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgLandmineRadius ==

'''Description:'''

Blast radius of a landmine.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchel ==

'''Description:'''

Amount of damage done by a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgSatchelRadius==

'''Description:'''

Blast radius of a satchel.

'''Type:''' integer

'''Default:''' 250

== g_dmgPanzer ==

'''Description:'''

Amount of damage done by a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 400

== g_dmgPanzerRadius ==

'''Description:'''

Blast radius of a panzerfaust rocket.

'''Type:''' integer

'''Default:''' 300

== g_dmgMortar==

'''Description:'''

Amount of damage done by a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgMortarRadius==

'''Description:'''

Blast radius of a mortar round.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamite ==

'''Description:'''

Amount of damage done by a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgDynamiteRadius ==

'''Description:'''

Blast radius of a dynamite.

'''Type:''' integer

'''Default:''' 400

== g_dmgAir ==

'''Description:'''

Amount of damage done PER BOMB by an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgAirRadius==

'''Description:'''

Blast radius PER BOMB of an airstrike.

'''Type:''' integer

'''Default:''' 400

== g_dmgArty ==

'''Description:'''

Amount of damage done PER BOMB by artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour (can do damage, but to a very small radius, making damage unlikely)

'''Type:''' integer

'''Default:''' 400

== g_dmgArtyRadius ==

'''Description:'''

Blast radius PER BOMB of artillery fire. If this value is non-zero, the spotting round will follow normal ET behaviour. The spotting round can do damage, but to a very small radius making damage unlikely.

'''Type:''' integer

'''Default:''' 400

== g_dmgDemolition ==

'''Description:'''

Amount of damage done by Improvised Demolition.

'''Type:''' integer

'''Default:''' 1100

== g_dmgDemolitionRadius ==

'''Description:'''

Blast radius of Improvised Demolition.

'''Type:''' integer

'''Default:''' 250

== g_dmg ==
'''Description:'''

Enables experimental advanced combat options.

'''Type:''' bitmask

'''Parameters:'''

0 Use traditional ET settings for combat.

1 Use Advanced Hit Locations: Differentiates between Head, Body, Arm, and Leg shot when computing damage.

2 Applies a more realistic damage vs. range equation for short-ranged weapons. This will reduce the effectiveness of these weapons at longer ranges.

4 Gives a damage bonus to short-range weapons when used in close combat situations. This will increase the effectiveness of these weapons at closer ranges.

8 Use bullet fall-off approximations when computing shot trajectory.

16 Improve accuracy of non-scoped single-shot rifles.

32 Use alternate bullet-spread characteristics for automatic or rapid-fire weapons.

64 Damage from players who are spectators or have disconnected is ignored, and XP is not awarded.

'''Default:''' 0

== g_dmgHeadShotMin==

'''Description:'''

This represents the minimum damage done by a headshot regardless of the weapon used to make the shot.

Headshots that would do damage below this value will be adjusted upward to equal g_dmgHeadshotMin. Headshots from a weapon with damage at or above this value will do a multiple of their damage, as specified by g_dmgHeadShotRatio. (The actual damage may undergo additional modification due to range and other conditions)

'''Type:''' integer

'''Default:''' 50

== g_dmgHeadShotRatio ==

'''Description:'''

This specifies the multiplier used for headshots that do damage ABOVE g_dmgHeadShotMin.

'''Type:''' float

'''Default:''' 2.0

== g_knifeThrowDamage ==

'''Description:'''

The amount of damage a thrown knife will cause to enemy.

'''Type:''' integer

'''Default:''' 50

== g_dmgPPSh==

'''Description:'''

The amount of damage done by a PPSh.

'''Type:''' integer

'''Default:''' 19

= Hitboxes, Physics & Anti Lag Settings =

== g_antilagDelay ==

'''Description:'''

Manually delay the antilag of every player on the server. Might give very weird behaviour, so use at own risk.

'''Type:''' integer

'''Default:''' 0

== g_fixedphysics==

'''Description:'''

Creates a smoother movement when enabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_fixedphysicsfps ==

'''Description:'''

Makes the fixedphysics act like all the clients have the same framerate, so that players with "magic" quake engine framerates don't have an unfair advantage. This CVAR must be between 60 and 333.

'''Type:''' integer

'''Default:''' 125

'''Note:'''

This doesn't actually change the framerates in clients, so the clients can keep their own framerates.

== g_antiwarp==

'''Description:'''

Enable ETPro-style antiwarp. This gives non-lagging players a much better game but for laggers it will be a bit more uncomfortable. This CVAR overrides both g_maxWarp AND g_skipCorrection in order to keep things consistent.

'''Type:''' [0|1]

'''Default:''' 1

== g_realHead==

'''Description'''

Enable ETPro headboxes.

'''Type:''' [0|1]

'''Parameters:'''

0 Regular headbox positions.

1 Server tracks the animations so the headbox will match the playermodels exactly. This is the recommended value.

'''Default:''' 1

'''Note:'''

This code was originally from ETPro (b_realhead). It was contributed by zinx and added to ETPub by forty. silEnT is based on the ETPub source and this code has not been altered from the ETPub.

'''Change log:'''

:* 0.5.1 - The option was removed. The ETPro headboxes are always used.

== g_realBody ==

'''Description'''

If server admin sets this, the player hitboxes are adjusted smaller and harder to hit. Value 0 corresponds to the hitboxes used up to 0.5.0.

'''Parameters:'''

0 Hitboxes used up to 0.5.0

1 Use smaller hitboxes

'''Default:''' 0

'''Minimum required version:''' 0.5.1

'''Note'''

To see the differences in the hitboxes, use g_debughitboxes server cvar. Do note that this kind of testing should not be done with many players because it will cause huge amount of lag.

== g_skipCorrection ==

'''Description:'''

Set this to 1 to enable Neil Toronto's unlagged2 skip correction. This will smooth out the movement of players with high packet loss (to a degree). This is similar to etpro's antiwarp, but has some differences. Neil likes this version better, bani likes his better.

This replaces g_smoothClients from etmain.

'''Type:''' [0|1]

'''Default:''' 0

== g_maxWarp ==

'''Description:'''

This allows you to control the amount of "warping" that players with high packet loss can do. The [integer] is the number of server frames that you allow a player to miss before their next movement is put in check.

A server frame is 50ms on a typical server (sv_fps set to 20). This means that if you set g_maxWarp to 5 you won't allow players to warp from point A to point B if that distance takes an normal player 1/4
of a second to travel. Setting this to 1 is a good way to drive off just about everyone from your server.

As far as I can tell, 1000ms is allowed by default in the game, so setting this to any value higher than 39 should have no effect if sv_fps is set to 10.

'''Type:''' integer

'''Default:''' 4

= Miscallenous =

== g_realPlayTime ==

'''Description:'''

Show additional real play time of the payer (without spec time) in the debriefing screen at the end of the map.
For instance: 6/10 would mean that player played 6 minutes, was on the server for 10 minutes and 4 minutes was in spec.

'''Type:''' [0|1]

'''Parameters:'''

'''Default:''' 1

'''Minimum required version:''' 0.6.0

== g_extraStatistics ==

'''Description:'''

Additional statistics over the end game awards.

'''Type:''' bitmask

'''Parameters:'''

1 Player with most mine kills

2 Player with most mine damage inflicted

4 Player with most knife kills

8 Player with most gibs

16 Player with most artillery kills

32 Player with most airstrike kills

'''Default:''' 0

== g_packDistance ==

'''Description:'''

Set the distance at which health packs and ammo packs are thrown. Set this to 0 to make it just like etmain. The settings should be similar to shrubet so set this to 2 for a subtle improvement.

'''Type:''' integer

'''Default:''' 0

== g_dropHealth ==

'''Description:'''

If set to a positive integer, medics will drop [integer] number of health packs when they are gibbed. If set to -1, medics will drop the number of health packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_dropAmmo ==

'''Description:'''

If set to a positive integer, fieldops will drop [integer] number of ammo packs when they are gibbed. If set to -1, fieldops will drop the number of ammo packs that they could have dropped at the moment of their death. Set this to 0 to turn it off.

'''Type:''' integer

'''Default:''' 0

== g_tossDistance==

'''Description:'''

Set the velocity at which health or ammo packs are tossed from the dead body when g_dropHealth or g_dropAmmo are activated. This changes the distance that these packs travel from the corpse.

'''Type:''' integer

'''Default:''' 0

== g_intermissionTime ==

'''Description:'''

Set the length of time the end of game screens displays before loading the next map.

'''Type:''' integer

'''Default:''' 60

== g_intermissionReadyPercent ==

'''Description:'''

The percent of connected players who need to hit the "READY" button to move on to the next map without waiting g_intermissionTime to run out.

'''Type:''' integer

'''Default:''' 100

== g_skills ==

'''Description:'''

Optional skill related flags.

'''Type:''' bitmask

'''Parameters:'''

1 Players with level 4 battle sense can spot landmines for teammates

2 Players with level 4 engineering can keep the flak jacket for other classes

4 Players with level 4 first aid can keep adrenaline for other classes

'''Default:''' 0

== g_misc==
'''Description'''

Miscallenous options.

'''Parameters'''

Type: '''bitmask'''

1 Enable double jump.

2 Enable binoc master competition. Requires g_weapons 64 to be set.

4 When a player is killed he can see the HP the killer has left.

8 Disable self damage.

16 Players can not jump if stamina is too low.

32 Enable Jaymod style doublejump.

64 Disable Falling Damage.

128 Announce revives.

256 Setting this flag disables the "First Blood" announcement.

512 Full body predict. This makes it harder to get inside for example walls and stones. Same as ETPub g_misc 32 + 256. Do note that this can cause problems when proning through windows and similar narrow passages

'''Default:''' 0

== g_moverScale ==

'''Description:'''

Multiply the speed of movers (e.g. tanks) by float.

'''Type:''' float

'''Default:''' 1.0

== g_slashKill==

'''Description:'''

Controls the behavior of the /kill command. See also g_fear and g_maxSelfkills.

'''Type:''' bitmask

'''Parameters:'''

1 Player spawns with half charge bar after /kill

2 Player spawns with 0 charge bar after /kill

4 Restores the charge bar to the same state it was in at the moment the player issued /kill (regardless of how long they were in limbo)

8 Disable /kill when player is frozen

16 Disable /kill when player is poisoned

'''Default:''' 0

== g_maxSelfkills ==

'''Description:'''

Amount of times a player can use /kill per map. Setting this to -1 will result in normal behaviour (infinite selfkills). Setting this to 0 will disable /kill.

'''Type:''' integer

'''Default:''' -1

== g_ammoCabinetTime ==

'''Description:'''

The time between ammo cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 60000

== g_healthCabinetTime ==

'''Description:'''

The time between health cabinet regenerations in milliseconds.

'''Type:''' integer

'''Default:''' 10000

== g_spectator==

'''Description:'''

Controls spectator behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 When in freelook mode, you can 'fire' at a player to follow. If you miss a player, nothing happens.

2 When in freelook mode with the 1 flag set, if you shoot and miss you start following the next available player.

4 When the player you're following goes into limbo, don't move to the next available player.

8 When the player you're following goes into limbo, go to freelook instead of following the next available player. (4 has precedence)

'''Default:''' 0

== g_truePing ==

'''Description:'''

Allows players to see the true amount of time it takes until their actions are processed on the server. Pings will show around 50 ms higher than normal, but it's more accurate. Shows in the scoreboard.

'''Type:''' [0|1]

'''Default:''' 0

== g_dropObj ==

'''Description:'''

Sets the number of times a player can drop/toss the objective (e.g. parts on radar) per life.

The parts are dropped by pressing the +activate key (usually bound to F) when there's nothing else around to be activated.

Before enabling this recall how spammy the voiceovers can be. Then picture a player tossing the parts to himself over and over again. For this reason you probably don't want to set this very high.

Players must switch to knife in order to drop the objective. If they are not holding knife and hit +activate they will see a message that notifies them that they must switch to knife. This change was made to prevent accidental dropping of the objective when trying to push, drag, pick up, or activate something else.

'''Type:''' integer

'''Default:''' 0

== g_doubleJumpHeight ==

'''Description:'''

Adjusts the height of the second jump in a double jump. This value is a multiplier to the default jump velocity. The greater g_doubleJumpHeight is, the greater the height of the second jump. This setting has no effect if double jump is disabled in g_misc.

'''Type:''' float

'''Default:''' 1.4

== g_serverInfo==

'''Description:'''

Use this cvar to change the behaviour of the 'serverinfo' string. This string is printed in response to the 'getstatus' primative command used by game browsers.

'''Type:''' bitmask

'''Parameters:'''

1 Display player team information using the 'P' cvar in the server info string. (etpro and etmain 2.60 behaviour)

2 Display player team information using the 'Players_Axis' and 'Players_Allies' cvars in the server info string. (etmain < 2.60 behaviour)

4 Display the 'campaign_maps' cvar in the server info string. This contains a comma delimited list off all the maps in the current campaign. Only works if you have g_gametype set to 4.

8 Displays the 'C' CVAR in the server info string. This is a string containing the current map number in the campaign, and total maps in current campaign, in the form of "xx,yy". Only works if you have g_gametype set to 4.

16 The class charge times will not be present in the server info string unless this flag is set. They are removed by default in order to make room in the serverInfo string for more useful information. These cvars are g_medicChargeTime, g_engineerChargeTime, g_LTChargeTime, g_covertopChargeTime, g_soldierChargeTime.

32 Send KR (KillRating) instead of XP in SERVERINFO string. This is overriden by flag 64.

64 Send PR (PlayerRating) instead of XP/KR in SERVERINFO string. Overrides flag 32.

'''Default:''' 1

'''Note:'''

This cvar MUST be set prior to loading the first map. You will not be able to change this cvar once the game code is loaded. The serverInfo string has a fixed length of 1024 characters. This space is shared with any cvar you create on your server with the 'sets' command. If you use up too much space with 'sets', your server will fail to start. It will print the message "Info string length exceeded" if you don't have enough space left in your serverinfo string to handle the g_serverInfo flags you've selected. To fix this, either remove some sets cvars from your config, or use different g_serverInfo flags.

== g_fear ==

'''Description:'''

If a player uses the /kill command within g_fear milliseconds after taking damage from an enemy, the attacker that last damaged that player will recieve full credit for the kill and the mode of death will be recorded as MOD_FEAR. Other restrictions are that the attacker must be on the opposite team and the attacker must still be alive.

G_fear applies also to players that try to switch teams within g_fear milliseconds. The player will remain in the same team and the usual g_fear behavior applies.

In-game statistics will reflect that the death was caused by the weapon that did the last recorded damage to the player.

Set this to 0 to disable this behaviour.

'''Type:''' integer

'''Default:''' 2000

== g_inactivity ==

'''Description:'''

The number of seconds of player inactivity before the player is made a spectator.

'''Type:''' integer

'''Default:''' 0

== g_spectatorInactivity==

'''Description:'''

The number of seconds of player inactivity as spectator before the player is kicked/dropped from server.

'''Type:''' integer

'''Default:''' 0

== g_gametype ==

'''Description:'''

Please see Map Voting.

'''Type:''' [2|3|4|5|6|7]

'''Parameters:'''

2 Objective

3 Stopwatch

4 Campaign

5 Last Man Standing

6 Map Voting

7 Team Death Match

'''Default:''' 4

== g_spoofOptions ==

'''Description:'''

Options for PunkBuster GUID and IP spoof detections and behaviour.

'''Type:''' bitmask

'''Parameters:'''

1 Kick for GUIDspoofing.

2 Kick for IPspoofing.

4 Display a global warning when someone is GUIDspoofing. (When flag 1 is set, this will not work)

8 Display a global warning when someone is IPspoofing. (When flag 2 is set, this will not work)

16 Don't use the stored GUID. (This option is a higher security risk.)

32 Don't use the stored IP. (This option is a higher security risk.)

'''Default:''' 3

'''Note:'''

Do NOT change this CVAR unless you encounter problems!

== g_maxNameChanges ==

'''Description:'''

Limit the number of namechanges per player per map by setting this cvar. This is especially needed if you have cheaters that autochange their name every second. Set to -1 to disable.

'''Type:''' integer

'''Default:''' 3

== g_disableComplaints ==

'''Description:'''

Disable teamkill complaints for some weapons.

'''Type:''' bitmask

'''Parameters:'''

1 Landmines

2 Artillery and airstrikes

4 Mortar

8 Dynamite

'''Default:''' 0

== g_watermark==

'''Description:'''

Set a watermark that will be displayed to all clients. The watermark must be put in a folder named "watermark" and then this whole folder needs to be zipped into a .pk3 file. The silEnT watermark is "logo_silent.tga".

'''Type:''' string

'''Default:''' ""

== g_watermarkFadeAfter ==

'''Description:'''

When g_watermark is set, the watermark will fade out after [integer] number of seconds.

'''Type:''' integer

'''Default:''' 0

== g_watermarkFadeTime ==

'''Description:'''

When g_watermarkFadeAfter is set, the watermark will fade out in [integer] seconds. (So the fading process from 1.0 alpha to 0.0 alpha takes [integer] seconds.

'''Type:''' integer

'''Default:''' 0

== g_panzerwar==

'''Description:'''

Enables/Disables Panzerwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_sniperwar ==

'''Description:'''

Enables/Disables Sniperwar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_riflewar ==

'''Description:'''

Enables/Disables Riflewar. 1 is enabled, 0 is disabled.

'''Type:''' [0|1]

'''Default:''' 0

== g_countryFlags ==

'''Description:'''

Sets whether the players will see the GeoIP country flags in the crosshair when aiming at someone and in the scoreboard. Players can enable/disable it with cg_countryFlags (default 1).

You will need the GeoIP.dat file in your server's silent folder. You should read and accept the license of the GeoIP.dat database!

Read the database license at http://geolite.maxmind.com/download/geoip/database/LICENSE.txt
Download the latest database at http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz

'''Type:''' [0|1]

'''Default:''' 1

== g_noSkillUpgrades==

'''Description:'''

When set to 1, disables player skill upgrades.

'''Type:''' [0|1|2]

0 No skill locking.

1 Lock skills.

2 Lock skills and hide all HUD elemnts that would show the skill levels.

'''Default:''' 0

'''Change Log:'''

Starting from silEnT version 0.6.0, this cvar will lock the skills to the always enabled levels. See the skill_x cvars. Also, it is possible to hide the skill levels from the player HUDs setting this cvar to value 2.

== g_flushItems ==

'''Description:'''

Evens the dropped items out with the surface.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxConnsPerIP ==

'''Description:'''

Maximum number of connections allowed from one particular IP. This prevents the fake clients Denial of Service attack.

'''Type:''' integer

'''Default:''' 4

== shoutcastPassword ==

'''Description:'''

Enables shoutcaster status on the server.

'''Type:''' string

'''Default:''' "none"

== g_headshot==

'''Description:'''

Controls additional head shot options.

'''Type:''' bitmask

'''Parameters:'''

1 Headshots only

2 Instagib damage (controlled by g_instagibDamage)

'''Default:''' 0

== g_instagibDamage ==

'''Description:'''

Damage used for instagib mode (e.g. set this to 160 so that a player can still be revived after being shot.).

'''Type:''' integer

'''Default:''' 400

== g_inactivityOptions ==

'''Description:'''

Controls additional inactivity options.

'''Type:''' bitmask

'''Parameters:'''

1 Don't drop shoutcasters

2 Don't drop spectators when in following mode

4 ETmain inactivity behavior (don't wait for a full server)

8 Shrubbot flag '0' admins will be moved to spectators due to team inactivity

'''Default:''' 3

== g_ettvFlags ==

'''Description:'''

Controls additional ETTV options.

'''Type:''' bitmask

'''Parameters:'''

1 Prevent ettv slaves from being callvote kicked

2 Grant shoutcaster status to ettv slaves

'''Default:''' 3

== g_mode==

'''Description:'''

Controls some additional modes for fun or for testing.

'''Type:''' bitmask

'''Parameters:'''

1 Players will spawn instantly

2 Each class receives adrenaline

4 No damage on players

8 Players can pick up any weapon on the ground (Removing this bitflag will force all players to respawn!)

'''Default:''' 0

== g_hitsounds ==

'''Description:'''

Server side hitsound options.

'''Type:''' bitmask

'''Parameters:'''

1 Enable hitsounds

2 Disable hitsounds when shooting wounded players

4 Disable the headshot sound when shooting wounded player in the head. (default hitsound will be used in it's place)

8 Enable warning sound from hitting team mates

16 Disable hitsounds from poison damage

32 Disable hitsounds from explosive weapons

'''Default:''' 1

'''Note:'''

A client can disable hitsounds with cg_hitSounds client cvar. Also an option to play only headshots is available.

== g_playDead ==

'''Description:'''

Allows players to use the 'playdead' command and their character will act like it is dead until the playdead command is used again (or they really die).

'''Type:''' [0|1]

'''Default:''' 0

== g_shove ==

'''Description:'''

Allows players to push other players with the "use" key. The integer adjusts the amount of force players shove with. 80 seems fair.

'''Type:''' integer

'''Default:''' 80

== g_shoveNoZ==

'''Description:'''

Set this to 1 if you want to disable shove in the up/down direction (a.k.a "boosting").

'''Type:''' [0|1]

'''Default:''' 1

== g_dragCorpse ==

'''Description:'''

Allows players do drag wounded players with the use key when moving backward slowly. Works best when crouching or prone.

'''Type:''' [0|1]

'''Default:''' 0

== g_classChange ==

'''Description:'''

Allows players to take the class of a gibbed teammate temporarily similarly to how a covert steals an uniform. Class changing does not latch, so the original class the player had will be restored on respawn.

'''Type:''' [0|1]

'''Default:''' 0

== g_forceLimboHealth ==

'''Description:'''

If set to 0 it takes about 3 shots to gib a wounded player, if set to 1 it takes about 5.

'''Type:''' [0|1]

'''Default:''' 1

== g_goomba==

'''Description:'''

If set to a positive integer, players can damage each other by landing on each other. The integer is multiplier that determines how much damage should be done to the player that was fallen on. Also the impact for the falling player will be broken so that they only recieve 20% of the damage they would have normally. It is also possible to do small amounts of damage (5HP) to other players by hopping up and down on them.

Falling damage can be either 500, 50, 25, 15, or 10 depending on the length of the fall. So if you set g_goomba to 5 and land on a player from a fall that would have damaged you 10HP, you will inflict 50HP of damage on the player you land on, and you will only recieve 2HP of damage.

See also g_goombaFlags

Set this to 0 to disable it

'''Type:''' integer

'''Default:''' 0

== g_goombaFlags ==

'''Description:'''

Controls the way g_goomba is handled.

'''Type:''' bitmask

'''Parameters:'''

1 Cannot do goomba damage to teammates.

2 Short falls (hopping) on another player does no damage.

4 Short falls (hopping) does no damage to teammates. (not necessary if 1 or 2 flag is set)

8 Falling player recieves no damage when landing on any other player. (default is to recieve 20% of the damage the fall would have given if not landing on a player).

16 Insta-gib goomba. All goomba damage will be 500HP regardless of fall distance. The exception is hopping on anther player which still does 5HP of damage.

32 Falling corpses won't cause damage.

'''Default:''' 0

'''Note:'''

Set this to 31 to have g_goomba work like shrubet.

== g_spawnInvul ==

'''Description:'''

The number of seconds players will be invincible after they spawn.

'''Type:''' integer

'''Default:''' 3

== g_spawnInvulFair ==

'''Description:'''

Removes the spawn protection when the player fires his first shot (note : the spawn protection will still be removed after the g_spawnInvul time)

'''Type:''' [0|1]

'''Default:''' 1

== g_spinCorpse==

'''Description:'''

Allow players to use +left and +right binds to spin their corpse when dead or playing dead.

'''Type:''' [0|1]

'''Default:''' 0

== g_teamChangeKills ==

'''Description:'''

If set to 0, players are allowed one non-killing team change per respawn cycle. If a player changes teams, he will be instantly spawned in the other teams default spawn point. Players will die (but not lose a life) if they change teams a second time in one spawn cycle.

'''Type:''' [0|1]

'''Default:''' 1

== g_maxIgnoresPerMap ==

'''Description:'''

he maximum number of times one player can ignore another player during one map. This can prevent spamming other players with the ignore command. The value can be between 0 and 255. Any value higher then 255 will always allow ignoring. Any value below 1 will disable ignoring completely.

'''Type:''' Integer

'''Default:''' 2

'''Minimum required version:''' 0.7.0

== g_min_crazyspeed ==

'''Description:'''

Set minimum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 200

'''Minimum required version:''' 0.7.0

== g_max_crazyspeed ==

'''Description:'''

Set maximum speed for !crazyspeed command.

'''Type:''' Integer

'''Default:''' 540

'''Minimum required version:''' 0.7.0

== g_min_crazygravity ==

'''Description:'''

Set minimum speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 10

'''Minimum required version:''' 0.7.0

== g_max_crazygravity ==

'''Description:'''

Set max speed for !crazygravity command.

'''Type:''' Integer

'''Default:''' 1200

'''Minimum required version:''' 0.7.0

= Logs =

== g_logOptions==

'''Description:'''

This is meant to match the shrubmod g_logOptions cvar, but so far the only implemented flags are:

'''Type:''' bitmask

'''Parameters:'''

1 Server outputs obituaries to chat.

2 Adrenaline countdown displayed.

4 Disable display of tap-out confirmation box.

8 Display connection attempts by banned players.

16 Display gib reports ("<victim> was gibbed by <attacker>").

32 Omit "item" lines from log file.

64 Report gibs.

128 GUID's are logged in the game log. Note, if this option is enabled the VSP log parser will not work.

256 Log all private messages (/m commands). This setting won't have any effect unless g_tyranny is enabled.

512 Logs the real time into logs, instead of the normal uptime of the server.

1024 This flag allows logging every player drop. It can be usefull for inspecting the server operation, but it will also cause lot of needless log writes.

2048 Print TK death message like a normal kill message, giving killing weapon, except it is preceeded by a red TEAMKILL: identifier. Only works if g_obituary is set to 3.

4096 Log client cvar values.

8192 Log cvar values only when found from the client. Note that flag 4096 must also be set if using this flag.

'''Default:''' 0

'''Change log:'''

0.6.3 - Flags 4096 and 8192 were added.

== g_logAdmin==

'''Description:'''

The name of the file that all shrubbot commands will be logged to. For example, g_logAdmin "admin.log".

'''Type:''' string

'''Default:''' ""

= Omni-Bots =

== omnibot_enable ==

'''Description:'''

When set to 1, Omni-bot functionality is enabled. You still need to have Omni-bots installed correctly in order for the bots to work.

'''Type:''' [0|1]

'''Default:''' 1

== omnibot_path ==

'''Description:'''

The path where the Omni-bot dll/so file is installed. If you installed Omni-bot to the default locations, then you do not need to modify this cvar. Leaving this cvar blank will search for the Omni-bot dll/so file from the default locations.

'''Type:''' string

'''Default:''' ""

== g_bot_maxXP ==

'''Description:'''

Any bots present will have their XP reset after this much XP is reached. If g_maxXP is also set to a value greater than -1, then the bot XP will be reset whenever the lower limit of the two is hit. Set this to -1 to disable this feature

'''Type:''' integer

'''Default:''' -1

== omnibot_flags==

'''Description:'''

Customizes bot management/behavior.

'''Type:''' bitmask

'''Parameters:'''

1 Disables XPSave for bots

2 Bots cannot mount tanks

4 Bots cannot mount emplaced guns

8 Don't track bot count in omnibot_playing cvar

16 Bots will target ungibbed enemies

32 Bots will trigger team and spotted mines

64 Bots can use g_shove

65536 Bots are granted shrubbot command immunity (the same as shrubbot flag !)

131072 Bots cannot be !kicked or !banned

262144 Disable shrubbot greeting for bots

'''Default:''' 0

= Lua =

== lua_modules==

'''Description:'''

List of files to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. The paths are relative to the mod's directory, and can optionally be placed inside pk3 archieves. We are aiming for compatibility with ETPro's Lua Mod API found at http://wolfwiki.anime.net/index.php/Lua_Mod_API.

'''Type:''' string

'''Default:''' ""

== lua_allowedModules==

'''Description:'''

List of sha1 signatures for the lua modules to be loaded by the Lua API engine. Can be separated by space, comma or semicolon. Only lua modules with the matching sha1 signature listed in this cvar will be allowed to load by the Lua API engine (ACL).

'''Type:''' string

'''Default:''' ""