From 2333a437bd0beb2296b4b8a32fd3ddb921489bd5 Mon Sep 17 00:00:00 2001 From: alexpolo1 Date: Tue, 15 Sep 2026 04:22:14 +0200 Subject: [PATCH] docs(baal_xp): note that the leech enable flag resolves to the params.ini default The paladalla profile sets run_baal_xp=1 in [routes] but has no [baal_xp] section, so the leech enable flag resolves to the params.ini default (1). The 09-08 '5 cycles failed in a row' breaker was the join failing after the fallback candidate was picked - the cycle then never re-armed and the bot fell through to end_game. The rearm loop (98f9b73) handles that; this just documents where the flag actually comes from so the next debug session does not chase a phantom profile override. --- config/params.ini | 3 +++ 1 file changed, 3 insertions(+) diff --git a/config/params.ini b/config/params.ini index f8b39ee..6827fac 100644 --- a/config/params.ini +++ b/config/params.ini @@ -664,6 +664,9 @@ max_engagements=8 [baal_xp] ; Baal XP farm: join public Baal games, hide, collect XP, leave. Repeat. ; Enable by adding run_baal_xp to [routes] order above. +; NOTE: the active profile (paladalla) does not set this, so the default below +; applies. Set enabled=0 in the profile's [baal_xp] section to force the +; leech off for that profile. enabled=1 ; Substring to match against game names (case-insensitive). Empty = join first game. game_name_filter=baal