Another update -
V3 Build 15c:
+Fixed another problem with hostages (few times pickuped by a bot the same hostage).
+Fixed (my) mistake in the waypoint editor - now when You point some waypoint - the manual path connection will be done with that pointing WP. If You have sme trouble with pointing a WP - just try to point the middle of its height.
+Added 2 new cvars requested by Austin:
pb_bot_quota_match and
pb_bot_join_team. Usage:
Quote:
|
Originally Posted by PB MM V3 DOCS
That function (auto add/kick bot) also doesn't work in the case if pb_bot_quota_match is defined as grater than 0 (in that case number of bots follows the number of humans multiplied by pb_bot_quota_match (of course in the range between pb_minbots/pb_maxbots). More info read below.
pb_bot_quota_match (value) - configure the number of bots that will match humans on the server (number_of_bots = number_of_humans * pb_bot_quota_match). In this case number of bots will be limited by pb_minbots and pb_maxbots settings. For that function pb_maxbots keeps the max limit of bots on the server (not max number of bots + humans like it's for auto add/kick bot function). The work of the function matching humans is stopped by usage some of these functions - pb fillserver or pb removebots (in both cases pb_bot_quota_match will be set to 0). If pb_bot_quota_match is grater than 0 You cannot also use the function pb add or pb remove (because of the reason the amount of bots must match humans...). Default is 0 (bots don't match humans).
pb_bot_join_team (string) - forces joining the bots to specyfied team (T or CT) to overwrite the setting of the command pb add or pb fillserver. Useful if You want to keep always bots in one team against humans in the other. Possible value of argument - "T", "CT", ANY". Default is "ANY" (bots aren't forced to join any specyfic team.
|
@Austin - please test Your new functions, @Ancient - please test the WP editor - let me know if now it works better....