Maverick

If the bot picks the player that died last when the teams need to be evened (at the begin of the 30 seconds period) then it doesn't pick the last one that died; there will be another player that died in the 30 seconds period.

pointless

God you really dont understand it eh... The bot keeps a list of players of who died, per team. So there are two lists that the bot maintains. (two teams) Once someone dies, he gets added to the bottom of the list (of that team). As soon as the teams need to be evened AND the 30 seconds time period has passed that bot picks the last player (the player at the bottom of the list) of the desired team and evens him. If that player is not on the team, is not in a ship or just can't be found, it will pick the player before the current one in the list. If it can't find a player in the list (50 players per list) then it will even a player randomly. I doubt this will ever hapen. Finally, the bot removes the evened player from the list to avoid errors. So it DOESN'T record people's deaths after the 30 seconds have been announced. Anyway, I will try to change the team evener to do what you say, Raem. To conclude; the only problem with the team evener is the possible loss of bounty or ?buy'ed stuff.

pointless

I don't know what you are talking about. Its not like the bot treats people differently. That will disturb game balance and gameplay

lol DKR is right about the first 3 lines

I hate people that hate people that hate people that hate people that hate

Raem, it takes alot of effort to recode the bot to do it the way you spoke off. Even then, it won't solve the problems. People don't want to switch by themselves. Considering the structure of the team evener, I doubt its even possible to have it do this. In his dreams I'm not infatuated with supposed limitations. <{POST_SNAPBACK}> Then don't reply here anymore. Everything has limitations, also Mervbot and I can't help it. Alot of people already told you numerous of times that Mervbot is not able to see whether a player has bought bounce / super / bricks.

pointless

lol Raem, that is not doable right now. Its streching the limit. Switching the one who has been on the freq the least amount of time is not solving the problem either. As madhaha has said its not very convenient for the one who has just joined. Secondly it doesn't prevent the loss of bounce / bounty / super. Instead of this, the one who has died last would be better to get switched - but for people balling isnt this a good solution either. Any other ideas people?

pointless

pointless...

Exactly, it holds a buffer of 50 players who died last. So if it can't get the last, it will get the one before that - and so on. When it totally can't find the last one to die then it will even someone randomly. This is only as a precaution because the bot will always find someone in the list of 50 players (2x50 players that is - 2 teams).

congrats (WOO page 44 )

Past week the team evener has been disabled and it was obvious that it did alot of good then bad. The teams were more uneven then ever. Anyway, we'll see what the poll does

still .. being a "slave to the system" is far worse

http://images.google.nl/images?hl=nl&lr=&q=tree http://images.google.nl/images?hl=nl&lr=&q=bush (<-- lol) http://images.google.nl/images?hl=nl&lr=&q=stump http://images.google.nl/images?hl=nl&lr=&q=log http://images.google.nl/images?hl=nl&lr=&q=rock ... ?

Indeed NBVegita (hiya! ), I believe some ship (correct me if Im wrong) also tried to check whether a player has bounce or not, but it seemed that it just wasn't possible in Mervbot. If you look in-game - how do you estimate that someone has bounce? It isn't greened, it is ?buy'ed what no other client can see. You can only see by the type of bullets the player shoots. Something a bot can't do.

eek!

lol pointless

not a bug. negative S2C means that packets from server to client (S2C) arrive but packets from client to server (C2S) doesn't arrive at the server: the server will send packets again. Thats why you get everything double. It's not a SS problem, more an ISP problem.

lol... its funny how you make it up that I was referring to this topic all I said was "pointless"

<{POST_SNAPBACK}> <{POST_SNAPBACK}> <{POST_SNAPBACK}>