i recently check in several code changes which all belongs to =
colonization. If a planet can be colonized is now been decided on the =
serverside. That's why=20
FleetColonizeOrder has changed to be done within two steps. First when =
the order is issues, everything works the same way as before, except =
that the planet isn't colonized immediate. On the server side =
ExecuteServerApply or ExecuteServerRevoke is been called. =
ExecuteServerApply is used to complete the colonize order (planet =
changes ownership) and ExecuteServerRevoke is used to cancel the =
colonize order. ExecuteServerRevoke will also bring the colony ship back =
to life (in it's own fleet).
Because of recent cvs changes i had to merge some code by hand. I hope i =
didn't miss anything by doing so.
I also did some debugging. Even if it isn't possible that to empires =
have combat forces at the same system, i tested this case too.=20
Get latest updates about Open Source Projects, Conferences and News.