ENet-CSharp VS GameNetworkingResources

Making games isn't an easy thing to do, this is especially true for multiplayer games. Ever since I was 12 years old I wanted to make the ultimate multiplayer game. I first started getting into networking through GameMaker studio engine. I would watch tutorials online, try to understand them and end up just copying code for code. Later on I discovered Unity's Low-Level Multiplayer API (LLMAPI) and it was horrendous to get working. Not to mention the documentation for it was even more horrendous. Then much later I discovered [ENet-CSharp](https://github.com/SoftwareGuy/ENet-CSharp) and fell in love with its [simple approach](https://github.com/SoftwareGuy/ENet-CSharp/blob/master/QUICKSTART-EXAMPLES.md). I later found out that I could just add nuget packages to the .csproj file of Godot Modules project and bam I'm using Godot C# + ENet-CSharp. This is great because I'm super comfortable with the C# language.

The list maintained here favors content for actual game developers: https://github.com/ThusSpokeNomad/GameNetworkingResources

Here is a list of resources: A Curated List of Game Network Programming Resources

Check these articles here to learn how game netcode works. The answer to your question (and a lot more) will come naturally after a bit of reading. https://github.com/ThusWroteNomad/GameNetworkingResources

Honestly this is all largely a completely solved problem space. The article is just way out in left field seemingly fully oblivious to how game netcode currently works, which certainly isn't with AI prediction.

Look at actual game engine docs like this one from Valve https://developer.valvesoftware.com/wiki/Latency_Compensatin... or this one from Halo https://www.halowaypoint.com/news/closer-look-halo-infinite-...

But tldr is the only thing a client ever predicts is their own inputs, which of course can't really ever end up wrong later on. There's no other prediction happening (eg, the position of other players is not predicted)

And then for anti-cheat/optimization purposes the server also only sends positions for enemies that could be visible soon, which is done by taping into the same map chunking logic that would be used for asset streaming.

There's a ton of other great resources on this topic here https://github.com/ThusWroteNomad/GameNetworkingResources

But you'll find they all largely do the same basic thing. There's nuance in some of the rules and what state is replicated and what isn't (such as server side or client side ragdolls), but the general architecture tends to be the same. And without a fundamental shift in connectivity, seems pretty unlikely to change.

https://github.com/MFatihMAR/Game-Networking-Resources (This is a list maintained by someone else, and it has some amazing things in it, and far more technical leaning than what I maintain).