Test: Difference between revisions

Latest revision as of 22:49, 22 January 2011

**blabla**
test	test	test
g_privateMessages	g_spreeOptions	in voluptate velit
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

@@ Line 3: / Line 3: @@
 ! test || test || test
 |-
-| [[test#g_dbUserMaxAge|g_dbUserMaxAge]]  || in reprehenderit || in voluptate velit
+| [[test#g_privateMessages|g_privateMessages]]  || [[test#g_spreeOptions|g_spreeOptions]] || in voluptate velit
 |-
-| esse cillum dolore || eu fugiat nulla || pariatur.
+| test || blabla || unz unz.
 |}
@@ Line 12: / Line 12: @@
+==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
-[[Client_Manual#Autoexec_Files|to some extent allowed]]
-Client_Manual#Autoexec_Files
-==g_dbUserMaxAge==