This feature allows you to sit on your lazy ass while watching a MultiView Demo (MVD) and let the client switch POVs to the best player for you. To tell the client who is THE BEST player, you have the possibility to specify an equation wich will then be evaluated for every player, giving the player a 'value'. During the playback the player with highest value will be tracked.
This value can be seen by using 'mvd_info 1' and 'mvd_info_setup %n %v' wich will show something like "Johnny_cz -6" :).
In the equation you are allowed to use the standard math operations +-/* and parentheses ().
This will get the current gametype and select one of the following:
This will use mvd_autotrack_custom
Only works in combination with cl_multiview. Then you can use different equation for each window using these variables:
You can specify constants used in your equations like 'value of Quad', 'value of Pent', 'value of Nailgun' ;-).
All these mvd_autotrack_*_values variables consist of 14 numbers. Each number is a value assigned to given item, armor or powerup according to this table:
1 | Axe |
2 | Shotgun |
3 | Supershotgun |
4 | Nailgun |
5 | Supernailgun |
6 | Grenadelauncher |
7 | Rocketlauncher |
8 | Lightninggun |
9 | Green Armor |
10 | Yellow Armor |
11 | Red Armor |
12 | Ring Powerup |
13 | Quad Powerup |
14 | Pent Powerup |
Example:
mvd_autotrack_1on1_values "0 1 2 1 2 4 6 6 0.5 0.3 1.3 50 200 2000"
These constants are used in the %-variables. Example:
There are lots of variables available for you to be used with %. Most of these variables can be seen with 'mvd_status 1'.
Notes:
%a | - is the current amount of armor a player has |
%A | - is the value of the current armor type |
%c | - current run time |
%C | - current run frags |
%d | - current run teamfrags |
%f | - overall frags |
%F | - overall teamfrags |
%g | - deaths |
%h | - current amount of health |
%I(big i) | - taken Supershotguns |
%j | - taken Nailguns |
%J | - taken Supernailguns |
%k | - taken Grenadelaunchers |
%K | - dropped Grenadelaunchers (left in pack when player died) |
%l(small L) | - taken Rocketlaunchers |
%L | - dropped Rocketlaunchers |
%m | - taken Lightningguns |
%M | - dropped Lightningguns |
%n | - taken Megahealths |
%N | - taken green armors |
%o | - taken yellow armors |
%O | - taken red armors |
%p | - added powerupvalues player currently has |
%q | - Axe kills |
%Q | - Shotgun kills |
%r | - Supershotgun kills |
%R | - Nailgun kills |
%s | - Supernailgun kills |
%S | - Grenadelauncher kills |
%t | - Rocketlauncher kills |
%T | - Lightninggun kills |
%v | - average run time |
%V | - average run frags |
%w | - average run teamfrags |
%W | - best weapon value |
%x | - taken Rings |
%y | - taken Quads |
%z | - taken Pents |
Easy one first :)
%f
Now to make it more sophisticated:
%f/(%g+2*%F)
For a more numbery look lets say
player 1 | - 3 frags, 5 teamkills and 4 deaths (your average teamplay newbie) |
player 2 | - 12 frags, 1 teamkill and 2 deaths (your not so average guy with a quad run) |
for player 1 it would be 3/(4+2*5) = 0.214285714
for player 2 it would be 12/(2+2*1) = 3
meaning player 2 would be tracked.
There are no limitations to how often you can use a value or how high you want to set the values or the static numbers in the algorythm. There is one limitation thats when the number is longer than 4096 digits but in that case mvd_autotrack would disable itself.
Last update: 08.02.2008 08:38 UTC
ezQDocs