There is a bug in the platform. I noticed that sometimes the beginning of a move action is erroneously modified by the platform by adding some extra digits in front of the output.
@f2guibert it’s possible. That was my first assumption as well, so I started chsing the problem down. But once I traced all move actions to the Error console I couldn’t find the problem so as a final test I decided to buffer the entire move command (the full string) and output it to standard error before outputting the same string to standard output and the two strings were different as I explained in the original question.
So far I’ve only seen this at the start of the move line but I’m afraid it might be happening at other places as well.
What makes it difficult to track is that it doesn’t happen all the time. And the only reason I even noticed in the fist place was I saw some of my pods were just stopping at random places and not advancing even though I was certain I had logic that would dictate they should be moving.
And I can’t say if anybody else is affected by this because I only have access to my own console output.
@julien_poulton thank you for looking into this. At this point I’ve found a method to work around this issue by including an extra no-op move command at the beginning of each of my move requests.
When the contest is over I will e-mail my code, and a specific replay where it happens (as I said, these are not easy to find since the problem is intermittent)