Content deleted Content added
m rewrite |
m ref |
||
| Line 2: | Line 2: | ||
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. |
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. |
||
This offloads the entire state of the universe: things like characters, ships, weapons, and more away from the game servers.<ref>[https://www.youtube.com/watch?v=pCPaSkcK3mM Inside Star Citizen: Dev Diary - Server Meshing], Star Citizen, Youtube, 4 July 2024</ref> |
|||
=== Crash Recovery === |
=== Crash Recovery === |
||
Revision as of 18:12, 6 July 2024
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.
This offloads the entire state of the universe: things like characters, ships, weapons, and more away from the game servers.[1]
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
- ↑ Inside Star Citizen: Dev Diary - Server Meshing, Star Citizen, Youtube, 4 July 2024
This article is a stub.
This article needs some ❤️! You can help the Star Citizen Wiki by expanding it. See Category:Article stubs for other pages that needs expansion.