Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save tariqazmat101/3b82dd2ece6ed7a20ee7ca23c970a949 to your computer and use it in GitHub Desktop.
Save tariqazmat101/3b82dd2ece6ed7a20ee7ca23c970a949 to your computer and use it in GitHub Desktop.
Replay Recorder Archecture feature
If you're reading this then there is a good chance you are interested in building something similar or are simply a laymen who wants to really understand how this feature works(can't blame you, it's pretty cool :D). Just note, this analysis provides a high level overview of all the systems along with a bit of technical sprinkling. IT DOES NOT TELL YOU HOW TO BUILD IT,
Because this analysis will also cater to the laymen, I will need to explain a few things that the developer may already know. skip this section if you're a seasoned ogar dev.so let's star:
1)The client-server model
the server is just a computer somehwre in the world that evryone connects to, as you may probably know,there is server out here in the world that every player connects to. the server sends data messages to the client
2) the client
You can think of the client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment