okay for release numbers..
here's how it goes..
"Podbot 2.6mm Release X.Y"
X will be incremented for each release..
Y is incremented only when there was a problem with the first initial release such as a little tiny bug that needed fixing..
the next release is R3... so the betas are actually R3 betas..
the min_bots and max_bots problem can all be solved..
if only you guys read what was in the podbot.cfg since pb2.5...
Quote:
# Remove the comments on the 2 lines below to support a minimum and maximum
# number of bots running on a dedicated server. Bots will be added to the
# server until the total number of players (bots and humans) reaches the
# max_bots value. Each time a new player joins the server, a bot will be
# kicked from the server unless there are only min_bots number of bots
# currently on the server. After players disconnect from the server, bots
# will be automatically added back to the server until the total number
# of players reaches max_bots again. You should make max_bots be AT LEAST
# one less than the maxplayers value (otherwise no one will be able to join
# your server).
|
and that is exactly how it is implemented in the current beta...
it's pretty close how CF wanted it..
yet KWo complains that it's an auto fillserver...
I will now DEFAULT min_bots and max_bots to ZERO..
that way there will be no limits and no bots added automaticly when those 2 commands are commented out..
once you uncomment it should do exactly like how that quote is..