This will have the effect of removing the bot-game chat history from moderator toolbox.
Benefits: fixes potential infinite loop that would crash the bot & otherwise simplifies the code.
Fix details:
Any warn/error message is sent as a chat message. Any chat message in turn is sent to the lobby. If there is an error sending a message to the lobby, it can yield an error message, which in turn triggers a chat message, which in turn yields another upload to the lobby thereby starting an infinite cycle. If we do not send messages to the lobby, then this is no longer a problem.
Future plans:
Overall, ideally we can invest efforts in "network relay" rather than bot hosts, and remove all of the headless-game code entirely.
Give moderators read-only access to the bot logs, which do contain the chat logs. (To do this, we'd need to set up a syslog "log-aggregation-server", send syslog data to that server, then run NGINX and mount the aggregated log data folder to be served as a webpage. Do a DNS entry, and set up a password & share that password with moderators).
This will have the effect of removing the bot-game chat history from moderator toolbox.
Benefits: fixes potential infinite loop that would crash the bot & otherwise simplifies the code.
Fix details:
Future plans: