StarCitizen:Replication layer: Difference between revisions
More actions
imported>TheBookfinder m removed stub |
Sync: upstream update available (local edits by imported>TheBookfinder preserved) |
||
| Line 1: | Line 1: | ||
{{Upstream update available|StarCitizen:Replication layer/Upstream}} | |||
The '''replication layer''' is currently part of the server and is planned to be between the client and the server. | The '''replication layer''' is currently part of the server and is planned to be between the client and the server. | ||
Latest revision as of 11:21, 8 October 2026
Upstream Update Available — The source wiki has a newer version of this page.
View upstream version
Dismiss this banner by removing {{Upstream update available}} from the page after reviewing.
The replication layer is currently part of the server and is planned to be between the client and the server.
Instead of the player connecting directly to the server, the player and the server both connect to the replication layer. The layer allows all the servers to be synchronized.
The replication layer was introduced In alpha 3.18<ref name=":0" />. It offloaded the entire state of the universe: things like characters, ships, weapons, and more away from the game servers, called DGS.<ref name=":0">Inside Star Citizen: Dev Diary - Server Meshing, Star Citizen, YouTube, 4 July 2024</ref> The work of splitting the replication layer to be shared between the client and DGS into a new hybrid service still needed to be done, as was the testing of the new crash recovery system. These would be the focus of two tech preview tests which showed that it worked well.<ref name=":0" />
Crash Recovery
If the server crashes, the client stays up, still connected to the replication layer, and when the server comes back up again or a new one replaces it, it comes back to its state before the crash, still impacted by player actions, as opposed to a default state.
References
<references />