fix: remove !quiet guard from ML decision logging in BatchRunner

The condition 'mlLoggingEnabled && !quiet && mlDecisionLogger != null'
silently skipped ML training data extraction whenever quiet mode was
active. DecisionExtractor works with the same log lines regardless of
quiet mode, so the guard was unnecessary and prevented JSONL generation.

Now: mlLoggingEnabled && mlDecisionLogger != null — ML logging runs in
all modes as long as --ml-log is passed.
This commit is contained in:
KoalaTrapLord committed 2026-04-05 16:19:56 +00:00
1 parent 14ff543135
commit 8995d743af
1 file changed
+5 -1
@@ -845,7 +845,11 @@ public class BatchRunner {
}
}
if (mlLoggingEnabled && !quiet && mlDecisionLogger != null) {
// ML decision logging: extract state+action snapshots from the
// verbose Forge game log for the training pipeline.
// Note: the !quiet guard was removed — ML logging now works in all
// modes. DecisionExtractor parses the same log lines regardless.
if (mlLoggingEnabled && mlDecisionLogger != null) {
try {
String gid = "game-" + gameIndex + "-" + gameSeed;
String[] cmdNames = new String[numPlayers];