I meant player KD is Kill:Death ratio and player KD actual is Kill:Death ratio in game.
//well the actual KD would be limited (or modified) because we dont want to have KD 13 (13:1)..

Of COURSE, we doesnt want to make machine which will know who will win.. we cant -> eg. AFAIK the engine doesnt support stats of healing, etc.
We just want the most precise autobalance we can..

Hmm the player KD maybe could be the one from the Maps stats (to be more precise -> how is the player good on this map), and of course count somehow skill too (because player with same ratios, i think the one with higher skill is better).
And yes a player could be switched only once per map, thats ok..

Autobalance is ran every 2 minutes, no one complain about that (except when they just joined, are switched quickly and get the "stats points will be removed" message hehe)...

...but you don't know about it cause moderators and admins are not switched

Ok you are talking about causes which make you get a good ratio or a bad one. Let's say we keep thinking in the scope of what B3 is able to do and try to improve the gameplay, because I'm not sure anything else would be useful =)
The most interesting base components for the algorithm are probably :

=> Player level
- total kills and deaths
- total number of rounds played
- xlrstats skills value
- rank (based on xlrstats skills)
- time spent on the server for the current month
- total number of teamkills/teamdeaths
- number of kills and deaths per map
- current kills and deaths
- date of the last auto team switching

=> Server level
- current red and blue teams scores
- current map
- amount of time since the current round started
- amount of time until the round ends

I'm sure I forgot some... So here is the challenge : find the algorithm which will keep the teams balanced and players happy, you have 1 week
If some are interested I could write a basic B3 plugin to implement easily algorithms and test them.

Thanks, good to read that

_________________
ut4_he_tennis_v0.1
-------------------------
"We are talking about computers here, compared to those I can read women like a book ;P"
Unclefragger

You just use special sneaky french cheats we dont understand, sva.

anyways: i read 'xlrstats' and then think 'hmm that isnt really reliable'
since i hav crappy stats and manage to shoot most of u, and b3 and autobalance also dont take into account good rounds/days bad rounds/days.. so basicly it will always be unbalanced for one reason or another.

But gl on that algorithm thingy.

_________________

I think the current ratio is a good indicator whether your are in good or bad shape for a given round, at least it's the less worse.

Except if admins and mods online think about switching to balance the game =) (and are able to...)

Still pissed of against french people cause of strikes ?

_________________
ut4_he_tennis_v0.1
-------------------------
"We are talking about computers here, compared to those I can read women like a book ;P"
Unclefragger

Btw, just a hint if anyone intends to ever write that algorithm: IMO K-D would be better than K/D because there's no division by zero and there is no 1:0 score meaning infinite ratio, or 3:1 (by a lame camper in a non-populated place where noone cares to kill him) being better than say 30:15.

_________________
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«

Healing stats will be really good thingie and motivation for players to heal teammates.
Actually is it possible to make it?

Game does not log healing, so b3/xlr can't find out about any healing done in-game.

_________________
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«

maybe write a little code into the game that _does_ log healing?

_________________

it's in the game code

_________________
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."
- Martin Golding

_________________