3 ms·

https://rivet.gg/docs/general https://rivet.gg/docs/general That link appears broken. I don't quite get the concept yet. The details are kinda slim.

• NathanFlurry 2y ago
  > I don't quite get the concept yet. The details are kinda slim. Would be helpful to learn more. From looking at one of the examples, can you elaborate a bit on what doesn't make sense? Or is this more broadly how it works architecturally? > That link appears broken. Looks like we had a broken link in the mobile nav – is that where you found it?
  • pizzafeelsright 2y ago
    Mobile, yes. Perhaps a use case? To say it's like another service requires me to know the alternative and now your completion is known as well. I'm also curious how the service handles multiple requests to the same state.
    • NathanFlurry 2y ago
      Does this example list help? https://github.com/rivet-gg/actor-core?tab=readme-ov-file#examples https://github.com/rivet-gg/actor-core?tab=readme-ov-file#ex... > I'm also curious how the service handles multiple requests to the same state. That's the key part of ActorCore – state is persisted across requests. It's like a Lambda function that can (a) run forever and (b) persist state.