WolfWiki - User contributions [en]

ETPro:Pluggable Config Files

2006-11-17T00:53:40Z

Fusen: edited sig example config info

ETPro supports '''Pluggable Config Files'''. These files provide servers the use of additional features not available from traditional <tt>.cfg</tt> files.

==Creation and Installation==
Config files must be located in <tt>etpro/configs</tt> and their names must end in <tt>.config </tt>

==Config file format==
The following shows the .config syntax. This is not a complete config, the ... indicates that in a real config many similar commands would follow

configname "^/foobar^f 6v6"
// config for 6v6 foobar league
version 1.2.3.4 foobar6v6.version.foobarleague.com
init
{
setl sv_pure 1
setl sv_cheats 0
setl g_gametype 3
...
command "pb_sv_enable"
command "pb_sv_kicklen 1"
command "pb_sv_cvarempty"
...
}
map default
{
set g_userTimeLimit 0
setl g_useralliedrespawntime 0
setl g_useraxisrespawntime 0
setl b_moverscale 1
}
map radar
{
set g_userTimeLimit 12
command "forcecvar r_drawfoliage 0"
mapscripthash <hash>
}
...
signature <40 char sha1 hash>
===Config file details===
;comments : any text following // is a comment and is ignored

;version w.x.y.z some.dns.name : ET will check that version matches the IP returned form some.dns.name If it does, ETPro displays the message "config is latest version available" to all players in warmup. '''not fully implemented''' - etpro doesn't currently do the DNS check.

;configname <name> : defines the name of the config. This name is displayed to players in warmup, but is '''not''' used to refer to the config in config related commands. The name may contain ET [[Color Codes]]

;init : The init block is executed only once, when the config is loaded by referee or rcon/console. It is never reloaded.

;map <mapname>|default : The map blocks are loaded on every map_restart. The parameter is the mapname to match to. A parameter of default will execute that block for all maps. map blocks are executed in order from first to last. Generally you want your default block first, and then specific map blocks to override it.

;signature <sig> : provides crypotgraphic signature to verify that that the config is unmodified. ETPro displays the message "config is certified" to all players in warmup. The signature must be generated by the etpro team.

'''init''' and '''map''' are followed by a block, delimited by curly braces {}. Each block can contain the following keywords

;set <cvarname> "value" : sets the specified cvar to the specified value.
;setl <cvarname> "value" : sets the specified cvar to the specified value, and locks it so that it cannot be changed by rcon, forcecvar or other means until the config is unloaded
;command "command text" : execute "command text"
;mapscripthash <hash> : Require a particular mapscript be used for a map. Must appear in a non-default map section. The hash can be found by loading the map and checking the value of the readonly server cvar b_mapscripthash. If the mapscript does not match when the map is loaded, a message will be sent to all players, and the config will be unloaded.

==Config related commands==
;callvote | ref config <config file name> : set the current config by vote or ref.
;config <config file name>|none : set the current config from the server console, or unload the current config. Settings set by the config remain in effect, but are no longer locked. Map specific blocks are no longer in effect.
''notes'':
:*<tt>config none</tt> can only be used from the console (or rcon) not ref or vote.
:*you must use the filename of the .config (minus the .config extension), not the 'configname' contained in the .config file. The 'configname' is a longer (possibly colored etc) descriptive name.
:*'''do not''' try to load a config with <tt>set config <configname></tt>. This will cause the <tt>config</tt> and <tt>ref config</tt> commands to stop working until the server is restarted.

