Comment 3 for bug 332717

Yeah, it's definitely message order. Axes in maps should not be problematic, but if axes (or map size) settings only arrive on the client after the grid has been created, stuff like that can happen. There are no real safeguards against it, but clients should sync before they create the grid and thus avoid this in 99.9% of all cases.

A real solution would be if the server would delay sending the gGame object responsible for creating the grid until all settings are transmitted. I give this bug a low priority for now and will attempt that on the trunk; the settings system has sufficiently diverged for merge hell issues.