I submitted this comment to the wrong commit, so I'm now adding it to the correct one:

Start atlas, place a unit for player one, change his civ, then start the game. There's errors starting with:

ERROR: Error calling component script function GetColor

When you change the civ and attempt to start the game, for some reason (which I didn't explore) it changes ownership to gaia before the changing ownership back to player 1. In that second step it calls GetColor but the player color isn't defined yet (again for some reason that I didn't explore). This all happens before session starts, I think.

I guess when you change a player's civ the color of his unit is invalidated? Why would that be? Or at least it's invalidated before the session starts.

A quick "fix" is to use this in Player.js:

Player.prototype.GetColor = function()
{
	return this.color || { "r": 1.0, "g": 0.0, "b": 1.0, "a": 1.0 };
};

The units will be pink on the minimap, but it won't give errors.
If you reset and place new units, then play again, the new units will have correct color on the minimap but the old ones will still be pink.

(I had problems with the minimap in D754, too.)

(I believe this patch is the problem, I reverse-diffed just this one and everything was fine.)

elexis replied:

(Atlas support for changing colors and civs was never or never well supported before alpha 23 (and still is not completely supported as IIRC there are other bugs when doing things with these properties and running the simulation, or for instance reducing the number of players).)