Clive Johnson · Lead Network Programmer, Foundry 42

So beyond 3.4, so 3.4, we've got on the roadmap server migration. So for two systems, they're always going to work, or the plan is for them to work, like separate instances. So the servers for one system and the servers for another system will be completely disjoint and won't communicate at all. We're thinking, maybe, it's not decided yet, that we could use the server migration technology to help provide a seamless transition via the jump points from system to system. So potentially what we could do is someone wants to jump from one system to another. Their ship gets put into a server in its own little bubble. And that server then breaks off from the mesh in one system and then is moved over to a mesh in the other system and is connected in. One of the difficulties that we'll have to try and solve if we do that is, the reason we won't mix systems together, won't connect servers from different systems together, is that each system has its own coordinate system, with the star being at the center, 0, 0, 0. So we have to move from wherever you jumped from, say, the Stanton system, to whichever destination system you're going to. Move the ship, move that server ball across space without colliding with anything else that's in either of the systems. So it's a little tricky, but we're thinking about it. We have to build the server migration tech, server meshing tech, first, and then we'll see if we can utilize it that way.