Replies: 2 comments
-
After some thought, I found that it should be better to have 4 (16 if you a kind of variables for all variables, for example: %fa, %fb, %fc, %fd. |
Beta Was this translation helpful? Give feedback.
-
I will look into this when I get time, thanks. |
Beta Was this translation helpful? Give feedback.
-
I've found some variables that are very close to what I wanted for them to do for mvd_auto_track_custom (%C and %c), although, instead of considering "what I did in this entire run" or "how much time I survived in this run", it uses "what I already did in this run" or "how much time I'm surviving". I want to use (%C-3)/%c) in the second specified way, with it, I will be able to see players that did at least 3 kills, but it will be focusing the player who did those kills in less time. In this case, a cvar that changes the behavior of the tracker by using all they did in a run instead of what they currently did in the run I watch, I think a cvar would be better because I don't find anything to mix variables from the first method with the second method, not sure if there is anything that would be good to mix.
%c is a time value which starts at 0, meaning that if you pick any variable and divide by it, you will get an division by 0 error in the console, in those cases, just giving 0 in the result of division will solve the problem.
The frag variables should have a damage version of them so that it is possible to consider players that causes damage but doesn't kill other players as trackeable/skilled players, also one damage variable that picks damage but only the damage that wasn't healed by the damaged player.
Beta Was this translation helpful? Give feedback.
All reactions