{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreievzimvvbn4lhcjxvnvhjay3e6y5p3lsm2uruqh34wi73mz52jlmi",
    "uri": "at://did:plc:dxjzgxe7cvirxkwfjr2tjspt/app.bsky.feed.post/3mnq4znupcfk2"
  },
  "path": "/t/zay-es-and-hidden-states/49615#post_3",
  "publishedAt": "2026-06-07T19:25:53.000Z",
  "site": "https://hub.jmonkeyengine.org",
  "textContent": "I guess that describes it well. I feel that it’s probably going to be painful to do, but I’m at a point now where it makes sense to implement it, if at all.\n\nAn example:\n\nI would have something like a VisibilitySystem. It would do some processing and end up with a list of visible entities/units, maybe they’re added to a VisibleUnits component.\n\nBased on this component, I would either send Position, Rotation, and a bunch of other spatial components. But maybe some other component, indicating the entity is still alive would be sent, for gui and stats.\n\nMaybe the entity could be skipped all together? Would that be simpler? And “public” data could be sent as some other entity to all clients.\n\nThe purpose would be anti-hacking/cheating. (Let’s not get into the discussion whether anyone would bother doing that).\n\nDoes it make sense? The last time I attempted something like this was for Hostile Sector, and it was turn based and rest-like. So much simpler",
  "title": "Zay-ES and hidden states"
}