[pendragon]

Originally Posted by VooDooDemOn doeas this work with 0.20

I haven't tested it and I abandoned it a long time ago.

zor has another version taht I know works with .20.
it has one bug though (a player model issue) but there is a fix (thanks to firestorm) we have discussed in the DoD Amxx plugins site (www.dodplugins.net).

[pendragon]

Originally Posted by VooDooDemOn doeas this work with 0.20

I haven't tested it and I abandoned it a long time ago.

zor has another version taht I know works with .20.
it has one bug though (a player model issue) but there is a fix (thanks to firestorm) we have discussed in the DoD Amxx plugins site (www.dodplugins.net).

[Jedi]

Yes this works with v0.20 - I'm using it - just make sure you turn spectator lock off - unless you don't want anyone to be able to go spec. This version has an auto-teambalancer that I like - something Zor's version does not include - that's why I use this one instead.

[MAUGHOLD]

a couple questions if i may.

#1-does this lag the server by checking if the teams are unbalanced or does it olny check when a player is trying to switch.

if so.

#2-can it be configured to just simply prevent a player who trys to switch and make the teams uneven. saying something like

"this switch would make the teams uneven" and stop the switch.

thank you all in advance.

[tla-nick]

I got a request to add a command to this, so I hauled it out and updated it.

added:
new command amx_playerswitch <player1> <player2>
if <player1> and <player2> are on different teams then switch them

changed:
balancer now ignores bots, they (should) balance themselves
team locking overhauled to be simpler

fixed:
assign-by-comparison bug in force_client()
- always set g_balance to 1, meaning the only way to disable the balancer was to not compile it in
logic bug in swap_client()
- wrong check order meant that a timed out or connecting player could sometimes cause a balance to fail
logic bug in force_client()
- allies locking was checked, axis wasn't

thanks to Stoned Smurf for testing.

and to give (very) late answers to the post above:

#1, it won't allow a player to join a team if doing so would unbalance them, and it actively checks (and possibly forces) balance only when a player disconnects or an admin issues the command amx_balance.

#2 the hlds cvar mp_teamlimit sets how many players one team is allowed to have over the other (setting it to 0 disables this) this can be used as a passive balancer. However I found it wasn't very good which is why I wrote this plugin.

[Flashhh!]

Originally Posted by tla-nick I got a request to add a command to this, so I hauled it out and updated it. added: new command amx_playerswitch <player1> <player2> if <player1> and <player2> are on different teams then switch them changed: balancer now ignores bots, they (should) balance themselves team locking overhauled to be simpler fixed: assign-by-comparison bug in force_client() - always set g_balance to 1, meaning the only way to disable the balancer was to not compile it in logic bug in swap_client() - wrong check order meant that a timed out or connecting player could sometimes cause a balance to fail logic bug in force_client() - allies locking was checked, axis wasn't thanks to Stoned Smurf for testing. and to give (very) late answers to the post above: #1, it won't allow a player to join a team if doing so would unbalance them, and it actively checks (and possibly forces) balance only when a player disconnects or an admin issues the command amx_balance. #2 the hlds cvar mp_teamlimit sets how many players one team is allowed to have over the other (setting it to 0 disables this) this can be used as a passive balancer. However I found it wasn't very good which is why I wrote this plugin.

Nice! finally I found it!