GameNetworkingResources VS TOSIOS

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).

https://github.com/halftheopposite/TOSIOS: never brought the game to the "fun" part of what a game is supposed to be, but at least it serves as educational.

https://github.com/halftheopposite/graph-dungeon-generator: what was supposed to be circular graph dungeon generator, ended up being a tree dungeon generator.

https://webcursors.click - I should have spent more time thinking about solving a problem that doesn't exist and clearly you can feel that there's something missing.

TOSIOS https://github.com/halftheopposite/TOSIOS (open source browser game)

Shameless promotion of an open-source project I've been working on in the last years and has attracted many beginner developers https://github.com/halftheopposite/TOSIOS.

I've had a bit of experience going through this and I've maintained an open-source project for people to build their own multiplayer game or see how it works (see https://github.com/halftheopposite/TOSIOS).

I do not plan to open-source it for now, but I have created another open-source project named TOSIOS - The Open-Source io shooter which is using Colyseus and client-side prediction and that you can check out at https://github.com/halftheopposite/TOSIOS. I hope to make some big update to that project as well as I didn't do much on it for the past year. I also hope to write a few articles on creating multiplayer games.

This is not a game per se, but more of an open-source toy that I plan to integrate into another of my open-source project https://github.com/halftheopposite/tosios in the incoming weeks.

Hello HN!

I created this hobby-project to learn more about procedural generation and decided to start with the classic but efficient Binary-Space Partitioning method. I also wanted to look at the auto-tile algorithm for the editor and renderer.

I plan to integrate this dungeon generator into my other open-source project https://github.com/halftheopposite/tosios to add more roguelike elements to it and better gameplay elements.

This generators code is also available on NPM at https://npmjs.com/package/@halftheopposite/dungeon.