mirror of
https://github.com/clusterio/clusterio.git
synced 2026-11-11 23:04:52 +09:00
bbassieandClaude Opus 4.8
42dc83df80
The console's chat filter kept only Factorio output parsed as an action, which dropped the server's replies to those actions. Running a console command with a typo in it echoed the command and then appeared to print nothing, because "Cannot execute command. Error: ..." is a plain message rather than an [ACTION] line. Factorio's engine level errors were dropped the same way, so a failed multiplayer connection left no trace either. Filter by where a line came from instead. Factorio interleaves two streams on stdout: the date stamped console log, which carries what was done to the server and the replies to it, and the seconds stamped engine log, which is verbose diagnostic output. Keep the console log whole and take only warnings and errors from the engine log. Apply the same rule to Clusterio's own entries, which were previously kept in full and drowned the Factorio output they were mixed with. Keep those at warn or worse and drop the routine bookkeeping. Replayed over a development cluster's history this drops 415 informational lines and surfaces engine errors that were never visible in either mode. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>