@Cernel

Yea I'm not certain either but like you, I thought we were supposed to have 15.

The reason I mention it again, besides potentially paying for a service we aren't receiving, there's usually only 1 available bot or sometimes none.

I'm glad the lobby still popular but I was hoping to play on it again since new maps are now supported.

Anyway, it seemed noteworthy to mention again

@beelee My understanding is that TripleA has 5 servers on which the bots are located. The servers are all working but currently have 2 bots each instead of the 3 each @lafayette had them having. I've no idea if that is because 3 bots per server are just too much (so it has to be 2 as it currently practically is) or there is a problem or some problems with the bots which @lafayette (or an other developer) may fix eventually (maybe with help from @eyeswideshut).

Not sure if we should make a problem report in GitHub about this or if we should notify anyone anywhere when we see that some bots are broken.

I'm consistently seeing only 10 triplea bots in the lobby. If triplea is paying for 15, then this is something that should be addressed sooner than later imo

@Cernel OK! So I think I solved the bot crashing problem on my end. It was the script function, and the fix was actually very simple.

The problem was that I had this command in the Docker startup script -- and it's probably in all the bots:

--env EXIT_ON_GAME_END=true \

That tells the bot to exit when the game ends. Since the container was configured with --restart always, I was expecting Docker to bring it back, but this was creating problems with the bot disappearing from the lobby.

I removed that command from the startup scripts.

For example, the relevant part went from:

sudo docker run
--network host
--pull always
--restart always
--env BOT_PORT_NUMBER=3301
--env BOT_NAME=Bot_Revised_Ladder
--env BOT_COMMENT=bit.ly/RevLad2
--env LOBBY_URI=https://prod.triplea-game.org
--env EXIT_ON_GAME_END=true
--env BOT_MAX_MEMORY=256m \

to:

sudo docker run
--network host
--pull always
--restart always
--env BOT_PORT_NUMBER=3301
--env BOT_NAME=Bot_Revised_Ladder
--env BOT_COMMENT=bit.ly/RevLad2
--env LOBBY_URI=https://prod.triplea-game.org
--env BOT_MAX_MEMORY=256m \

And I did the same for the second bot on port 3302.

The two bots are now running normally, so I'm going to see whether they remain in the lobby after their next games. Hopefully that's all it was! check to see if the other bots have this function..