netcode.io VS RakNet

yojimbo/ netcode/ reliable, all developped by Glenn Fidler, author of GafferOnGames

Man-in-the-middling the netcode. From what I can tell, this would work ... but the packets are encrypted. It appears the netcode is largely based on this library, that they sponsor. There appear to be some differences from the "standard" but there are too many similarities to not have a common ancestor. I got pretty far on this, just to at least verify there was encryption. Even if it is not encrypted, it appears to be a custom protocol.

I use netcode.io - if you have read gafferongames posts, this is made by the guy.

You may not be there yet with your developer skills but if you are curious you can have a look at the netcode source code. I'm not sure if they're still using it since the switch to Lumberyard and Amazon Services but it's a really good and strong codebase: https://github.com/networkprotocol/netcode

I found that there is a relatively new protocol called netcode.io that provides UDP-like connection between client-server.

If you want to learn more about networking for game in C++, Glenn Fiedler has great articles from the basics to advanced topics: https://www.gafferongames.com/ He also created a library for client-server networking: https://github.com/networkprotocol/netcode (He has a big name in networking, totally recommend reading his articles if you want to learn more about networking)

Halo was mostly all about single player and early multiplayer/local multiplayer but their online netcode has sucked since Blood Gulch. Lots of games do networking horribly, I have been in gamedev making networking and I hate most of what people do. The ones that have a clean natting, based on enet style reliable UDP channels, RakNet style punch are better (RakNet was good until Facebook bought it). It has come a long way but also fallen back. Valve source netcode (on github) is probably the best and you can check it out here. They started with the best in Quake networking, then to Source.

Here

Raknet No longer worked on but from what I've read, it's complete and working. It has been used in many games between 2000 - 2010

Inconsistencies can be prevented by ensuring the server handles all operations and does so in a given order, then transmits the results to clients. I wrote a little about this for my game Avoyd a long while ago. Clients (including a client running the server) send an edit request via reliable ordered UDP (e.g. using Enet, Raknet, Steam Networking etc.) and the server places these in a single queue then performs the edits and sends the results back also using reliable ordered UDP.

RakNet. It's been forked but still not that active.

RakNet (UDP network library)