Raem

You enjoy quoting yourself?

Really? IE sucks anyway... <{POST_SNAPBACK}> Words of wisdom from the fish

I heard from some ERs that they get 'disciplined' if they host event when there few players in pub...

Bounty reward sounds pretty good, but you'll still need a backup in case nobody wants to switch (whole freq balling)

I'm aware of that, but if you change it, then it will be changing the last person who died when the warning was issued, except the switch will be delayed 30 seconds

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. <{POST_SNAPBACK}> I wasn't sure exactly when the bot started recording deaths, which is why the 2nd part of my post !@#$%^&*umes that the bot be changed so that it can pick the player when the bot announces the uneven teams, and not after the 30 seconds are up. If it were left as it is, it obviously wouldn't work.

So it only starts recording people's deaths after the 30 seconds have been announced? What happens if nobody died during those 30 seconds? Otherwise... Does it really matter that the bot only switches people because they died after the bot's 'warning'? I honestly don't believe the players will care, because, either: 1- The person switched will just spec and wait for someone else (a 'type 2' person) to get switched. This happens with this bot anyway, and cannot be fixed no matter what you do. 2- The player switched will stay on the other team so that the teams are even. This kind of player does not need to be 'fixed'. 3- The player with the ball is switched. 4- The player switched has bounty/bounce. This problem can be solved by fixing the team evener. 5- Samapico. Switches after teams are evened. Now, by just having the bot PM that extra message, you can provide a 'fix' for cases 3 and 4. Since any other solution would require too much effort to be implemented, why not just add this? Type 1 will just spec earlier, type 2 will change him/herself over, or will wait for the 30 second period to expire. Type 3 might just continue with the ball, p!@#$%^&* it to someone else, or take it the other way (if the team is truly balling, then there will be at least 1 other person around the ball to recover it). Type 4 will get to a safety zone and change teams so they don't lose what they have. It it not an amazing solution, but its simple to implement (that is what you're after, isn't it?) and relatively effective. Edit: Added type 5 for Sama's sake

Yes, I'm sure people with high bounties won't want to switch themselves manually because they enjoy it when the bot "randomly" selects them. Ok, so maybe the bot won't be able to do that now, without someone actually putting work into it (because where's the fun in doing something right?), you could at least improve a bit on what you currently have. The bot is obviously capable of knowing who died last, and therefore who it will select to switch. The bot can also send messages. Why not have the bot (in addition to messaging the team) send the person who died last a private message, to warn them that they will be switched after the 30 seconds are up, and that if that person would like to preserve their bounty/bounce/whatever, then they better go to safety and switch themselves.

I hate people.

How exactly is that stretching the limit?(and what is this limit you speak of?) Please enlighten me

Good idea, but /*setfreq (which the bot uses) does not work the same way when you do = in a safe spot. Instead of preserving your bounty and specials, *setfreq in safe will reset your ship. -Rifle <{POST_SNAPBACK}> Bah, I thought there would something stupid like that...You could still have the bot warp them to safe and tell the player to =number, and if they don't do it within certain time limit, have the bot setfreq them (and maybe laugh at the player if he/she had bounce/high bounty and refused to manually switch )

I suppose you could, instead of instantly warping a player when 30 seconds are up, the bot could warp them to safety 1st, then switch them, so that they keep bounty/bounce...

A backwards ladd

If the last person who died, leaves then I believe the bot goes insane and chooses a random person? or, the person who died before the person who died last, but if that person were to leave, then the person who....you get the idea

Yes, take mav away from 17th...nobody will miss him anyway. "He's in a better place now"

I hate you.

Yea, Delic is a real !@#$%^&* sometimes...

I guess kent's girlfriend would be kinda similar, if anyone could believe it was true

You can't make 1 which would even player who has lowest bounty and doesnt have bounce/anti/super?

QUOTE(SD>Big @ Nov 24 2004, 09:22 PM)Mr.Ious <{POST_SNAPBACK}> Yes?

dont worry, you're not missing much (anything?)

Yea...you guys are hilarious

Perhaps he did and was trying to be funny? Who knows...X works in mysterious ways

I thought the main reason people complain about the bot is because it evens them when they have high bounty/bounce...

purrrrr