Server Manual: Difference between revisions

From MyGamingTalk
No edit summary
No edit summary
Line 1: Line 1:
{| class="wikitable" style="margin: 1em auto 1em auto"
{| class="wikitable" style="margin: 1em auto 1em auto"
|+ '''blabla'''
|+ '''Announcements and Messages'''
! test || test || test || test
|-
|-
| [[Server_Manual#g_privateMessages|g_privateMessages]]  || [[Server_Manual#g_spreeOptions|g_spreeOptions]] || [[Server_Manual#g_multikillTime|g_multikillTime]] || [[Server_Manual#g_obituary|g_obituary]]
| [[Server_Manual#g_privateMessages|g_privateMessages]]  || [[Server_Manual#g_spreeOptions|g_spreeOptions]] || [[Server_Manual#g_multikillTime|g_multikillTime]] || [[Server_Manual#g_obituary|g_obituary]]

Revision as of 22:56, 22 January 2011

Announcements and Messages
g_privateMessages g_spreeOptions g_multikillTime g_obituary
test blabla unz unz.



g_privateMessages

g_privateMessages [0|1]
If set to 1, players can send private messages to one another with the m command. Example:
/m tjw you totally suck!
Clients can reject private message from other individual clients with the /ignore client command.
Default is 0

g_spreeOptions

g_spreeOptions [bitmask]
A few options to control the display of killingsprees. Note that the flags 1, 2 and 4 are just made for fast enabling / disabling and :still require a g_settings file.
1
Enable killingsprees ([spree] blocks)
2
Enable killingspree ends ([end] blocks)
4
Enable multikills ([kill] blocks)
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 is 0

g_multikillTime

g_multikillTime [integer]
The time (in milliseconds) in which two kills should be made in order to count them as multikills.
Default is 1000

g_obituary

g_obituary [0|1]
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.
Default is 1