It's relatively simple, but "The SpacetimeDB devs have not yet shipped a game using client-side prediction techniques", is not correct.
I have enough experience in this space to spot something real vs. hype and horseshit and let me tell you point blank -- there is nothing of value here for people making any sort of serious multiplayer games.
Maybe you can even negotiate a consultancy fee with them
You can stay sceptical, but try giving them a chance. You might end up surprising eachother!
Aside: I'm getting into indie game dev recently and love your site!
No thanks!
What's going on is that we have some people here (SpacetimeDB) making some very bold and incorrect claims about a supposed game changing technology in a domain that I happen to be a world expert in.
I stay silent and a bunch of people try this out, build games with it and it blows their company up because it's a toy product (it's happened before with Improbable).
I call it out and now I'm "emotional" and I'm "attacking" them. oohhh I'm such a horrible person. How do I sleep at night. You can't win :)
This company focused all it's effort in reinventing the part of multi-player games that did not need reinventing.
40 engineers for 5 years. I'm guessing at least 20 million dollars spent. 1 million trailer views... Let's say 100k wishlists, 10,000 sales at 30 LTV. 300k in revenue
This company will need to pivot if the game is not successful.
I would say the db could be pivoted for multi-player Figma style apps rather than games, but the coupling of server and db means you can't scale the db layer the same way you could do with literally every other db solution available s your company scales
At least, not if you want me to not call you out on it.
I get the sentiment, I really do, but being misguided isn’t a crime that’s worth being treated like shit for. Especially when you are trying to learn.
> Things I have never thought as a professional multiplayer game developer: "Phew! I've just finished coding all the complex lag masking netcode myself, you know what I really need next? An in-memory SQL-like database to store my world state!"
Transation: This is not the way multiplayer games are usually made. Solving for problems like latency hiding, competitive integrity and making the game fun are orders of magnitude more difficult than "how do I store my object state on the server".
> How can you think deeply and plan for something when you don't know what don't know. You can only really understand these things when you've taken a game using these latency hiding techniques into production, and then after this, you'll probably realize that some of your original ideas were wrong. Where does this leave SpacetimeDB then?
Translation: The SpacetimeDB devs have not yet shipped a game using client-side prediction techniques. Because of this the entire architecture of SpacetimeDB is suspect. Client-side prediction, latency compensation and delta-encoding over UDP are the things that most influence the structure of game state on the server, and the fact that the team doesn't have experience with these things means that they've almost certainly built SpacetimeDB the wrong way.