Oof, that’s no bueno! Thanks for letting us know. Could you provide a little more info as to how you are running the Game engine, and how many and which bots you are connecting to it?
Had not seen this for a while, so was beginning to wonder if it was finger trouble on my side, but with the latest version of my bot I can reproduce it pretty reliably at around tick 438.
I think it might have something to do with the fact that prunes often happen at that point, if I spin up 4 instances of my bot.
I’m running the engine and my bots natively (i.e. not with docker), i simply go dotnet run projectName.csproj. I’ve decreased the tick time to 125ms, this might only be happening because of that. But I guess we want to fix any issues like these even if generous tick times hide them.
I suspect most bots will show this (since my current one has changed quite a bit), but I can send you my current one. Is there an email address I can send it to?