Silent Mod Server Cvar: Difference between revisions
Hellreturn (talk | contribs) |
Hellreturn (talk | contribs) |
||
| Line 16: | Line 16: | ||
'''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 '/'. | '''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 == | == g_spreeOptions == | ||
'''Description:'''<br>Options to control the display of killingsprees. | |||
<br>'''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 == | == g_multikillTime == | ||
Revision as of 20:06, 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