bot_vs_human: Added some more words to its definition, to warn about its usage.

There would need further changes to handle correctly state changes (from a positive to a negative value, for instance) during a game (reallocate/rebalance teams as well as update allowed teams in the team select dialog). But I think it's not worthwhile to work on it.

diff --git a/defaultXonotic.cfg b/defaultXonotic.cfg
index d7ed1815a8eb970d6d1c3cd1842a983ef5d15e15..1c6942d0b5e393ab9b15902d5657d218a8a9e14e 100644 (file)
--- a/defaultXonotic.cfg
+++ b/defaultXonotic.cfg
@@ -451,7 +451,7 @@ set bot_ai_aimskill_order_filter_5th 0.5 "Movement prediction filter. Used rarel
 set g_waypointeditor 0
 set bot_ignore_bots 0  "When set, bots don't shoot at other bots"
 set bot_join_empty 0   "When set, bots also play if no player has joined the server"
-set bot_vs_human 0     "Bots and humans play in different teams when set. positive values to make an all-bot blue team, set to negative values to make an all-bot red team, the absolute value is the ratio bots vs humans (1 for equal count)"
+set bot_vs_human 0     "Bots and humans play in different teams when set. positive values to make an all-bot blue team, set to negative values to make an all-bot red team, the absolute value is the ratio bots vs humans (1 for equal count). Changes will be correctly applied only from the next game"
 
 alias g_waypointeditor_spawn "impulse 103"
 alias g_waypointeditor_remove "impulse 104"