builder VS gridia

We have a partnership with Hathora (https://hathora.dev/) so that our infrastructure can scale globally with high performance so we can provide the best user experience possible despite the realities of playing games over the internet. We also have some big plans around using rollback that we've covered elsewhere that we're cautiously optimistic about.

For multiplayer/server-less games, try Hathora

I cofounded Hathora (https://hathora.dev/) last year and we've been working on making it easier for smaller teams and individual developers to build scalable multiplayer games. We think the serverless model is the simplest approach, allowing you to dynamically provision a new instance of your game server when users or your matchmaker requests a new session.

We made this .io style demo to showcase this approach, and we're releasing the source code and documentation alongside with it.

Hey I'm the creator of https://hathora.dev/ which aims to provide a super simple deployment and scaling experience for session-based games. It's based on containers and can deploy any kind of game server. Check it out and see if it meets your needs!

At Hathora, our mission is to make it easier for developers to build, launch, and scale multiplayer games. One of the core technologies we have built is the Hathora Coordinator, which is our fully managed multi-tenant implementation of a Stateful Router.

Hi there! I started a company this year focused on multiplayer server infrastructure. We also built a multiplayer game framework for Typescript that has gotten 400+ stars on Github in the past few months: https://github.com/hathora/hathora

Would love to connect and exchange notes about multiplayer development -- if you're interested, my email is on my profile.

I've been working on my own realtime networking engine[0] and I think there are a few important points related to network syncing that are not mentioned in this article:

1) Bandwidth. The users internet can only handle so much network throughput, so for fast paced games (where you're sending data to each client at a rate of 20+ frames per second) it becomes important to optimize your per-frame packet size. This means using techniques like binary encoding and delta compression (only send diffs).

2) Server infrastructure. For client-server games, latency is going to be a function of server placement. If you only have a single server that is deployed in us-east and a bunch of users want to play with each other in Australia, their experience is going to suffer massively. Ideally you want a global network of servers and try to route users to their closest server.

3) TCP vs UDP. Packet loss is a very real problem, and you don't want clients to be stuck waiting for old packets to be resent to them when they already have the latest data. UDP makes a major difference in gameplay when dealing with lossy networks.

[0] https://github.com/hathora/hathora

I built a bunch of multiplayer games in the past and am now working on a framework to try and make it easier for others to do so: https://github.com/hathora/hathora

I've been working on this sort of game for awhile now. Never too seriously, though that will change in 2023. Hardly worth sharing at this point, but I will anyway.

https://hoten.cc/gridia/play/

I need to seriously think about what I want out of this game (more of a mmo game engine), but "UO-like" is definitely top of mind.

When making the netcode for my web game, I highly valued TypeScript support so to get it by default, I defined the message types in TypeScript so they could be used directly[1]. I see that this framework defines its messages in .yml and converts it to types (stored in a folder kept out of source control).

I'm not sure which way is best, but it is very nice to have the feature support of `.d.ts` files when creating complex message types, as opposed to needing to learn a new thing. Clearly if this is going to be a cross-platform (not just web) framework then using TypeScript as the source-of-truth makes far less sense.

Anyway, very impressed with the binary format/delta encoding feature! That's been something that I know I _should_ do but am putting off until I see signs of sending raw JSON being problematic.

[1] https://github.com/connorjclark/gridia/blob/master/src/proto...

- All my Preact code is in this folder: https://github.com/connorjclark/gridia-2019-wip/blob/master/src/client/ui/ - Most complex one: https://github.com/connorjclark/gridia-2019-wip/blob/master/src/client/ui/admin-window.tsx - CSS: https://github.com/connorjclark/gridia-2019-wip/blob/master/src/client/styles/main.css