Description
Hey I'm a bit confused about how to work with STDB + physics simulation and am looking for advice/sanity check since this must be a very common concern but I'm not seeing a definitive treatment of it. I don't have much experience here.
I think a "blessed", and simple, game reference (of both client + server) would be very helpful.
Question
It seems there are two ways to go about it:
- for trivial simulations reducers run the simulation: STDB -> Game engine client
- otherwise, use game server replication as normal but persist from the server to STDB ..?
Is that right?
Problem
My main confusion is that I already have a physics simulator - the game engine I'm using e.g. Bevy or Godot. The examples seem to imply that every reducer reimplements a slice of physics..? It feels quite bad and brittle to me unless it's a turn based game or something trivial as opposed to just using the game engine itself as the authority.
The nice thing about having the headless game engine be the server is all your code is isomorphic for free.
Activity
MichaelrMentele commentedon Nov 19, 2026
Going off of BitCraft's server code it looks like you just sniff test the clients work then and then replicate back down to peers..? Is that the right mental model? Am I conflating physics simulation with validation perhaps?
I'm having trouble seeing how things scale out either way because I haven't done both for a head to head! Any comments to orient would be helpful :)