==Common pitfalls to watchout for==
*Any cvar that isn't a number (vote_allow_config, b_watermark, b_levels_medic etc) must have quotes around it's value, even if its value is a single character.
*XP levels lists should not have commas in them (b_levels_medic etc)
*Putting cvars in groups alphabetically as above makes it a lot easier to maintain and verify.
*Make sure there is an extra newline at the end of the file (after the closing '}')
*Test your <tt>.config</tt> - you can do this simply by putting it in your /etpro/configs directory, and starting ET with <tt>+set dedicated 2 +exec server.cfg</tt>, then calling the <tt>.config</tt> with <tt>/config NAME</tt>. The console will report any major syntax errors in the <tt>.config</tt>
*Make sure to include all relevant gameplay-related cvars. Most are included in [http://bani.anime.net/banimod/forums/viewtopic.php?t=4558#43204 this list].

==Getting Your Configuration Certified==
The easiest way is to send a private message to [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=2 bani] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=800 Rain] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=1462 zinx] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=761 ReyalP] with the URL using the [http://bani.anime.net/banimod/forums/privmsg.php?folder=sentbox ETPro forums], including a link to the <tt>.config</tt> hosted on the league's website.

An alternate way, if the first way fails, is to talk to one of the [[ETPro Developer]]s on [[IRC]].

==See also==
*[[Cvar Restrictions]]
*[[Forced Cvars]]
*[[WolfWiki:Community_Portal#Leagues / Competitions]] is a good place to find full config file examples.

[[Category:ETPro]]

ETPro:Pluggable Config Files

2006-11-17T00:52:02Z

Fusen: added mapscripthash example to example config

ETPro supports '''Pluggable Config Files'''. These files provide servers the use of additional features not available from traditional <tt>.cfg</tt> files.

==Creation and Installation==
Config files must be located in <tt>etpro/configs</tt> and their names must end in <tt>.config </tt>

==Config file format==
The following shows the .config syntax. This is not a complete config, the ... indicates that in a real config many similar commands would follow

configname "^/foobar^f 6v6"
// config for 6v6 foobar league
version 1.2.3.4 foobar6v6.version.foobarleague.com
init
{
setl sv_pure 1
setl sv_cheats 0
setl g_gametype 3
...
command "pb_sv_enable"
command "pb_sv_kicklen 1"
command "pb_sv_cvarempty"
...
}
map default
{
set g_userTimeLimit 0
setl g_useralliedrespawntime 0
setl g_useraxisrespawntime 0
setl b_moverscale 1
}
map radar
{
set g_userTimeLimit 12
command "forcecvar r_drawfoliage 0"
mapscripthash <hash>
}
...
signature deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
===Config file details===
;comments : any text following // is a comment and is ignored

;version w.x.y.z some.dns.name : ET will check that version matches the IP returned form some.dns.name If it does, ETPro displays the message "config is latest version available" to all players in warmup. '''not fully implemented''' - etpro doesn't currently do the DNS check.

;configname <name> : defines the name of the config. This name is displayed to players in warmup, but is '''not''' used to refer to the config in config related commands. The name may contain ET [[Color Codes]]

;init : The init block is executed only once, when the config is loaded by referee or rcon/console. It is never reloaded.

;map <mapname>|default : The map blocks are loaded on every map_restart. The parameter is the mapname to match to. A parameter of default will execute that block for all maps. map blocks are executed in order from first to last. Generally you want your default block first, and then specific map blocks to override it.

;signature <sig> : provides crypotgraphic signature to verify that that the config is unmodified. ETPro displays the message "config is certified" to all players in warmup. The signature must be generated by the etpro team.

'''init''' and '''map''' are followed by a block, delimited by curly braces {}. Each block can contain the following keywords

;set <cvarname> "value" : sets the specified cvar to the specified value.
;setl <cvarname> "value" : sets the specified cvar to the specified value, and locks it so that it cannot be changed by rcon, forcecvar or other means until the config is unloaded
;command "command text" : execute "command text"
;mapscripthash <hash> : Require a particular mapscript be used for a map. Must appear in a non-default map section. The hash can be found by loading the map and checking the value of the readonly server cvar b_mapscripthash. If the mapscript does not match when the map is loaded, a message will be sent to all players, and the config will be unloaded.

==Config related commands==
;callvote | ref config <config file name> : set the current config by vote or ref.
;config <config file name>|none : set the current config from the server console, or unload the current config. Settings set by the config remain in effect, but are no longer locked. Map specific blocks are no longer in effect.
''notes'':
:*<tt>config none</tt> can only be used from the console (or rcon) not ref or vote.
:*you must use the filename of the .config (minus the .config extension), not the 'configname' contained in the .config file. The 'configname' is a longer (possibly colored etc) descriptive name.
:*'''do not''' try to load a config with <tt>set config <configname></tt>. This will cause the <tt>config</tt> and <tt>ref config</tt> commands to stop working until the server is restarted.

==Common pitfalls to watchout for==
*Any cvar that isn't a number (vote_allow_config, b_watermark, b_levels_medic etc) must have quotes around it's value, even if its value is a single character.
*XP levels lists should not have commas in them (b_levels_medic etc)
*Putting cvars in groups alphabetically as above makes it a lot easier to maintain and verify.
*Make sure there is an extra newline at the end of the file (after the closing '}')
*Test your <tt>.config</tt> - you can do this simply by putting it in your /etpro/configs directory, and starting ET with <tt>+set dedicated 2 +exec server.cfg</tt>, then calling the <tt>.config</tt> with <tt>/config NAME</tt>. The console will report any major syntax errors in the <tt>.config</tt>
*Make sure to include all relevant gameplay-related cvars. Most are included in [http://bani.anime.net/banimod/forums/viewtopic.php?t=4558#43204 this list].

==Getting Your Configuration Certified==
The easiest way is to send a private message to [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=2 bani] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=800 Rain] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=1462 zinx] or [http://bani.anime.net/banimod/forums/profile.php?mode=viewprofile&u=761 ReyalP] with the URL using the [http://bani.anime.net/banimod/forums/privmsg.php?folder=sentbox ETPro forums], including a link to the <tt>.config</tt> hosted on the league's website.

An alternate way, if the first way fails, is to talk to one of the [[ETPro Developer]]s on [[IRC]].

==See also==
*[[Cvar Restrictions]]
*[[Forced Cvars]]
*[[WolfWiki:Community_Portal#Leagues / Competitions]] is a good place to find full config file examples.

[[Category:ETPro]]

ETTV:Viewer's Guide

2006-08-31T10:45:54Z

Fusen: it mentions replaying on local windows machine yet talks about the linux so files?

== ETTV Viewer's Guide ==
=== Introduction ===
ETTV is a modification that allows anybody to spectate Enemy Territory matches without actually being on the server the teams are playing on. The purpose is so that you have have thousands of people all able to watch an exciting match live, without being able to interfere or otherwise cause problems with the match.

The ETTV modification is supplied within the ETPro modification, you do not need any further modification unless you intend to run an [[ETTV:Server_Configuration|ETTV Server]].

=== Watching ETTV ===
Simply connect to an ETTV server like any other Enemy Territory server. Once you are connected it will look and feel very much like you are in spectator mode on any normal server.

There are some issues which occur frequently enough to make it worth noting here, however.

* ETTV servers frequently do not allow clients (that's you/your game) to auto-download any missing files. You should try to ensure you '''have the correct patch, modification and custom map versions before you join'''. This is usually, but not necessarily the latest official version. If you do not have the correct versions you may be unable to join, or disconnected at some point during viewing.

* '''Do not be concerned about interfering with the match''', you cant. The ETTV server you join is essentially playing a live demo of the match which is actually being played on another server. You can spectate freely and talk crap with the other viewers on the same ETTV server, thats it. Chat from ETTV viewers is distinguished from chat in the match by the red "ETTV" preceding it.

* '''Connecting via IP address''' (command-line or console) is identical to any other Enemy Territory server. If you've been given the IP address of an ETTV server and are wondering what to do with it, open the console (usually by pressing the key under ESCape, often the ~ or ` key) and use the following command (including the forwardslash) - <tt>/connect ip.add.ress:port</tt>
:(for example: <tt>/connect 62.75.178.112:27962</tt>)

=== Additional Controls ===
* cycle between everybody on the server (who shows up on the scoresheet)
:fire <tt><Left Mouse button></tt>
* cycle following only objective carriers
:Prone + (fire / altweapon) <tt><X + LeftMouse></tt>
* cycle following only spectators / shoutcasters
:Zoom + (fire / altweapon) <tt><nowiki></nowiki></tt>
* Jump directly to following a player in view
: Press activate while pointing crosshair at player
* return to free floating mode.
: Press jump or activate <tt><Spacebar></tt>

=== Generally Useful Tips ===
* Chats from other ETTV spectators can be hidden with the console command <tt>/tvchat off</tt>, and re-enabled with <tt>/tvchat on</tt>. All chat done on ETTV won't be seen on the game server (luckily). If certain chatters start to irritate you, you can easily ignore specific people with the <tt>/ignore</tt> command and can use the <tt>/unignore</tt> command to show their chat messages again.

* To spectate a specific player through their eyes, open console and put in the command <tt>/players</tt>, and notice the player number. Now just <tt>/follow x</tt>. If you're new to Enemy Territory, you might find it most entertaining to follow a shoutcaster, if there is one.

* Viewing ETTV in a window can be convenient while you find other IP's, talk in IRC, or access WinAmp, for example. To do this, you can go to the options screen and set a resolution which is smaller than your desktop screen resolution, and then select windowed mode. Alternatively, enter <tt>/r_mode 3</tt> into console, and then hit ALT+Enter.

* Normal cvar restrictions dont apply when viewing demos, nor do they (usually) when viewing ETTV. This is OK because you're not playing against anyone. Several leagues remove the foliage (all the grassy stuff) on Radar because it hurts performance and, some say, isnt good for competitive gaming. As an ETTV viewer you can remove it via console: <tt>/r_drawfoliage 0</tt>. To further incrase performance you can remove wolffog (an effect which "adds" fog to the map, sometimes restricting the viewing distance [e.g. Railgun]) by setting <tt>r_wolffog 0</tt>. You might want to ensure that is reset to 1 before you join a normal gameserver however.

* ETTV is generally not live; normally a few minute long delay is added so competing teams cannot have another member watching and sending participants advantagous information.

== Shoutcasts ==
A [http://en.wikipedia.org/wiki/Shoutcast shoutcast] is essentially a match commentary, broadcast over something akin to internet radio. The shoutcaster is usually someone heavily involved with the ET community and listening to the shoutcast greatly enhances the entertainment value of ETTV.

A shoutcast is completely seperate from ETTV however, to listen to a shoutcast you will need to open the URL with a suitable program - [http://winamp.com/ WinAmp] being one of many such programs. The shoutcast URL is often available at the same place you found the ETTV details for the match you want to watch.

Like ETTV, shoutcasts are usually not totally live - normally a few minutes delay is added so competing teams cannot have another member watching or listening in and sending participants advantagous information. Typically ETTV has a longer delay than the shoutcast does, so the result is ETTV and shoutcast are out of sync.

Fortunately it isnt the other way around, because you can pause WinAmp to syncronise the two. Simply listen for some event in the shoutcast (often shoutcaster will read out the time on the clock for this purpose, or you can listen for event's like 'FIGHT!' or 'dynamite planted') and immediately hit pause. When the event occurs in ETTV, hit play again. This can be easier if you view ETTV in windowed mode, also if you make a mistake and pause WinAmp for too long, reconnect to the shoutcast URL.

== Replaying ETTV demos on a local Windows server ==

If you have ETTV Demo files (*.tv84), you can watch them locally on your windows machine. in order to do so, you will need a ETTV-Server. Download the latest version (currently: http://bani.anime.net/banimod/forums/viewtopic.php?t=6529) and proceed with the following steps:

* Extract all files except tvgame.mp.i386.(so|dll) into your "Wolfenstein - Enemy Territory" root directory (not etmain).
* The tvgame.mp.i386.(so|dll) file goes into the etpro directory.
* Put the *.tv_84 files in your etpro\demos directory
* Create a shortcut to ETTV.exe (Right click in explorer windows, "new..." -> "Shortcut").
* Change the program call in the shortcut (Right click, "Properties") to: '"path\ettv.exe" +set fs_game etpro +set ettv_autoplay 1 +demo demo0000'

When you double click on the shortcut, ETTV should come up displaying a console and starting the playback. Note that the demo files are required to be named like demo0000.tv_84, demo0001.tv_84, etc. in order to work like this. The server will autoplay all demos in successive order. You can now start your ET and connect to your local server (choose "Internet Play", then "connect to IP" 127.0.0.1.

==== Known Issues ====

You have to install the complete etpro package for servers - the pk3 file that clients have is not enough.

I have discovered client error "MAX_GAMESTATE_CHARS" on several demos: The ETTV seems to run fine but local clients get kicked for that reason. I have not yet found why this happens, nor a solution. Any hints on that would be helpful.

This short How-To was written on request for gamestv.org, they are hereby permitted to use this text on their own site.

== External Links ==
* [http://www.gamestv.org/ GamesTV.org] is an ETTV listings site.
* [http://www.radioitg.com/schedule.php Radio iTG's schedule] is a source of shoutcasts.
* [http://www.gamestah.com/ Gamestah] is a source of Australian shoutcasts.

[[Category:ETTV]]

ETTV:Viewer's Guide

2006-08-31T10:43:53Z

Fusen: changed ettv download link to forums instead of 3rd party website

== ETTV Viewer's Guide ==
=== Introduction ===
ETTV is a modification that allows anybody to spectate Enemy Territory matches without actually being on the server the teams are playing on. The purpose is so that you have have thousands of people all able to watch an exciting match live, without being able to interfere or otherwise cause problems with the match.

The ETTV modification is supplied within the ETPro modification, you do not need any further modification unless you intend to run an [[ETTV:Server_Configuration|ETTV Server]].

=== Watching ETTV ===
Simply connect to an ETTV server like any other Enemy Territory server. Once you are connected it will look and feel very much like you are in spectator mode on any normal server.

There are some issues which occur frequently enough to make it worth noting here, however.

* ETTV servers frequently do not allow clients (that's you/your game) to auto-download any missing files. You should try to ensure you '''have the correct patch, modification and custom map versions before you join'''. This is usually, but not necessarily the latest official version. If you do not have the correct versions you may be unable to join, or disconnected at some point during viewing.

* '''Do not be concerned about interfering with the match''', you cant. The ETTV server you join is essentially playing a live demo of the match which is actually being played on another server. You can spectate freely and talk crap with the other viewers on the same ETTV server, thats it. Chat from ETTV viewers is distinguished from chat in the match by the red "ETTV" preceding it.

* '''Connecting via IP address''' (command-line or console) is identical to any other Enemy Territory server. If you've been given the IP address of an ETTV server and are wondering what to do with it, open the console (usually by pressing the key under ESCape, often the ~ or ` key) and use the following command (including the forwardslash) - <tt>/connect ip.add.ress:port</tt>
:(for example: <tt>/connect 62.75.178.112:27962</tt>)

=== Additional Controls ===
* cycle between everybody on the server (who shows up on the scoresheet)
:fire <tt><Left Mouse button></tt>
* cycle following only objective carriers
:Prone + (fire / altweapon) <tt><X + LeftMouse></tt>
* cycle following only spectators / shoutcasters
:Zoom + (fire / altweapon) <tt><nowiki></nowiki></tt>
* Jump directly to following a player in view
: Press activate while pointing crosshair at player
* return to free floating mode.
: Press jump or activate <tt><Spacebar></tt>

=== Generally Useful Tips ===
* Chats from other ETTV spectators can be hidden with the console command <tt>/tvchat off</tt>, and re-enabled with <tt>/tvchat on</tt>. All chat done on ETTV won't be seen on the game server (luckily). If certain chatters start to irritate you, you can easily ignore specific people with the <tt>/ignore</tt> command and can use the <tt>/unignore</tt> command to show their chat messages again.

* To spectate a specific player through their eyes, open console and put in the command <tt>/players</tt>, and notice the player number. Now just <tt>/follow x</tt>. If you're new to Enemy Territory, you might find it most entertaining to follow a shoutcaster, if there is one.

* Viewing ETTV in a window can be convenient while you find other IP's, talk in IRC, or access WinAmp, for example. To do this, you can go to the options screen and set a resolution which is smaller than your desktop screen resolution, and then select windowed mode. Alternatively, enter <tt>/r_mode 3</tt> into console, and then hit ALT+Enter.

* Normal cvar restrictions dont apply when viewing demos, nor do they (usually) when viewing ETTV. This is OK because you're not playing against anyone. Several leagues remove the foliage (all the grassy stuff) on Radar because it hurts performance and, some say, isnt good for competitive gaming. As an ETTV viewer you can remove it via console: <tt>/r_drawfoliage 0</tt>. To further incrase performance you can remove wolffog (an effect which "adds" fog to the map, sometimes restricting the viewing distance [e.g. Railgun]) by setting <tt>r_wolffog 0</tt>. You might want to ensure that is reset to 1 before you join a normal gameserver however.

* ETTV is generally not live; normally a few minute long delay is added so competing teams cannot have another member watching and sending participants advantagous information.

== Shoutcasts ==
A [http://en.wikipedia.org/wiki/Shoutcast shoutcast] is essentially a match commentary, broadcast over something akin to internet radio. The shoutcaster is usually someone heavily involved with the ET community and listening to the shoutcast greatly enhances the entertainment value of ETTV.

A shoutcast is completely seperate from ETTV however, to listen to a shoutcast you will need to open the URL with a suitable program - [http://winamp.com/ WinAmp] being one of many such programs. The shoutcast URL is often available at the same place you found the ETTV details for the match you want to watch.

Like ETTV, shoutcasts are usually not totally live - normally a few minutes delay is added so competing teams cannot have another member watching or listening in and sending participants advantagous information. Typically ETTV has a longer delay than the shoutcast does, so the result is ETTV and shoutcast are out of sync.

Fortunately it isnt the other way around, because you can pause WinAmp to syncronise the two. Simply listen for some event in the shoutcast (often shoutcaster will read out the time on the clock for this purpose, or you can listen for event's like 'FIGHT!' or 'dynamite planted') and immediately hit pause. When the event occurs in ETTV, hit play again. This can be easier if you view ETTV in windowed mode, also if you make a mistake and pause WinAmp for too long, reconnect to the shoutcast URL.

== Replaying ETTV demos on a local Windows server ==

If you have ETTV Demo files (*.tv84), you can watch them locally on your windows machine. in order to do so, you will need a ETTV-Server. Download the latest version (currently: http://bani.anime.net/banimod/forums/viewtopic.php?t=6529) and proceed with the following steps:

* Extract all files except tvgame.mp.i386.so into your "Wolfenstein - Enemy Territory" root directory (not etmain).
* The tvgame.mp.i386.so file goes into the etpro directory.
* Put the *.tv_84 files in your etpro\demos directory
* Create a shortcut to ETTV.exe (Right click in explorer windows, "new..." -> "Shortcut").
* Change the program call in the shortcut (Right click, "Properties") to: '"path\ettv.exe" +set fs_game etpro +set ettv_autoplay 1 +demo demo0000'

When you double click on the shortcut, ETTV should come up displaying a console and starting the playback. Note that the demo files are required to be named like demo0000.tv_84, demo0001.tv_84, etc. in order to work like this. The server will autoplay all demos in successive order. You can now start your ET and connect to your local server (choose "Internet Play", then "connect to IP" 127.0.0.1.

==== Known Issues ====

You have to install the complete etpro package for servers - the pk3 file that clients have is not enough.

I have discovered client error "MAX_GAMESTATE_CHARS" on several demos: The ETTV seems to run fine but local clients get kicked for that reason. I have not yet found why this happens, nor a solution. Any hints on that would be helpful.

This short How-To was written on request for gamestv.org, they are hereby permitted to use this text on their own site.

== External Links ==
* [http://www.gamestv.org/ GamesTV.org] is an ETTV listings site.
* [http://www.radioitg.com/schedule.php Radio iTG's schedule] is a source of shoutcasts.
* [http://www.gamestah.com/ Gamestah] is a source of Australian shoutcasts.

[[Category:ETTV]]

ETTV:Server Configuration

2006-07-16T15:28:25Z

Fusen: updated to explain the file extensions for windows

<dot_graph>
digraph ettv {
master -> slave1
master -> slave2
slave1 -> "client1.."
slave1 -> "..client50"
slave2 -> "client51.."
slave2 -> "..client100"
slave1 -> "chained_slave1"
chained_slave1 -> "client101"
chained_slave1 -> "...client150"
}
</dot_graph>

==Installation - "Master" (gameserver)==

Copy ettv.(x86|exe) to the same directory your etded.(x86|exe) is located.
Start your gameserver as normal, but run ettv.(x86|exe) instead of etded.(x86|exe).

===Set some cvars===

'''ettv_sv_maxslaves''' (default 0, no slave connections allowed)
:Number of ettv slaves allowed to connect.
:''Note:'' Slave slots are always reserved, like private slots.
'''ettv_password''' (default "", no slave connections allowed)
:Password for ettv slaves.
:Must be set, or no slaves will be able to connect!
'''b_ettv_flags''' (default 3)
:1 = prevent slaves from being callvote kicked
:2 = grant shoutcaster status to slaves
:values can be added together, eg 3 for both features.

===Playing on the master===
Players may now connect to your gameserver as normal.

==Installation - "Slave" (broadcast server)==

Copy ettv.(x86|exe) to the same directory your etded.x86 is located.
Copy tvgame.mp.i386.(so|dll) to the same directory as your etpro/qagame.mp.i386.(so|dll) is located.

===Set some cvars===
'''sv_maxclients'''
:Number of spectator clients to allow. This number is only limited by available cpu and memory.
:Some guidelines when provisioning a broadcast server:
:*100 spectator slots will require ~ 128mb ram. Use com_hunkmegs to set this.
:*100 spectator slots will require ~ 768kbyte/sec (6mbits), roughly 6kbyte/sec per client
:*100 spectator slots will take ~ 80% cpu of a Xeon 2.2ghz
:*Each slave will require ~20-40kbyte/sec from the master.

'''ettv_clientname''' (default "ETTV")
:Playername the slave will use when connecting to the master, eg "ETTV-xyz"

'''ettv_delay''' (default 0, disabled)
:number of seconds for slave to delay the master feed. Recording/playback chains should no longer be needed, and slaves should always maintain an exact delay from the master server.
:''note'': this should ONLY be set on the slave.
:''note'': only supported in ettv beta8 and later

===Chat passwords===
In order to curb the rampant abuse of ettv chat, admins may set "chat passwords" on their servers. If enabled, viewers are not allowed to chat unless they have a password. You can define as many passwords as you like, so you can easily track down individual abusers and limit the damage of stolen passwords.

'''ettv_chatpasswords''' (default 0, disabled)
:number of chat passwords defined.
'''ettv_chatpassword'''(1-99999)
:individual chat passwords.

viewers use <tt>/chatpassword <password></tt> to login.

if logged in, ettv chats will be tagged with a number in parentheses identifying which chat password the viewer is using.
===Misc commands for viewers===
;For ettv beta 4 and above
* spectators may <tt>/ignore</tt> and <tt>/unignore</tt> other spectators
* semiadmin functionality now works for slaves
* rcon may now mute/unmute specs

===Connect the slave===
Now start your slave server by running ettv.(x86|exe)

Tell the slave server to connect up to the master server:
:<tt>tv connect master.ip.address:port ettv_password(required) g_password(if the master has a g_password set)</tt>

If you have configured everything correctly, the slave should connect to the master.
Clients should now be able to connect to the slave and spectate the game in progress.

This is a "live broadcast" with no delay.

===Disconnect the slave===
To tell the slave to disconnect from the master:
:<tt>tv disconnect</tt>

===Slave Chaining===

==== What is chaining and why chain slaves? ====

ETTV allows chaining slaves together. This very neat feature lets you connect one ETTV slave to another ETTV slave that is broadcasting a match instead of directly to the game server hosting the match. Apart from the "w00t this is very cool" factor, why is this feature so important for admins? Basicly, working in a chained model allows to broadcast a match to a large number of spectators without too much hastle and too many risks for the master server.

Chaining was developped for a simple reason: if you take into account that one ETTV slave connects at an '''unlimited''' rate to a master, you really don't want to connect 15 or 20 slaves to a game server to broadcast let's say the ''Atlantic Battle''. Chances are you will bring down the master game server and thus the game. Chaining slaves firmly alleviates the load on the master game server. 2 or 4 of these ''Hubs'' can do the job of delaying the signal and feeding it to other slaves.

Other benefits might include better network performance. If you can choose to either connect your slave to the game server where your connection is not optimal or to a nearby slave who is on a better connection to the master, it might help the quality of your broadcast. Plus you don't need to record anything when connecting to a delayed slave.

==== Setting up your slave to allow connections from other slaves ====

This part is actually pretty easy. You need to set up your slave as if you were setting up a master game server. This means that, next to the normal slave parameters, you have to set up the following:

* '''b_ettv_flags''': set this to at least 1
* '''ettv_sv_maxslaves''': set this to at least 1. Depending on how powerful your machine is you can set this number higher. Don't set it too high though, a slave still connects at an unlimited rate
* '''ettv_password''': set to something else than "". This password is needed by the slaves connecting to your slave (together with g_password of course)

Other settings such as ettv_netblast, ettv_tv_iptos etc... can be set as well. You can even use autorecord if you wish, or just add an extra delay.

==== Pitfalls ====

There are however a few risks associated with slave chaining. One of the biggest issues is '''PK3 dependancies'''.

As you know, a slave needs to have at least all the PK3s of the server it connects too. But a slave can have more PK3s installed, as long as it has the ones on the server's pure list. This is what complicates things! The further you go down the "chain", the more the chances exist of PK3 pollution, which makes the job of the last slave very hard. And the viewers connecting to that slave will not be very happy either.

So for those of you venturing into chaining slaves here's a rule of thumb: '''always keep the installed PK3s to the bare minimum'''! Do not add stuff you do not need. If you want to know what PK3s you need and not need, connect your slave to the master or the hub, see which PK3s are on the pure list and rename or remove the PK3s that are not on the list. You will make your viewers and other admins connecting to your slave very happy.

Another risk could be '''chained lag'''. If one of the slaves that is higher in the chain starts lagging, the consequenses for the slaves depending on it will be seen immedeatily. So if you offer to be one of the higher slaves in the chain, make sure your machine can handle it! An ETTV chain is much like the food chain ;-).

==== Admin contributions ====

If by now you feel like getting your hands dirty in ETTV chaining madness and you want to see some example of hubs, slaves, broadcasters and scripts to get it all working, you can already start by checking out [[User:Deej|deej's page]].

==ETTV Demos==
ETTV can record and playback '''ETTV demos'''. ETTV demos have the extension .tv_84 (or .tv_83 for older versions) and are completely different from the .dm_84 demos recorded on clients.

You may record the match in progress to a file, with the command:
:<tt>record <'''demo name'''></tt>
If you omit the demo name, ettv will start recording using a filename of demoXXXX where XXXX is the first available number starting from 0000.

Demos will stop recording when a map changes.

To stop recording a demo:
:<tt>stoprecord</tt>

To play back a recorded demo:
:<tt>demo <'''demo name'''></tt>

To check the status of an ettv slave:
:<tt>tv status</tt>
This will tell you if the slave is connected to a master, or if it is currently playing back a demo.

To fastforward a demo:
:<tt>ff <seconds></tt>
Eg <tt>ff 30</tt> will fast foward 30 seconds. Fast forward stops at map restarts, so you can safely ff 999 to fast forward through a warmup.
:''note'': requires ettv beta 7 or later

===Autorecording demos===
ettv is able to automatically continuously record demos, creating new demofiles when the map changes. To do this, set the cvar ettv_autorecord to 1. ettv will start recording demos with the name demoXXXX where XXXX is a number starting at 0000 and incrementing on each map change.

Server admins may find it useful to use the demo recording feature of ettv to record matches, instead of requiring individual players to record them. An ettv demo records everything that happens on a server, including all player viewpoints.

===How to create demo based delayed feeds===
Autorecording demos is the first half of the process for delayed feeds. Typically you would run a passworded slave server with the smallest number of sv_maxclients possible. No spectators should connect to this server. The only purpose of this slave is to connect up to the master and record the match to sequentially numbered demofiles.

Now start up a slave, and tell it to broadcast the demo being recorded.

:<tt>demo demo0000</tt>

If you wait approx. 60 seconds after the master begins recording before issuing this command to your slaves, then you have a 60 second delay on your broadcast.

If you want slaves to automatically switch to the next demo when the end of the demo is reached (eg on a map change), you would set the cvar ettv_autoplay to 1. If a slave is playing demo0000 and it reaches the end, it will then try to play demo0001 and so on.

Disadvantage of this method: It is not automated in ettv itself, though admins can script it.
Advantage of this method: You may run multiple broadcast servers from the same single demo stream.

Automated delayed feeds are supported in ettv beta 8. See the above.

===Playing back previously recorded ETTV demos===
This is essentially the same as delayed feeds above.
* Configure your server as described in [[ETTV:Server_Configuration#Installation_-_.22Slave.22_.28broadcast_server.29|Slave Installation]] section
* Obtain the <tt>.tv_*</tt> demos and place them in <tt>''fs_game''/demos</tt>
* Start the ettv executable with pb disabled
* <tt>set ettv_autoplay 1</tt> if you want to play back sequential demos named <tt>demo0000.tv_84</tt>, <tt>demo0001.tv_84</tt> etc.
* <tt>demo '''<yourdemoname>'''</tt>
* connect a client and enjoy the show!

==Troubleshooting==

* The slave server must be running the same fs_game setting as the master server.
* The slave server must have a copy of every map pk3 the master server is using.
* If the master server loads a map the slave server doesn't have, the slave will get stuck.
* Spectators will be forced to download any custom pk3 you are using.
* It is a good idea to keep the master server pk3 list to a minimum.
* If you are using the autorecord/autoplay feature for running delayed feeds, you will usually want to make sure you clear out the demos directory first. Autorecording will start numbering demofiles using the first available number, so if you have old recorded demos then ettv might start recording from eg demo0017. If your scripts expect to start playback from demo0000 then you might end up broadcasting a game recorded at some earlier date...
* If the broadcaster constantly reloads on round starts etc, it's probably a problem with too many pk3s on the ettv servers.

==Miscellaneous==
* Slaves may send chats to the master with the command msay
* Slaves may list players on the master with the command players

==Performance tuning==

Spectator servers with large numbers of clients (eg >100) will push the OS very hard with huge amounts of UDP traffic. The default OS buffer settings for Linux are inadequate and can hurt performance, causing lag and/or disconnects.

If you get messages like
:<tt>NET_SendPacket ERROR: No buffer space available to 192.168.120.142:27960</tt>

Then you definitely need to increase your kernel network buffers.

Large spectator servers should increase the kernel buffers.

The following commands should be issued as root on linux:
:<tt>echo "524288" > /proc/sys/net/core/rmem_max</tt>
:<tt>echo "524288" > /proc/sys/net/core/wmem_max</tt>

FreeBSD can try this:
:<tt>sysctl -w net.inet.udp.recvspace=65535</tt>
:<tt>sysctl -w net.inet.udp.maxdgram=57344</tt>
:<tt>sysctl -w kern.ipc.maxsockbuf=8388608</tt>

===Network tuning cvars===
;The following are only available in ettv beta 7 and later.
By default, et uses small packets of 1400 bytes or less to send to clients. If messages need to be larger, they are 'fragmented' and sent over several server frames. ettv slave messages tend to be large and often fragment. ettv normally tries to send slaves all fragments at once to avoid jittery playback, but some networks / OSes handle this badly. ettv beta 7 introduces new controls so admins can optimize ettv for their individual network.

'''ettv_netblast''' (default 1)
:by default, ettv tries to send all fragments at once. some networks may handle this badly. setting this to 0 disables. warning: setting this to 0 without increasing ettv_mtu will result in severely laggy slave playback.

'''ettv_mtu''' (default 1400)
:; master only
:if your network / os supports it, you can set this to large values (eg 16000) to prevent message fragmentation and provide smoother ettv links. this cvar has no effect on normal ET clients.
:''note'': ettv_mtu must currently be set from commandline, it cannot be changed on the fly (yet).

'''ettv_tv_iptos''' (default 0)
:you can set the ip type of service field of ettv link packets. if your network/ISP supports it, you can use a value like 16 ("minimize delay") to prioritize ettv link packets over others on the network.

'''ettv_sv_iptos''' (default 0)
:same as ettv_tv_iptos, but affects packets for normal ET clients.

===Article Reference===
(x86|exe) refers to the file extension of the ettv file, for linux use .x86 and for windows use .exe
(so|.dll) refers to the file extension of the slave file, for linux use .so and for windows use .dll

[[Category:ETTV]]

Current events

2006-01-02T21:45:16Z

Fusen: oops

Phase I: Fill the wiki

Phase II: Finish coding ETPro

Current events

2006-01-02T21:45:00Z

Fusen:

Phase I: Fill the wiki
Phase II: Finish coding ETPro

EDV

2006-01-02T21:43:15Z

Fusen: Added as the rough data, a new layout wouldn't go amiss

EDV stands for Extended Demo Viewer it's a tool which gives you camera-moving possibilities. The most important options are the freecam and the weaponcam.

The freecam gives you the ability to watch a demo as a spectator, in other words you can freely fly around the map using your ingame movement
keys. type ''/freecam'' in the console to enable it. If you want fly through walls, you can use the well known "noclip" command.

'''NOTE:''' If you move
out of the pvs of the demo (the pvs of the player who recorded the demo), you won't see anything at all. Sometimes it's hard to find your way
back to the pvs, if you set the cvar b_demo_pvshint to 1, a line will be drawn from the camera origin to the demo-recorder's origin, in addition of noclip you will easily find your way back to the pvs. If ''b_predefineddemokeys'' is set to 1 you will be able to use the
hardcoded keys from the demohelpmenu, KP_ENTER is the key to toggle freecam, but I recommend that you set ''b_predefineddemokeys'' to 0 because in this doc the cvars/cmd's will be explained.

With "freecamgetpos" you can retrieve the position of the camera, and with freecamsetpos you can set it. When you set ''b_demo_lookat'' to a clientNum (default value is -1 = turned off) the camera will always look at
that player, you can reveal the clientNums with b_demo_nametag +4, nametags are actually floating playernames, +1 draws nametags from players who are in your pvs, +2 from every player, +4 adds the clientnumber to the nametag, +8 adds the class (letter) to the nametag , the same option exists
for dynamites: ''b_demo_dynamitecounter'' which draws a floating timer for every dynamite in your current fov.
If you want turn the camera with some keys, use:
<pre>
+freecam_turnup
+freecam_turndown
+freecam_turnleft
+freecam_turnright
+freecam_rollleft
+freecam_rollright
</pre>
the cvars '''b_demo_yawturnspeed b_demo_pitchturnspeed b_demo_rollspeed''', will control the speed of these commands

''b_demo_playersprites'' turns of player sprites in demoplay (the docs icon, the ! mark, ...)

The weaponcam attaches the camera to a missile (grenade, panzer, dynamite)

set:
<pre>
b_demo_grenadecam +1 to follow grenades
b_demo_grenadecam +2 to follow airstrike/smokegrenade cannisters
b_demo_mortarcam 1 to follow mortars
b_demo_panzercam 1 to follow panzers
</pre>
b_demo_teamonlymissilecam 1 if you only want to see the missiles of your teammates

next cvars control the distance from the camera to the missile:
</pre>
b_demo_followxDistance
b_demo_followyDistance
b_demo_followzDistance
</pre>
''b_demo_nopitch'' toggles the camera pitching when attached to a missile

if you want a good config, read this thread: http://bani.anime.net/banimod/forums/viewtopic.php?t=3207

auto change timescale to b_demo_autotimescale in weaponcam if the weapon is set in b_demo_autotimescaleweapons (bitflag)
* 1 = panzer
* 2 = grenade
* 4 = dynamite
* 8 = mortar
* 16 = smoke

Shoutcasting

2005-12-19T03:09:04Z

Fusen: Needs a major redesign, only added as a placeholder

admins can enable shoutcasting on their server by setting a shoutcastpassword in the cvar ''b_shoutcastpassword'' , to disable shoutcasting, add an empty string

shoutcasters can login with ''sclogin'' <pass> or ''shoutcastlogin'' <pass>, logout with sclogout or shoutcastlogout

referee's can make players a shoutcaster:

''makeshoutcaster'' <clientid>

''removeshoutcaster'' <clientid>

with rcon you can use:

''makeshoutcaster'''''|'''''makeshoutcast'''''|'''''makesc'' <clientid>

''removeshoutcaster'''''|'''''removeshoutcast'''''|'''''removesc'' <clientid>

shoutcasters can see :
* floating player names
* dynamite counter
* truck/tank health
* all the mines

they can't be speclocked, and in the scoreboard "shoutcaster" is written after their name

Headshot Mode

2005-12-19T03:06:18Z

Fusen:

A headshot mode is included in ETPro, controlled by the cvar ''b_headshot'' (which is a bitmask):
<pre>
0 = disabled
1 = only headshots do damage
2 = instagib headshots : hit = kill
4 = only clients can be damaged, not world entities (e.g. barrels)
8 = you can only receive damage from other clients, you can't receive damage from the world, e.g. from an exploding barrel</pre>

The instagib damage is controlled by the cvar ''b_instagibdamage'', 400 is the default value.

SendServerCommand

2005-11-27T15:40:12Z

Fusen: minors

et.trap_SendServerCommand() is used to send a command from the server to one or more clients. The first argument is the slot number of the client the command will be sent to. If it's equal to -1, the command will be broadcast to all clients.

The following commands can be issued with this function:

==Prining==
===Print===
: * "'''print''' \"''Message''\n\""
:'''print''' prints ''Message'' to the client's console.

===Center Print MoO===
: * "'''cpm''' \"''Message''\n\"" 
:'''cpm''' prints ''Message'' to the client's annoucement area and console.

===Center Print===
:"'''cp''' \"''Message''\n\"" 
:'''cp''' prints ''Message'' to the center of the client's screen.

===Scores Print===
: * "'''sc''' \"''Message''\n\"" 
:'''sc''' prints ''Message'' to the client's console and writes it to the statsdump file.

==Chatting==
===Chat===
: * "'''c''' ''ClientNum'' \"''Message''\"" 
:'''c''' prints ''Message'' as a global chat message on behalf of the client specified by ''ClientNum''.

===Team Chat===
: * "'''tc''' ''ClientNum'' \"''Message''\" ''X-Location'' ''Y-Location'' ''Z-Location''" 
:'''tc''' prints ''Message'' as a team chat message on behalf of the client specified by ''ClientNum'', 
:the ''X,Y,Z-Location's'' are optional parematers that represent the client's location, 
:if the ''X,Y,Z-Location's'' are left out then the message will be printed without a location.

===Fireteam Chat===
: * "'''bc''' ''ClientNum'' \"''Message''\" ''X-Location'' ''Y-Location'' ''Z-Location''". 
:'''bc''' prints ''Message'' as a fireteam chat message on behalf of the client specified by ''ClientNum'', 
:the ''X,Y,Z-Location's'' are parematers that represent the client's location.

==Voice Chat==
===Global Voice Chat===
: * "'''vchat''' 0 ''ClientNum'' 50 ''Vsay-String'' ''Vsay-Number'' \"''Custom-Message''\"". 
:'''vchat''' sends a global voice chat ''Vsay-String'' on behalf of the client specified by ''ClientNum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

===Team Voice Chat===
: * "'''vtchat''' 0 ''ClientNum'' 50 ''Vsay-String'' ''Vsay-Number'' ''Y-Location'' ''Z-Location'' \"''Custom-Message''\"" 
:'''vchat''' sends a team voice chat ''Vsay-String'' a on behalf of client ''ClienNtum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:the ''X,Y,Z-Location's'' parematers the represent the clients location. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

===Fireteam Voice Chat===
: * "'''vtchat''' 0 ''ClientNum'' 50 ''Fireteam-String'' ''Vsay-Number'' ''Y-Location'' ''Z-Location'' \"''Custom-Message''\"" 
:'''vchat''' will team voice chat ''Vsay-String'' on behalf of client ''ClienNum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:the ''X,Y,Z-Location's'' parematers the represent the clients location. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

==Fireteam==
===Application===
: * "'''application''' ''Number''"
:'''application''' shows a fireteam invation message to the client. 
:if ''Number'' > -1 - the "accept ... application to join your fireteam" message shows up. In this case ''Number'' is the ClientNum of the applying client. 
:if ''Number'' == -1 - the "your aplication has been submitted" message shows up. 
:if ''Number'' == -2 - the "your aplication failed" message shows up. 
:if ''Number'' == -3 - the "your aplication has been approved" message shows up. 
:if ''Number'' == -4 - the "your aplication reply has been sent" message shows up.

===Proposition===
: * "'''proposition''' ''Number'' ''Number2''"
:'''proposition''' shows a fireteam proposition message to the client. 
:if ''Number'' > -1 - the "accept ... proposition to invite ... to your fireteam" message shows up. In this case ''Number'' is the ClientNum of the proposed client, and ''Number2'' is the ClientNum of the proposing player. 
:if ''Number'' == -1 - the "your proposition has been submitted" message shows up. 
:if ''Number'' == -2 - the "your proposition was rejected" message shows up. 
:if ''Number'' == -3 - the "your proposition was accepted" message shows up. 
:if ''Number'' == -4 - the "your proposition reply has been sent" message shows up. 
:''Number2'' is an optional paramater only used when ''Number'' > -1.

===Invitation===
: * "'''invitation''' ''Number''"
:'''invitation''' shows the fireteam invation message to the client. 
:if ''Number'' > -1 - the "accept .. invitation to join your fireteam" message shows up. In this case ''Number'' is the ClientNum of the applying client. 
:if ''Number'' == -1 - the "your invitation has been submitted" message shows up. 
:if ''Number'' == -2 - the "your invitation rejected" message shows up. 
:if ''Number'' == -3 - the "your invitation was accepted" message shows up. 
:if ''Number'' == -4 - the "your invitation reply has been sent" message shows up.

==Others==
===Complaining===
: * "'''complaint''' ''Number''" 
:'''complaint''' shows the complaint vote message to the client. 
:if ''Number'' > 1 - the vote shows up. In this case ''Number'' is the ClientNum of the teamkilling player. 
:if ''Number'' == -1 - the "complaint filed" message shows up. 
:if ''Number'' == -2 - the "complaint dismissed" message shows up.

===Spawning===
: * "'''setspawnpt''' ''Number''" 
:"'''setspawnpt''' sets the client game selected spawnpoint to number ''number''.

[[Category:ETPro]]
[[Category:ETPro:Mods]]

SendServerCommand

2005-11-27T15:37:32Z

Fusen: cats

et.trap_SendServerCommand() is used to send a command from the server to one or more clients. The first argument is the slot number of the client the command will be sent to. If it's equal to -1, the command will be broadcasted to all clients.

The following commands can be issued with this function:

==Prining==
===Print===
: * "'''print''' \"''Message''\n\""
:'''print''' prints ''Message'' to the client's console.

===Center Print MoO===
: * "'''cpm''' \"''Message''\n\"" 
:'''cpm''' prints ''Message'' to the client's annoucement area and console.

===Center Print===
:"'''cp''' \"''Message''\n\"" 
:'''cp''' prints ''Message'' to the center of the client's screen.

===Scores Print===
: * "'''sc''' \"''Message''\n\"" 
:'''sc''' prints ''Message'' to the client's console and writes it to the statsdump file.

==Chatting==
===Chat===
: * "'''c''' ''ClientNum'' \"''Message''\"" 
:'''c''' prints ''Message'' as a global chat message on behalf of client ''ClientNum''.

===Team Chat===
: * "'''tc''' ''ClientNum'' \"''Message''\" ''X-Location'' ''Y-Location'' ''Z-Location''" 
:'''tc''' prints ''Message'' as a team chat message on behalf of client ''ClientNum'', 
:the ''X,Y,Z-Location's'' are optional parematers that represent the client's location, 
:if the ''X,Y,Z-Location's'' are left out then the message will be printed without a location.

===Fireteam Chat===
: * "'''bc''' ''ClientNum'' \"''Message''\" ''X-Location'' ''Y-Location'' ''Z-Location''". 
:'''bc''' prints ''Message'' as a fireteam chat message on behalf of client ''ClientNum'', 
:the ''X,Y,Z-Location's'' are parematers that represent the client's location.

==Voice Chat==
===Global Voice Chat===
: * "'''vchat''' 0 ''ClientNum'' 50 ''Vsay-String'' ''Vsay-Number'' \"''Custom-Message''\"". 
:'''vchat''' sends a global voice chat ''Vsay-String'' on behalf of client ''ClientNum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

===Team Voice Chat===
: * "'''vtchat''' 0 ''ClientNum'' 50 ''Vsay-String'' ''Vsay-Number'' ''Y-Location'' ''Z-Location'' \"''Custom-Message''\"" 
:'''vchat''' sends a team voice chat ''Vsay-String'' a on behalf of client ''ClienNtum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:the ''X,Y,Z-Location's'' parematers the represent the clients location. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

===Fireteam Voice Chat===
: * "'''vtchat''' 0 ''ClientNum'' 50 ''Fireteam-String'' ''Vsay-Number'' ''Y-Location'' ''Z-Location'' \"''Custom-Message''\"" 
:'''vchat''' will team voice chat ''Vsay-String'' on behalf of client ''ClienNum''. 
:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>), ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files. 
:the ''X,Y,Z-Location's'' parematers the represent the clients location. 
:''Custom-Message'' is by default \"\" (empty), otherwise it's the message that gets printed in the chat area.

==Fireteam==
===Application===
: * "'''application''' ''Number''"
:'''application''' shows a fireteam invation message to the client. 
:if ''Number'' > -1 - the "accept ... application to join your fireteam" message shows up. In this case ''Number'' is the ClientNum of the applying client. 
:if ''Number'' == -1 - the "your aplication has been submitted" message shows up. 
:if ''Number'' == -2 - the "your aplication failed" message shows up. 
:if ''Number'' == -3 - the "your aplication has been approved" message shows up. 
:if ''Number'' == -4 - the "your aplication reply has been sent" message shows up.

===Proposition===
: * "'''proposition''' ''Number'' ''Number2''"
:'''proposition''' shows a fireteam proposition message to the client. 
:if ''Number'' > -1 - the "accept ... proposition to invite ... to your fireteam" message shows up. In this case ''Number'' is the ClientNum of the proposed client, and ''Number2'' is the ClientNum of the proposing player. 
:if ''Number'' == -1 - the "your proposition has been submitted" message shows up. 
:if ''Number'' == -2 - the "your proposition was rejected" message shows up. 
:if ''Number'' == -3 - the "your proposition was accepted" message shows up. 
:if ''Number'' == -4 - the "your proposition reply has been sent" message shows up. 
:''Number2'' is an optional paramater only used when ''Number'' > -1.

===Invitation===
: * "'''invitation''' ''Number''"
:'''invitation''' shows the fireteam invation message to the client. 
:if ''Number'' > -1 - the "accept .. invitation to join your fireteam" message shows up. In this case ''Number'' is the ClientNum of the applying client. 
:if ''Number'' == -1 - the "your invitation has been submitted" message shows up. 
:if ''Number'' == -2 - the "your invitation rejected" message shows up. 
:if ''Number'' == -3 - the "your invitation was accepted" message shows up. 
:if ''Number'' == -4 - the "your invitation reply has been sent" message shows up.

==Others==
===Complaining===
: * "'''complaint''' ''Number''" 
:'''complaint''' shows the complaint vote message to the client. 
:if ''Number'' > 1 - the vote shows up. In this case ''Number'' is the ClientNum of the teamkilling player. 
:if ''Number'' == -1 - the "complaint filed" message shows up. 
:if ''Number'' == -2 - the "complaint dismissed" message shows up.

===Spawning===
: * "'''setspawnpt''' ''Number''" 
:"'''setspawnpt''' sets the client game selected spawnpoint to number ''number''.

[[Category:ETPro]]
[[Category:ETPro:Mods]]

User:Zinx

2005-11-20T15:02:26Z

Fusen:

<nowiki>(C%;_98\~|4X876543210/.o,+$#G!~}C0@c-w|_;98[v5Xs!</nowiki>

I work for the RIAA, so don't cross my path with your damn warez!

IAC

2005-11-19T12:59:54Z

Fusen:

== ETPro Anti Cheat ==

----

[[ETPro]] integrates a new Anti Cheat system named 'IAC' or 'Ikkyo Anti Cheat'. At the moment it is intended to complement (not replace) [http://www.evenbalance.com PunkBuster™] for cheat detection. [[ETPro]] looks for things [http://www.evenbalance.com PunkBuster™] cannot, and [http://www.evenbalance.com PunkBuster™] looks for things [[ETPro]] cannot.

== Controlling the anticheat system ==
''b_anticheat'' controls the anticheat system. The possible settings are:
* 0 - disabled. [[ETPro]] does not report cheaters at all.
* 1 - enabled (default). Normal sensitivity. [[ETPro]] reports known cheats from the database and known cheat techniques as cheaters.
* 2 - Increased sensitivity (not recommended). Includes checks which are likely to cause false positives.
* 3 - Extreme sensitivity (absolutely not recommended). Only absolutely clean Windows systems are allowed. Absolutely clean Windows sytems are very rare though, so lots of players will be reported as cheaters.

== Logs ==
If a cheater is found, they are reported to players on the server and in the server logs.

If the word '''CHEATING''' is in '''RED''', [[ETPro]] has detected the player is absolutely using a known public cheat. It is safe to kick/ban these players. You will also see something like this in your logs:

<pre><nowiki>21:58.11 etpro IAC: 1 [JiuJitsu^7] [304DADA5916CE3A8E8B6966AB772D142A7578C3D] [^1CHEATER^7 win32]
21:58.11 etpro IAC: HWe8auebgXt69-IaJ3TkljBwH7j8FlvEnJDUk1AUNMZgdOZ0WyyL2n
zx-z0phDJQFvXU74+rqeXadpIWgp822butKGwycggXnA-B9I4Sw9AqGuorR7Mwz+Rt45
tyMwxunGdEe0V8MGTzqM4IKm8mPt-6LlY6YaRvyDdOrqyaiInYX2Zeq8k2BI0mufHztkIU
CiSvtNQwtZFTjSCe6VKHKkbV8UUTKT-0PW5Oa1Y81cRdIBqkRQ</nowiki></pre>

This is encrypted information which allows an [[ETPro Developer]] to positively identify which specific cheat the player was using, if needed. An [[ETPro Developer]] does not generally need such logs reported to him.

''The following only applies if ''b_anticheat'' is set to 1:''

If the word '''CHEATING''' is in '''YELLOW''', [[ETPro]] has detected the player has software which does exactly the same thing cheats do. There are two possibilities: they are using software which causes false positives (FRAPS, atitool), or they are using a private/non-public cheat. Users who get false positives should read [http://bani.anime.net/banimod/forums/viewtopic.php?t=3275 this thread] to resolve them.

If an admin suspects a player in '''YELLOW''' is using a new undetected cheat, you may forward your logs to an [[ETPro Developer]] for inspection. You will see something like this in your logs:

<pre><nowiki>10:58.03 etpro IAC: 0 [^7[^3AV^7]^2Ikkyo^7^7] [5C650F40214398C58AE5ECDFADBC8D1AB6BFDD89] [^3CHEATER^7 win32]
10:58.03 etpro IAC: 5F+yE+tIboJD0TcZW+V3BrfKONQYxCEkmUGp4XWCRamupExR
cKGVjS31kmClRCWY0+d+0ugxz-X+9u1IHnispm3MGCt6QFlgVHuK41D3188DvPUY5i1
7LXNclCEYwQxs3rZLkCnXew3McNthKA8ASo4yyhbU6OALVV3az+dyEVAvB1NEudU
YoYJoEXFKFEbJSRt+3Rw4atWM8NO7yQbULkFrT1MjPjKzULVr2CiXcy+6YP6rDTXcWg</nowiki></pre>

This encrypted information allows an [[ETPro Developer]] to determine if the player was really cheating with a new cheat, or if it is a false positive caused by external programs.

Players who are reported as yellow '''CHEATER''' who are unable to resolve their problems by following [http://bani.anime.net/banimod/forums/viewtopic.php?t=3275 these instructions] should post a bug report in [http://bani.anime.net/banimod/forums/viewforum.php?f=14 this forum].

You may see "strange logs" like the following:

<pre><nowiki>09:20.10 etpro IAC: 0 [^7de^2A^7D ai^2M^7] [556B00DCB87C92A03784A7C558C5BFCA3238B1FF] [??? win32]
09:20.10 etpro IAC:MsCWa5viR4imLMGpS6W7gpMa1OgM-bSPmI69cE-z+nL2xQgc8t7
b6TdkwOfiDBG5llCaW4MuWrQr8VSBxSt+pqJVvJFkR29ppgerMLqGmCh0+bsf5w+m23
Wj-diM68xx4kVc+BDX1ZEMTsMYTccaSXKyNzkKZT1wx9rAWG5plv96QsrieIXY+3LpSK
xuuanLPixzpARZOv5VH6rZFY0LhvdvA3vVQwSynTKkOIW3XLmrmt3LNOWpO3RmTR3
uR87OFCCh38ws3S76cfmG</nowiki></pre>

This does not mean the player is cheating, it simply means there is something unusual about their system that may be of interest to an [[ETPro Developer]]. You should not forward these logs unless you suspect a player is cheating or unless an [[ETPro Developer]] specifically requests them from you.

Likewise, simply because an encrypted debug follows a player's log does not mean they are cheating:

<pre><nowiki>21:24.58 etpro IAC: 3 [^7|^0NE^7|R^5a^di^4n^7-^d42^7^7] [BD0875F42CB16B337A0EDC85F6BA03155665AEFF] [clean linux]
21:24.58 etpro IAC: vZHbY0m5i8DJ-my5FxRp1+I9Drj8cuVMAowAoX6XwWKaCh2h3lH
oCVTAgHsngeSrITZQWoFsJRGSjyAqsw9SxirdsZmoR7vLeTJYgk2t35ROlMyxgk+yd1nFq
HKfdE5sn5oE5tQQ-YTEJl7KIWHyG8ODeK+aLbR4NGIvgdWbVrllMEWFL3d99cgej+a+e
MKJIQYEbJB2LVh-MGxmXFovazupjtPGSydBnlCtWG6FWvLrd50tgO6gY2atXLaJfW-b-a
iw1Q5bcZMuZZ8yDHGDdFVoeobI2vw8qsZG-bXlINVVpNhIbNaenba6mvo</nowiki></pre>

In this case it is simply logging information so that the [[ETPro Developer]]s know the anticheat system is functioning correctly. Please do not forward these logs unless specifically requested.

== Keeping up to date ==

As new cheats are found, they will be added to [[ETPro]]'s anticheat database, and database updates will be posted in the [http://bani.anime.net/banimod/forums/viewforum.php?f=15 ETPro News forum]. Admins can download these database updates and install them at their leisure to keep up to date.

== Autokicking ==

The cvar b_cheatkicktime controls what is done when a cheater is detected. If it is -1 (default), nothing is done besides reporting to the console and logs. Any other value will kick the player for the specified number of minutes (eg 0 = kick for 0 minutes, 10 = kick for 10 minutes).

== FAQ ==
Q: In which log is this info saved?

<table><tr><td valign="top">A:</td><td><pre>// b_cheatlog - defines the name of a separate log for the anti-cheat system
// when set to an empty string, the anti-cheat system uses the main server
// log file
// default: ""
set b_cheatlog "etpro_cheats.log" </pre></td></tr></table>

Q: Can 2 different computers have the same GUID?

A: Yes, they can. It seems that every Windows™ 98 User got the same GUID '''<nowiki>[52FF6283916A9467908E6A771CB70285FB41C5E7]</nowiki>'''

[[Category:ETPro:Server_Cvars]]

User talk:WeblionX

2005-11-19T03:53:29Z

Fusen:

(Trying some fancyness) '''uglyness*'''

User talk:WeblionX

2005-11-19T03:53:03Z

Fusen:

uglyness*

User talk:Fusen

2005-11-18T23:34:27Z

Fusen:

This is just to turn the link from red to blue ;) --[[User:Deus|Deus]] 14:48, 18 November 2005 (PST)

I preferred it when it was red!

Main Page

2005-11-18T01:20:10Z

Fusen:

<center>'''Welcome to''' '''[[WolfWiki]]''' </center>

<table cellspacing="8">
<tr valign="top">

<td width="60%" style="border: 1px solid #FABD23; color: #000; background-color: #fcfae3">
<div style="padding: .5em .9em .9em">
__NOTOC__
==About==
[[WolfWiki]] is a collaborative site for the ETPro / ETTV / BayonET community.

==Getting Started==
Anyone with a [http://bani.anime.net/banimod/forums/ Banimod Forums] account may edit pages. If you do not have an account, you may [http://bani.anime.net/banimod/forums/profile.php?mode=register apply] for one. Please follow the [[Help:Editing]] guidelines when editing pages. 
<hr>
<center>There are currently {{NUMBEROFARTICLES}} [[:Special:Allpages|articles available]].</center>
</div>
</td>

<td style="border: 1px solid #3e48fb; color: #000; background-color: #C5DAEB">
<div style="padding: .5em .9em .9em">
==[[:Category:ETPro|ETPro]]==
{{ETPro_Topics}}
==[[:Category:ETTV|ETTV]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=18 Discussion Forums] 
[[ETTV:Server Configuration|Server Configuration]] 
[[ETTV:Viewer's Guide|Viewer's Guide]] 

==[[:Category:BayonET|BayonET]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=10 Discussion Forums]

</div>
</td>

</tr>

</table>

__NOEDITSECTION__

Cursefilter

2005-11-16T16:28:10Z

Fusen:

Admins may enforce filters on public text chats. While the primary use is for keeping cursing under control, some admins have made creative use of the filter to prevent accidental security leaks, such as filtering rcon password typos.

fireteam chats are never filtered, the logic behind this is that players who find someone's fireteam chats offensive may simply eject the offending player from the fireteam, or leave the fireteam themselves.

Also the filter only works for complete words, without colour codes etc. So you will need to create additional filters for such methods of circumventing the original filter such as "''s h i t''". But this also means that if you create a filter for the word "''ass''", all words that contain ''ass'' would also be filtered such as "Cl'''ass'''" and "P'''ass'''word" etc.

== How to use: ==

''b_cursefilter'' is a space separated list of words the cursefilter will watch for.

''b_cursefilteraction'' is the action to take when a word on the watchlist is found. there are 4 possible settings:
<pre>0 - do nothing
1 - silently drop the chat (player sees their chat, but nobody else does)
2 - censor b_cursefilter words with asterisks
3 - (default) totally block any chat containing a b_cursefulter word</pre>

Voicechat

2005-11-16T16:03:58Z

Fusen:

== Specific variant ==

ET Pro allows players more control over voicechats. For voicechats which have multiple variants (eg cheer, negative), players may specify specific voicechats to use.

''For example:''

<pre>/vsay 2 cheer</pre>

Would always use the second cheer variant.

== Custom text ==

If the admin has enabled custom voicechats (''b_customVoiceChat 1'', default) then players may use custom text for the voicechat, e.g.

<pre>/vsay enemydisguised Enemy in da skies!
/vsay needengineer We need an engine ear!</pre>

You may combine specific variants with custom text, for example:

(as axis):
<pre>/vsay 1 negative 9!
/vsay 2 ftattack A TACK!(@*#&</pre>

Main Page

2005-11-15T18:14:19Z

Fusen:

<center>'''Welcome to''' '''[[WolfWiki]]''' </center>

<table cellspacing="8">
<tr valign="top">

<td width="60%" style="border: 1px solid #FABD23; color: #000; background-color: #fcfae3">
<div style="padding: .5em .9em .9em">
__NOTOC__
==About==
[[WolfWiki]] is a collaborative site for the ETPro / ETTV / BayonET community.

==Getting Started==
Anyone with a [http://bani.anime.net/banimod/forums/ Banimod Forums] account may edit pages. If you do not have an account, you may [http://bani.anime.net/banimod/forums/profile.php?mode=register apply] for one. Please follow the [[Help:Editing]] guidelines when editing pages. 
<hr>
<center>There are currently {{NUMBEROFARTICLES}} [[:Special:Allpages|articles available]].</center>
</div>
</td>

<td style="border: 1px solid #3e48fb; color: #000; background-color: #CAE1FF">
<div style="padding: .5em .9em .9em">
==[[:Category:ETPro|ETPro]]==
{{ETPro_Topics}}
==[[:Category:ETTV|ETTV]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=18 Discussion Forums] 
[[ETTV:Server Configuration|Server Configuration]] 
[[ETTV:Viewer's Guide|Viewer's Guide]] 

==[[:Category:BayonET|BayonET]]==
[http://bani.anime.net/banimod/forums/viewforum.php?f=10 Discussion Forums]

</div>
</td>

</tr>

</table>

__NOEDITSECTION__

User talk:Bani

2005-11-15T18:08:01Z

Fusen:

The best method to contact [[Bani]] is through the [http://bani.anime.net/banimod/forums/ Banimod Forums] [http://bani.anime.net/banimod/forums/privmsg.php?folder=inbox Private Messenging] system. Alternatively you may join the [[ETPro]] [[IRC]] channel and talk to him there, but be warned that the Bani Monster rarely talks.

"nicked" ooo look at Bani trying to be English ;P

Color Codes

2005-11-12T12:03:45Z

Fusen: little changes

==What are they?==
Colour codes are used to add colour to text. They were introduced in Quake III Arena and are available in most Q3 engine based games, including Enemy Territory. They can be used with most text that gets displayed ingame, such as player names, chat or notices.

'''Usage:''' a dash character ('''^''') followed by another character. Each character produces a different colour. 
'''Example:''' ^1red ^2green ^4blue 
'''Produces:''' red green blue 
==Codes list==
The image below depicts the colours the characters produce, except '''^0''' which, stands for black. Notice that some letters and digits produce the same colour. 
http://velocity.lunarpages.com/images/colors.jpg

==Code Filtering==
Here is a little php script that can be used to parse colorcodes and return the HTML formatted, colored string:
<pre>// ©2003 Deus@pooHunter.de
// This script uses the original RGB-values that were used in RtCW:OSP which I received directly from rhea.
// AFAIK these RGB values did not change in ET/ETPro
function parse_gamecolors($string)
{
$string = ereg_replace("(\^)?$", "^", $string);
$string = ereg_replace("\^\^", "&#94^", $string);
$string = ereg_replace("(\^)?$", "", $string);
$string = ereg_replace("\^<", "^|", $string);
$string = ereg_replace("\<", "<", $string);
$string = ereg_replace("\^>", "^^", $string);
$string = ereg_replace("\>", ">", $string);
$string = ereg_replace("\^\^", "^>", $string);
$string = "".$string."";

$color_def = array
(
0 => "#000000", 1 => "#FF0000", 2 => "#00FF00", 3 => "#FFFF00",
4 => "#0000FF", 5 => "#00FFFF", 6 => "#FF00FF", 7 => "#FFFFFF",
8 => "#FF7F00", 9 => "#7F7F7F", 10 => "#BFBFBF", 11 => "#007F00",
12 => "#7FFF00", 13 => "#00007F", 14 => "#7F0000", 15 => "#7F4000",
16 => "#FF9933", 17 => "#007F7F", 18 => "#7F007F", 19 => "#007F7F",
20 => "#7F00FF", 21 => "#3399CC", 22 => "#CCFFCC", 23 => "#006633",
24 => "#FF0033", 25 => "#B21919", 26 => "#993300", 27 => "#CC9933",
28 => "#999933", 29 => "#FFFFBF", 30 => "#FFFF7F"
);

$color_chardef = array
(
"#000000" => array ( 0 => "0", 1 => "P", 2 => "p" ),
"#FF0000" => array ( 0 => "1", 1 => "Q", 2 => "q" ),
"#00FF00" => array ( 0 => "2", 1 => "R", 2 => "r" ),
"#FFFF00" => array ( 0 => "3", 1 => "S", 2 => "s" ),
"#0000FF" => array ( 0 => "4", 1 => "T", 2 => "t" ),
"#00FFFF" => array ( 0 => "5", 1 => "U", 2 => "u" ),
"#FF00FF" => array ( 0 => "6", 1 => "V", 2 => "v" ),
"#FFFFFF" => array ( 0 => "7", 1 => "W", 2 => "w" ),
"#FF7F00" => array ( 0 => "8", 1 => "X", 2 => "x" ),
"#7F7F7F" => array ( 0 => "9", 1 => "Y", 2 => "y" ),
"#BFBFBF" => array ( 0 => ":", 1 => "Z", 2 => "z",
3 => ";", 4 => "[", 5 => "{" ),
"#007F00" => array ( 0 => "<", 1 => "\\", 2 => "|" ),
"#7FFF00" => array ( 0 => "=", 1 => "]", 2 => "}" ),
"#00007F" => array ( 0 => ">" ),
"#7F0000" => array ( 0 => "?" ),
"#7F4000" => array ( 0 => "@", 1 => "`" ),
"#FF9933" => array ( 0 => "A", 1 => "a", 2 => "!" ),
"#007F7F" => array ( 0 => "B", 1 => "b" ),
"#7F007F" => array ( 0 => "C", 1 => "c", 2 => "#" ),
"#007F7F" => array ( 0 => "D", 1 => "d", 2 => "$" ),
"#7F00FF" => array ( 0 => "E", 1 => "e", 2 => "%" ),
"#3399CC" => array ( 0 => "F", 1 => "f", 2 => "&" ),
"#CCFFCC" => array ( 0 => "G", 1 => "g", 2 => "'" ),
"#006633" => array ( 0 => "H", 1 => "h", 2 => "(" ),
"#FF0033" => array ( 0 => "I", 1 => "i", 2 => ")" ),
"#B21919" => array ( 0 => "J", 1 => "j" ),
"#993300" => array ( 0 => "K", 1 => "k", 2 => "+" ),
"#CC9933" => array ( 0 => "L", 1 => "l", 2 => "," ),
"#999933" => array ( 0 => "M", 1 => "m", 2 => "-" ),
"#FFFFBF" => array ( 0 => "N", 1 => "n", 2 => "." ),
"#FFFF7F" => array ( 0 => "O", 1 => "o", 2 => "/" )
);

for ($cd1 = 0; $cd1 < 31; $cd1++)
{
for ($cd2 = 0; $cd2 < count($color_chardef[$color_def[$cd1]]); $cd2++)
{
$string = str_replace("^". $color_chardef[$color_def[$cd1]][$cd2], "", $string);
}
}
return $string;
}
</pre>

B placebo

2005-11-08T17:03:22Z

Fusen:

== Magical Beginning ==

Strangley, When this cvar was found in the CVS tree for ETPro, there wasn't a name for the contributer next to it and to this day the ETPro devs don't know where it came from.

== Description ==

When using this cvar anything is possible, examples include; you will be given the sticky bullet syndrome and will be able to shoot people through the corner of walls when they run away.

'''Features Include'''

* You will not be as easily damaged by explosions ''(as long as you aren't too close to the explosion)''

* Your team will win every game ''(as long as your team are better than your enemies)''

* When defusing dynamite, it won't matter how far into the 30 seconds it is, you will always be able to defuse it on time. ''(as long as you start defusing before 5 seconds is left on the clock)''

* You can now jump twice as far as normally ''(Only works if you have 333fps)''

* Your grenades will hit the target with 100% damage ''(Depends if your grenade is actually close to the target)''

== Why keep it? ==

The cvar can't be removed as it has been hidden within the deepest of the ET source, so deep that even the magical Rain cannot find it.

== I Can't Find it ==

The cvar does not show up when you try and tab complete it within the console, you just have to insert it in your config and be rest assured that it works.

B placebo

2005-11-08T16:59:09Z

Fusen:

== Magical Beginning ==

Strangley, When this cvar was found in the CVS tree for ETPro, there wasn't a name for the contributer next to it and to this day the ETPro devs don't know where it came from.

== Description ==

When using this cvar anything is possible, examples include; you will be given the sticky bullet syndrome and will be able to shoot people through the corner of walls when they run away.

'''Features Include'''

* You will not be as easily damaged by explosions ''(as long as you aren't too close to the explosion)''

* Your team will win every game ''(as long as your team are better than your enemies)''

* When defusing dynamite, it won't matter how far into the 30 seconds it is, you will always be able to defuse it on time. ''(as long as you start defusing before 5 seconds is left on the clock)''

* You can now jump twice as far as normally ''(Only works if you have 333fps)''

* Your grenades will hit the target with 100% damage ''(Depends if your grenade is actually close to the target)''

== Why keep it? ==

The cvar can't be removed as it has been hidden within the deepest of the ET source, so deep that evil the magically Rain cannot find it.

== I Can't Find it ==

The cvar does not show up when you try and tab complete it within the console, you just have to insert it in your config and be rest assured that it works.

B placebo

2005-11-08T16:57:23Z

Fusen: Header

== Magical Beginning ==

Strangley, When this cvar was found in the CVS tree for ETPro, there wasn't a name for the contributer next to it and to this day the ETPro devs don't know where it came from.

== Description ==

When using this cvar anything is possible, you will be given the sticky bullet syndrome and will be able to shoot people through the corner of walls when they run away.

Features include;

* You will not be as easily damaged by explosions ''(as long as you aren't too close to the explosion)''

* Your team will win every game ''(as long as your team are better than your enemies)''

* When defusing dynamite, it won't matter how far into the 30 seconds it is, you will always be able to defuse it on time. ''(as long as you start defusing before 5 seconds is left on the clock)''

* You can now jump twice as far as normally ''(Only works if you have 333fps)''

* Your grenades will hit the target with 100% damage ''(Depends if your grenade is actually close to the target)''

== Why keep it? ==

The cvar can't be removed as it has been hidden within the deepest of the ET source, so deep that evil the magically Rain cannot find it.

== I Can't Find it ==

The cvar does not show up when you try and tab complete it within the console, you just have to insert it in your config and be rest assured that it works.

B placebo

2005-11-08T16:57:09Z

Fusen: wording

== Magically Beginning ==

Strangley, When this cvar was found in the CVS tree for ETPro, there wasn't a name for the contributer next to it and to this day the ETPro devs don't know where it came from.

== Description ==

When using this cvar anything is possible, you will be given the sticky bullet syndrome and will be able to shoot people through the corner of walls when they run away.

Features include;

* You will not be as easily damaged by explosions ''(as long as you aren't too close to the explosion)''

* Your team will win every game ''(as long as your team are better than your enemies)''

* When defusing dynamite, it won't matter how far into the 30 seconds it is, you will always be able to defuse it on time. ''(as long as you start defusing before 5 seconds is left on the clock)''

* You can now jump twice as far as normally ''(Only works if you have 333fps)''

* Your grenades will hit the target with 100% damage ''(Depends if your grenade is actually close to the target)''

== Why keep it? ==

The cvar can't be removed as it has been hidden within the deepest of the ET source, so deep that evil the magically Rain cannot find it.

== I Can't Find it ==

The cvar does not show up when you try and tab complete it within the console, you just have to insert it in your config and be rest assured that it works.

B placebo

2005-11-08T16:52:27Z

Fusen:

== Magically Beginning ==

Strangley, When this cvar was found in the CVS tree for ETPro, there wasn't a name for the contributer next to it and to this day the ETPro devs don't know where it came from.

== Description ==

When using this cvar anything is possible, you will be given the sticky bullet syndrome and will be able to shoot people through the corner of walls when they run away.

Features include;

* You will not be as easily damaged by explosions ''(as long as you aren't too close to the explosion)''

* Your team will win every game ''(as long as your team is better than your enemies)''

* When defusing dynamite, it won't matter how far into the 30 seconds it is, you will always be able to defuse it on time. ''(as long as you start defusing before 5 seconds is left on the clock)''

* You can now jump twice as far as normally ''(Only works if you have 333fps)''

* your grenades will hit the target with 100% damage ''(Depends if your grenade is actually close to the target)''

== Why keep it? ==

The cvar can't be removed as it has been hidden within the deepest of the ET source, so deep that evil the magically Rain cannot find it.

== I Can't Find it ==

The cvar does not show up when you try and tab complete it within the console, you just have to insert it in your config and be rest assured that it works.

TrickJumpGhosts

2005-11-07T21:58:15Z

Fusen:

Trickjumpghosts or tjg's in short are fake players that playback a recorded movement.
You can use them in two ways, the first one is the easy to use one (with a build-in menu), the second one is the console-way but gives you more possibilities. Important: cheats must be enabled before you can use this tool.

== The Menu Way ==

To use the menu you have to bind the console command to a key.

''Example: '''/bind tjg_menu'''''

http://www.twwwo.be/etpro/docs/tjg/tjg_menu.jpg

As you can see there are five menu items:

* Record: this starts recording your movements.
* Stop: this stops your movement recoring.
* Quicksave: if you want to save your impressive jump into a file so you can share it with your friends, use this option.
* Quickload: this loads the last Quicksaved trickjumpghost, if you want to load other tjg files you have to use the console.
* Play: play a recorded/loaded ghost back.
* Pause: pause the playback.
* Effects: none - flicker - ghost - fire - fire only

== The Console Way ==

Open the console and type the commando '''/tjg_info''', this will give you detailed information about all the tjg cmd's and cvars.

* tjg_record : starts recording your movements
* tjg_play : plays back a recorded ghost
* tjg_stop : stops playing or recording
* tjg_pause : pauses/resumes the ghost playback
* tjg_menu : a convenient menu for the tjg tools
* tjg_save : saves a recording to a file
* tjg_load : loads a recording from a file

TrickJumpLines

2005-11-07T21:53:49Z

Fusen:

Trickjumplines or tjl's in short are lines that trace the path of your movement.

http://www.twwwo.be/etpro/docs/tjl/tjl_inaction.jpg

You can use them in two ways, the first one is the easy to use one (with a build-in menu), the second one is the console-way but gives you more possibilities. Important: cheats must be enabled before you can use this tool.

===The Menu Way===

To use the menu you have to bind the console command to a key.

''Example:'' '''/bind tjl_menu'''

http://www.twwwo.be/etpro/docs/tjl/tjl_menu.jpg

As you can see there are five menu items:

* Record: this starts recording your movements.
* Stoprecord: this stops your movement recoring.
* Quicksave: if you want to save your impressive jump into a file so you can share it with your friends, use this option.
* Quickload: this loads the last Quicksaved trickjumpline, if you want to load other tjl files you have to use the console.
* Draw slot: this toggles the drawing of the current slot.

All these actions are executed on the slotnumber set in the cvar '''*b_tjl_quickslot*''', you can use a maximum of 10 slots.

===The Console Way===

Open the console and type the commando '''/tjl_info''', this will give you detailed information about all the tjl cmd's and cvars.

* tjl_startrecord <clientnum> <slot> OR <slot> | no parameters records your own movements: starts recording your movements
* tjl_stoprecord : stops recording your movements
* tjl_drawslot <slot> OR <slot> <color> : draws a given slot (toggle) b_tjl_color must be set to -1 in order to use this option
* tjl_save <filename> <slot> : saves the current slot into a file
* tjl_load <filename> <slot> : loads the current file into a slot
* tjl_menu : a nice menu to easy use the tjl tools
* b_tjl_draw <1/0> : draws a recorded movement
* b_tjl_stoponnomove <1/0> : stops recording when not moving
* b_tjl_color <hex value> : default linecolor
* b_tjl_showmaxspeed <1/0>: shows the players max speed at that point on the line
* b_tjl_stepsize <number> : the distance between two points on the line, if you want to draw much long lines, use a big stepsize
* b_tjl_quickslot <number> : this slotnumber is used when u use the tjl_menu

===Other benefits of the trickjumplines===

You can use the trickjumplines to teach your tactics to your teammates, by showing them the places where they have to move to.
Or custommapmakers can include some tjl's into their pk3's so people can use them to learn the shortest path to the objectives.

http://www.twwwo.be/etpro/docs/tjl/tjl_tactics.jpg

TrickJumpLines

2005-11-07T21:52:50Z

Fusen:

Trickjumplines or tjl's in short are lines that trace the path of your movement.

http://www.twwwo.be/etpro/docs/tjl/tjl_inaction.jpg

You can use them in two ways, the first one is the easy to use one (with a build-in menu), the second one is the console-way but gives you more possibilities. Important: cheats must be enabled before you can use this tool.

==The Menu Way==

To use the menu you have to bind the console command to a key.

''Example:'' '''/bind tjl_menu'''

http://www.twwwo.be/etpro/docs/tjl/tjl_menu.jpg

As you can see there are five menu items:

* Record: this starts recording your movements.
* Stoprecord: this stops your movement recoring.
* Quicksave: if you want to save your impressive jump into a file so you can share it with your friends, use this option.
* Quickload: this loads the last Quicksaved trickjumpline, if you want to load other tjl files you have to use the console.
* Draw slot: this toggles the drawing of the current slot.

All these actions are executed on the slotnumber set in the cvar '''*b_tjl_quickslot*''', you can use a maximum of 10 slots.

==The Console Way==

Open the console and type the commando '''/tjl_info''', this will give you detailed information about all the tjl cmd's and cvars.

* tjl_startrecord <clientnum> <slot> OR <slot> | no parameters records your own movements: starts recording your movements
* tjl_stoprecord : stops recording your movements
* tjl_drawslot <slot> OR <slot> <color> : draws a given slot (toggle) b_tjl_color must be set to -1 in order to use this option
* tjl_save <filename> <slot> : saves the current slot into a file
* tjl_load <filename> <slot> : loads the current file into a slot
* tjl_menu : a nice menu to easy use the tjl tools
* b_tjl_draw <1/0> : draws a recorded movement
* b_tjl_stoponnomove <1/0> : stops recording when not moving
* b_tjl_color <hex value> : default linecolor
* b_tjl_showmaxspeed <1/0>: shows the players max speed at that point on the line
* b_tjl_stepsize <number> : the distance between two points on the line, if you want to draw much long lines, use a big stepsize
* b_tjl_quickslot <number> : this slotnumber is used when u use the tjl_menu

==Other benefits of the trickjumplines==

You can use the trickjumplines to teach your tactics to your teammates, by showing them the places where they have to move to.
Or custommapmakers can include some tjl's into their pk3's so people can use them to learn the shortest path to the objectives.

http://www.twwwo.be/etpro/docs/tjl/tjl_tactics.jpg

TrickJumpLines

2005-11-07T21:52:04Z

Fusen:

Trickjumplines or tjl's in short are lines that trace the path of your movement.

http://www.twwwo.be/etpro/docs/tjl/tjl_inaction.jpg

You can use them in two ways, the first one is the easy to use one (with a build-in menu), the second one is the console-way but gives you more possibilities. Important: cheats must be enabled before you can use this tool.

==== The Menu Way ====

To use the menu you have to bind the console command to a key.

''Example:'' '''/bind tjl_menu'''

http://www.twwwo.be/etpro/docs/tjl/tjl_menu.jpg

As you can see there are five menu items:

* Record: this starts recording your movements.
* Stoprecord: this stops your movement recoring.
* Quicksave: if you want to save your impressive jump into a file so you can share it with your friends, use this option.
* Quickload: this loads the last Quicksaved trickjumpline, if you want to load other tjl files you have to use the console.
* Draw slot: this toggles the drawing of the current slot.

All these actions are executed on the slotnumber set in the cvar '''*b_tjl_quickslot*''', you can use a maximum of 10 slots.

==== The Console Way ====

Open the console and type the commando '''/tjl_info''', this will give you detailed information about all the tjl cmd's and cvars.

* tjl_startrecord <clientnum> <slot> OR <slot> | no parameters records your own movements: starts recording your movements
* tjl_stoprecord : stops recording your movements
* tjl_drawslot <slot> OR <slot> <color> : draws a given slot (toggle) b_tjl_color must be set to -1 in order to use this option
* tjl_save <filename> <slot> : saves the current slot into a file
* tjl_load <filename> <slot> : loads the current file into a slot
* tjl_menu : a nice menu to easy use the tjl tools
* b_tjl_draw <1/0> : draws a recorded movement
* b_tjl_stoponnomove <1/0> : stops recording when not moving
* b_tjl_color <hex value> : default linecolor
* b_tjl_showmaxspeed <1/0>: shows the players max speed at that point on the line
* b_tjl_stepsize <number> : the distance between two points on the line, if you want to draw much long lines, use a big stepsize
* b_tjl_quickslot <number> : this slotnumber is used when u use the tjl_menu

==== Other benefits of the trickjumplines ====

You can use the trickjumplines to teach your tactics to your teammates, by showing them the places where they have to move to.
Or custommapmakers can include some tjl's into their pk3's so people can use them to learn the shortest path to the objectives.

http://www.twwwo.be/etpro/docs/tjl/tjl_tactics.jpg

Target location

2005-11-07T21:44:19Z

Fusen:

== For Maps In Production ==

A ''target_locations'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_locations on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations to a map you will have acces to the following commands:

===Loc_commands===

'''Loc_add <message>'''
:Add a new target_location at your current position whit name <message>

'''Loc_del'''
:Deletes the target_location that you are currently "in"

'''Loc_move'''
:Moves the target_location that you are currently "in" to your current position

'''Loc_rename <message>'''
:Renames the target_location that you are currently "in" to <message>

'''Loc_show'''
:Shows the target_location that you are currently "in" as text in console

'''Loc_save'''
:Saves all target_locations to a file (maps/''mapname''_loc_override.dat)

'''Loc_load'''
:Reloads all target_locations from a file (maps/''mapname''_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location
ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of
white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people
to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

''NOTE: while using '''b_debuglocations''' make sure you use '''loc_save''' a lot, this is becase of engine limits the client can crash while drawing to many sprites''

Target location

2005-11-07T21:43:54Z

Fusen:

Target location

2005-11-07T21:43:06Z

Fusen:

== For Maps In Production ==

A ''target_locations'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_locations on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations to a map you will have acces to the following commands:

===Loc_commands===

'''Loc_add <message>'''
:Add a new target_location at your current position whit name <message>

'''Loc_del'''
:Deletes the target_location that you are currently "in"

'''Loc_move'''
:Moves the target_location that you are currently "in" to your current position

'''Loc_rename <message>'''
:Renames the target_location that you are currently "in" to <message>

'''Loc_show'''
:Shows the target_location that you are currently "in" as text in console

'''Loc_save'''
:Saves all target_locations to a file (maps/''mapname''_loc_override.dat)

'''Loc_load'''
:Reloads all target_locations from a file (maps/''mapname''_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people
to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

''NOTE: while using '''b_debuglocations''' make sure you use '''loc_save''' a lot, this is becase of engine limits the client can crash while drawing to many sprites''

Target location

2005-11-07T21:41:19Z

Fusen:

== For Maps In Production ==

A ''target_locations'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_locations on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations to a map you will have acces to the following commands:

===Loc_commands===

'''Loc_add <message>'''
:Add a new target_location at your current position whit name <message>

'''Loc_del'''
:Deletes the target_location that you are currently "in"

'''Loc_move'''
:Moves the target_location that you are currently "in" to your current position

'''Loc_rename <message>'''
:Renames the target_location that you are currently "in" to <message>

'''Loc_show'''
:Shows the target_location that you are currently "in" as text in console

'''Loc_save'''
:Saves all target_locations to a file (maps/''mapname''_loc_override.dat)

'''Loc_load'''
:Reloads all target_locations from a file (maps/''mapname''_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

''NOTE: while using '''b_debuglocations''' make sure you use '''loc_save''' a lot, this is becase of engine limits the client can crash while drawing to many sprites''

Physics cvars

2005-11-07T21:07:44Z

Fusen:

Since Quake 3, the function that's responsible for game physics ''(amongst other things)'' is named Pmove(). Normally, this function is run once every client frame, and this is where framerate-dependant physics (most notably jump heights) come from. pmove_fixed is an attempt to level the playing field by running this function at a fixed rate ''(every pmove_msec milliseconds.)'' The default pmove_msec of 8 is equivalent to normal physics at 1000 / 8 = 125 frames/second.

* '''pmove_fixed''' can be set on either the client or the server--the client will default to the value on the server ''(And, on non-ETPro servers, it will be reset to the value of the server quite frequently due to some silliness in the code.)'' pmove_msec can only be set on the server side.

* '''b_fixedphysics''' is a server-side setting with similar goals to pmove_fixed. b_fixedphysics 1 avoids rounding the velocity at all ''(Removing the framerate-dependent behavior in movement)''; however, it offers b_fixedphysicsfps to adjust the jump velocity to emulate the old framerate-dependent behavior. This is the best of both worlds—no movement speed problems ''(as several people observed at 333fps)'' nor any of the problems that pmove_fixed brings with it ''(some parts of the game behave poorly at high fps, most notably mounted MG42 and mortar aiming)'', but the same jump heights trickjumpers would kill us for taking away. b_fixedphysics 2 is a cross between normal behavior and fixed behavior, which effectively just caps the maximum framerate-dependent behavior to 166fps.

* '''b_optimizedprediction''' is a client-side setting that ''(theoretically)'' has no effect other than increasing performance. Basically, etmain ''(and RTCW, and Q3)'' will re-do all the physics computations for up to the previous 64 frames in order to figure out where you should be for the current one. b_optimizedprediction will store the result of the previous computations and reuse them ''(Only if the results look acceptable based on the latest data the client has from the server)'' instead of doing all the math again. This provides a rather dramatic performance boost, especially if you have a high ping.

Extended ASCII

2005-11-07T21:02:11Z

Fusen:

== Extended ASCII Characters in ET Pro 3 ==

In ET Pro 3.0.1, you are finally able to use extended ASCII characters as you could in RTCW. Not all of these characters work outside of the console, but they do exist should you feel a need to use them.

http://games.theteamkillers.net/rtcw/etpro/ascii/ascii-con.png

http://games.theteamkillers.net/rtcw/etpro/ascii/ascii-nocon.png

The two images above display a table of all ASCII characters allowed in ET Pro 3, the top image displaying what it appears as in the console and the bottom displaying what it appears as in-game.

To use these characters, you can (if you're using Windows) use alt+xxxx, where xxxx is a series of numbers. ''(found using the Character Map, usually found in '''Start''' -> '''Programs''' -> '''Accessories''' -> '''System''' -> '''Character Map'''.)'' If you prefer not to use this method, there's another easy way - you can use the a two-character hex code to represent the ASCII character. Each time you see a "=XX" in the screenshot above, the =XX is the hex code that represents the ASCII character to the right of it.

If you try to use these in game (e.g. '''/vsay hi =aaHELLO=ab''') you'll soon find that it won't display them right away. To make the game recognize them, you'll have to run them through cmd - such as '''/cmd vsay hi =aaHELLO=ab'''. Without the essential cmd, your characters will come out completely normal.

The code used to generate the above script was written by Rain. Here's the config, aptly named ascii.cfg:

<pre>echo "00: 01:� 02:� 03:� 04:� 05: 06:� 07: 08:� 09: 0A: 0B: 0C:� 0D: 0E:� 0F:� "
echo "10:� 11:� 12:� 13:� 14:� 15:� 16:� 17:� 18:� 19:� 1A:� 1B:� 1C:� 1D:� 1E:� 1F:� "
echo "20: 21:! 22: 23:# 24:$ 25:% 26:& 27:' 28:( 29:) 2A:* 2B:+ 2C:, 2D:- 2E:. 2F:/ "
echo "30:0 31:1 32:2 33:3 34:4 35:5 36:6 37:7 38:8 39:9 3A:: 3B:; 3C:< 3D:= 3E:> 3F:? "
echo "40:@ 41:A 42:B 43:C 44:D 45:E 46:F 47:G 48:H 49:I 4A:J 4B:K 4C:L 4D:M 4E:N 4F:O "
echo "50:P 51:Q 52:R 53:S 54:T 55:U 56:V 57:W 58:X 59:Y 5A:Z 5B:[ 5C:\ 5D:] 5E:^^* 5F:_ "
echo "60:` 61:a 62:b 63:c 64:d 65:e 66:f 67:g 68:h 69:i 6A:j 6B:k 6C:l 6D:m 6E:n 6F:o "
echo "70:p 71:q 72:r 73:s 74:t 75:u 76:v 77:w 78:x 79:y 7A:z 7B:{ 7C:| 7D:} 7E:~ 7F: "
echo "80:€ 81: 82:‚ 83:ƒ 84:„ 85:… 86:† 87:‡ 88:ˆ 89:‰ 8A:Š 8B:‹ 8C:Œ 8D: 8E:Ž 8F: "
echo "90: 91:‘ 92:’ 93:“ 94:” 95:• 96:– 97:— 98:˜ 99:™ 9A:š 9B:› 9C:œ 9D: 9E:ž 9F:Ÿ "
echo "A0: A1:¡ A2:¢ A3:£ A4:¤ A5:¥ A6:¦ A7:§ A8:¨ A9:© AA:ª AB:« AC:¬ AD: AE:® AF:¯ "
echo "B0:° B1:± B2:² B3:³ B4:´ B5:µ B6:¶ B7:· B8:¸ B9:¹ BA:º BB:» BC:¼ BD:½ BE:¾ BF:¿ "
echo "C0:À C1:Á C2:Â C3:Ã C4:Ä C5:Å C6:Æ C7:Ç C8:È C9:É CA:Ê CB:Ë CC:Ì CD:Í CE:Î CF:Ï "
echo "D0:Ð D1:Ñ D2:Ò D3:Ó D4:Ô D5:Õ D6:Ö D7:× D8:Ø D9:Ù DA:Ú DB:Û DC:Ü DD:Ý DE:Þ DF:ß "
echo "E0:à E1:á E2:â E3:ã E4:ä E5:å E6:æ E7:ç E8:è E9:é EA:ê EB:ë EC:ì ED:í EE:î EF:ï "
echo "F0:ð F1:ñ F2:ò F3:ó F4:ô F5:õ F6:ö F7:÷ F8:ø F9:ù FA:ú FB:û FC:ü FD:ý FE:þ FF:ÿ "
</pre>

Players Allies

2005-11-07T20:54:39Z

Fusen:

The serverinfo cvars ''Players_Axis'',''Players_Allies'' have been removed from etpro.

== Reasons ==
The cvars could get very long, in some cases so long that they would overflow the serverinfo string and crash the server.
There was no way to associate spectator client ID#'s with listed players, nor players who had not yet finished connecting.

== Solution ==

ETPro introduces a new cvar which is shorter (so it doesn't overflow the serverinfo string and cause server crashes), easier to parse, and allows for associating player client ID's in all cases.

== Format ==

The new cvar is P, and probably the easiest way to show its usage is by example:

<pre>29 frags 30ms bani
106 frags 20ms rain
189 frags 50ms zinx
63 frags 32ms fretn
43 frags 96ms duke'ku
0 frags 999ms ikkyo
100 frags 56ms majikthise
22 frags 108ms boco
31 frags 101ms vio
0 frags 44ms ohayden

P=--------221120111-3</pre>

In this case the first 8 server slots are empty (client id 0-7), probably private server slots. bani and rain are client ids 8 and 9, both allies. zinx and fretn are client ids 10 and 11, both axis. duke'ku is allied in client id 12. ikkyo is still connecting in client id 13 and has not been assigned a team yet. majikthise, boco and vio are all axis in slots 14-16. slot 17 is empty. slot 18 is ohayden as spectator.

Players

2005-11-07T20:54:34Z

Fusen:

Target location

2005-11-07T20:50:02Z

Fusen:

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

<nowiki>***</nowiki> '''AWOL''' ***

Target location

2005-11-07T20:49:50Z

Fusen:

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== Locations For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

<nowiki>***</nowiki> '''AWOL''' ***

Target location

2005-11-07T20:49:01Z

Fusen:

== Target_location for maps in production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== Locations For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

<nowiki>***</nowiki> '''AWOL''' ***

ETPro:Pluggable Config Files

2005-11-07T16:30:10Z

Fusen:

DrawFPS

2005-11-05T16:32:11Z

Fusen:

The FPS counter in ETPro is been extended from the default setting.

There are now three different settings you can use to show more detailed information about your frames per second.

'''cg_DrawFPS 2'''
Draws a more accurate fps meter, it updates every second

'''cg_DrawFPS 3'''
Draws the time needed to render a frame in milliseconds

'''cg_DrawFPS >3'''
The same as 2 but here you can you specify the time in milliseconds between two updates

AntiWarp

2005-11-05T16:23:49Z

Fusen:

ET Pro implements an antiwarp system to keep players from "warping" or "teleporting" around, accidentally or intentionally.

== Controlling the antiwarp system ==

'''b_antiwarp''' controls the antiwarp system. The possible settings are:
<pre>0 - disabled. ET Pro does no antiwarp at all.
1 - enabled (default). ET Pro keeps players from "warping"</pre>

== What is "warping" ==

"Warping" occurs when the server recieves several new commands for a player in a very short period of time. This happens because packets from the player were lost or never sent. The player will appear to cross a great distance in a very short period of time, making them hard to hit and possibly allowing them to avoid landmine damage.

== How the antiwarp system keeps players from warping ==

The antiwarp system in ET Pro delays commands when they are recieved too quickly. Thus, when a player sends 700ms worth of commands in 50ms, the commands will be spread out over 700ms, causing the player to move smoothly to other players. This affects the player who sent the commands too quickly only by increasing their ping, and will not keep increasing ping endlessly - at maximum, the added ping is the highest ping the player is actually getting. If temporary network issues cause ping to increase beyond a sensible number, the player can stand still for a moment and their ping will normalize.

Hitsounds

2005-11-05T16:19:50Z

Fusen:

ETPro uses hitsounds like those used in Quake 3 Arena, hitsounds are sounds that are played when you hit another player, there are three different instances when a sound will play:

* When you shoot an enemy
* When you shoot an enemy in the head hitbox
* When you shoot a teammate

== Using Hitsounds ==

The hitsounds are controlled by the cvar '''b_hitsounds'''
There are three different settings that can be used with this cvar;

<pre>1 = On, All sounds are used
0 = Off, No sounds are used
2 = A sound occurs only when you get a headshot</pre>

Hitsounds

2005-11-05T16:17:46Z

Fusen:

ETPro uses hitsounds like those used in Quake 3 Arena, hitsounds are sounds that are played when you hit another player, there are three different instances when a sound will play:

* When you shoot an enemy
* When you shoot an ememy in the head hitbox
* When you shoot a teammate

== Using Hitsounds ==

The hitsounds are controlled by the cvar '''b_hitsounds'''
There are three different settings that can be used with this cvar;

<pre>1 = On, All sounds are used
0 = Off, No sounds are used
2 = A sound occurs only when you get a headshot</pre>

Hitsounds

2005-11-05T16:12:20Z

Fusen:

etpro has now hitsounds as in quake3arena, hitsounds are a sounds that are played when you hit somebody, there are three different sounds:

* one when you hit an enemy
* one when you shoot a headshot on an enemy
* one when you hit a teammate

the hitsounds are controlled by the cvar b_hitsounds

<pre>1 = On
0 = Off
2 = Headshots Only</pre>

Cvar Restrictions

2005-11-05T16:11:00Z

Fusen:

The sv_cvar setting is for the etpro cvar range enforcement mechanism. Its similar to PunkBuster's cvar range checking in that it uses nearly the same syntax. However it is different in that instead of simply warning the user that their cvars are out of range, it actually forces them to server-enforced values. This is used as it is better than having players scrambling to type in the console trying to get their cvars into compliance before they get kicked by PunkBuster.

== Possibilities: ==

* sv_cvar ''cvarname'' '''EQ''' value
* sv_cvar ''cvarname'' '''GE''' value
* sv_cvar ''cvarname'' '''LE''' value
* sv_cvar ''cvarname'' '''WITHBITS''' bitflag
* sv_cvar ''cvarname'' '''WITHOUTBITS''' bitflag
* sv_cvar ''cvarname'' '''IN''' low_value high_value
* sv_cvar ''cvarname'' '''OUT''' low_value high_value
* sv_cvar ''cvarname'' '''INCLUDE''' substring default
* sv_cvar ''cvarname'' '''EXCLUDE''' substring default

== EQ ==
EQ requires one argument. 
EQ is used when a cvar is supposed to EQual a certain value.

== GE ==

GE requires one argument. 
GE is used when a cvar is supposed to be Greater or Equal a certain value.

== LE ==

LE requires one argument. 
LE is used when a cvar is supposed to be Lower or Equal a certain value.

== WITHBITS ==

WITHBITS requires one argument 
WITHBITS is used when a bitmask-cvar is supposed to include a certain bitflag 
Exclamation For further information regarding bitmask-cvars look here

== WITHOUTBITS ==

WITHOUTBITS requires one argument 
WITHOUTBITS is used when a bitmask-cvar is supposed to not include a certain bitflag 
Exclamation For further information regarding bitmask-cvars look here 

== IN ==

IN requires two arguments 
With the IN enforcement, cvars that are non compliant are snapped to the nearest IN parameter.

Example:
<pre>sv_cvar cg_fov IN 90 120

A player who had a cg_fov of 40 would see it snapped to 90.

A player who had a cg_fov of 130 would see it snapped to 120.</pre>

Exclamation 1st Argument = lower limit
Exclamation 2nd Argument = upper limit

== OUT ==

OUT requires two arguments

With the OUT enforcement, cvars that are non compliant are snapped to the nearest OUT parameter.

Example:
<pre>sv_cvar m_pitch OUT -0.015 0.015

A player who had a m_pitch of -0.010 would see it snapped to -0.015.

A player who had an m_pitch of 0.04 would see it snapped to 0.015.

A player who had an m_pitch of 0.00 (a value equidistant from both lower and upper bounds) would be snapped to the lower bound -0.015.</pre>
Exclamation 1st Argument = lower limit
Exclamation 2nd Argument = upper limit

== INCLUDE ==

INCLUDE requires two arguments
INCLUDE is used when a cvar is supposed to include a certain substring. Otherwise it will set the cvar to default.

== EXCLUDE ==

EXCLUDE requires two arguments
EXCLUDE is used when a cvar is supposed to not include a certain substring. Otherwise it will set the cvar to default.

Exclamation If a cvar is changed that needs a vid_restart, etpro will force a vid_restart on the client after snapping them into range.