Building a Game Network Protocol: Reading and Writing Packets

Instead of sending 20-30 position/rotation delta packets per second, you could only send something when there is something to send = some key is pressed (move forward, strafe left, fire gun).

Imagine Counter-Strike without sending the rotation of the player until he actually fires his weapon or changes his strafe/run/walk direction.

It works surprisingly well, and with prediction you can't even tell there's a difference most of the time.

Check out rocket league for a working example.

But with fiber spreading like wildfire because copper is oxidizing globally, our challenges are not text based protocols:

Latency is not bandwidth. Binary does not travel faster than text.

The only problem we have is peak Moore's law and peak oil hitting simultaneously, so optimizing and distributing server systems, preferably decentralizing them into client P2P, is our only challenge.

So my bet is to build a strong async. HTTP backbone now to cater for all futures = organizing these P2P nodes.

That doesn't mean I'm against binary P2P UDP protocols once IPv6 gets a critical mass. But that might be never!

Text is better for protocols because humans can read it.

Instead of implementing TCP on top of UDP, let the internet hardware people implement XYZ under your TCP! Do you think that's ethernet running under the atlatic ocean?