> Anyways I’d just like to voice myself as a possible target audience
Local development is tricky, and we have plenty of room for improvement here.
Currently we provide a special developer token [1] which will cause API endpoints to return mock responses when used locally. This way, you can use the exact same API with no difference in production & locally, so you don't have to mess with nested prefabs.
However, this doesn't help much with exposing your local machine for testing. We've toyed around with the idea of something similar ngrok built in to our Rivet CLI and integrated in to the API.
To be honest I do wonder if my fixation with local development is even justifiable. Looking around at projects and documentation I do get the sense that local dev is not a priority, and maybe that isn’t a bad thing. Amazing projects exist. Perhaps other game devs are more resourceful than I am and simply build, working around limitations.
I do enjoy learning and this constraint requires I deeply learn. However there is an opportunity cost.
> Anyways I’d just like to voice myself as a possible target audience
Local development is tricky, and we have plenty of room for improvement here.
Currently we provide a special developer token [1] which will cause API endpoints to return mock responses when used locally. This way, you can use the exact same API with no difference in production & locally, so you don't have to mess with nested prefabs.
However, this doesn't help much with exposing your local machine for testing. We've toyed around with the idea of something similar ngrok built in to our Rivet CLI and integrated in to the API.
[1]: https://rivet.gg/docs/general/concepts/dev-tokens#mock-respo...