Silent Mod Server Cvar: Difference between revisions
Hellreturn (talk | contribs) No edit summary |
Hellreturn (talk | contribs) No edit summary |
||
| Line 118: | Line 118: | ||
== g_floodprotect == | == g_floodprotect == | ||
'''Description:''' | '''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 == | == g_floodthreshold == | ||
Revision as of 20:45, 14 September 2011
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 ( [revive] blocks )
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_settings
Description:
This should be set to the name of your settings.cfg file if you want to enable banners. See settings documentation for more information about this file.
Type: string
Default: ""
Example:
set g_settings "settings.cfg"
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