Updated Playerbot Configuration (markdown)

bash 2024-11-14 20:49:51 +01:00
parent acf1266089
commit 4b6d666df8

@ -20,6 +20,8 @@ The following logic is applied to determine whether a bot is active or not, appl
``` ```
These rules will always be applied regardless what value you have configured **'AiPlayerbot.BotActiveAlone'**. These rules will always be applied regardless what value you have configured **'AiPlayerbot.BotActiveAlone'**.
***
All remaining situations e.g. bots in zones or maps without real players, empty server etc will be configured All remaining situations e.g. bots in zones or maps without real players, empty server etc will be configured
based on the **'AiPlayerbot.BotActiveAlone'** value. That value basically means that the bot has about based on the **'AiPlayerbot.BotActiveAlone'** value. That value basically means that the bot has about
% chance to get active for only a few seconds. Unless in those few seconds one of the above rules % chance to get active for only a few seconds. Unless in those few seconds one of the above rules
@ -31,6 +33,7 @@ the bots is the level scope of the configured values of:
* **'AiPlayerbot.botActiveAloneSmartScaleWhenMinLevel'** * **'AiPlayerbot.botActiveAloneSmartScaleWhenMinLevel'**
* **'AiPlayerbot.botActiveAloneSmartScaleWhenMinLevel'** * **'AiPlayerbot.botActiveAloneSmartScaleWhenMinLevel'**
***
#### 1. best performance with high bot count. #### 1. best performance with high bot count.
My personal preference is that i keep my bots idle when i am not in the zone or map, which is applied with the following config My personal preference is that i keep my bots idle when i am not in the zone or map, which is applied with the following config
@ -70,17 +73,17 @@ AiPlayerbot.botActiveAloneSmartScaleWhenMinLevel = 75
AiPlayerbot.botActiveAloneSmartScaleWhenMaxLevel = 80 AiPlayerbot.botActiveAloneSmartScaleWhenMaxLevel = 80
``` ```
#### How to determine whether your config/hardware are good or not ***
#### Check profile and performance
Use the command '.server info' to see your latencies. The general latenciesshould be under 70-80 and the percentiles maxed out around Use the command '.server info' to see your latencies. The general latenciesshould be under 70-80 and the percentiles maxed out around
100, 120, 150. If higher change profile or lower your bot count. 100, 120, 150. And verify how quick a bot executes your command. It should be pretty much instant. If not to should choose a different profile
and/or lower your bot amount.
Another way; verify how quick a bot executes your command. It should be pretty much instant if not to should choose a different profile If dont use the performance checks it might result into strange and incorrect bot behaviours and/or huge amount of memory footprint growth in
or lower your bot amount. a relative short time (OOM)
If dont use the performance checks it might result into strange and incorrect behaviours and/or huge amount of memory footprint growth in ##### Reference
a short time of your server.
##### example
I use profile 1 with 5000 bots on amd 5700x (6 cores), linux, 20GB with the following result: I use profile 1 with 5000 bots on amd 5700x (6 cores), linux, 20GB with the following result:
![image](https://github.com/user-attachments/assets/6760feaf-3dc7-4d7a-9534-d4183ff43284) ![image](https://github.com/user-attachments/assets/6760feaf-3dc7-4d7a-9534-d4183ff43284)