Restarting specific rooms from PC?
For some reason, anyone who connects to Room 01 right now has their Quest crash. Unfortunately, that's the first room all players go through.
I can connect just fine to Room 02, is it possible for me to restart Room 01 somehow?
2 Replies
Hi @Alix Ollivier. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Normcore room servers are ephemeral and are automatically shut down when all players leave, then restarted on-demand with a fresh process the next time someone connects. [Room server configs]
In practice, to “restart” Room 01 you need to: 1. Ensure everyone disconnects from that room.
Once the last client leaves, the room server will shut down after about 30 seconds of idleness. [Room server configs]
2. Wait at least ~30 seconds, then connect again to Room 01.
A new room server instance will be provisioned when the first client connects. [Room server configs]
If you’re using persistent models, note that the datastore is written to disk when the room server shuts down and then reloaded on the next connect. [Datastore persistence] This means a logic or data issue in the datastore could persist across restarts; in that case, the crash might reoccur even after a restart, and the docs don’t describe a way to manually clear or delete a single room’s persisted datastore from the client side. The knowledge sources do not mention any admin API or dashboard control to forcefully kill or reset a specific room server beyond the automatic shutdown behavior. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
In practice, to “restart” Room 01 you need to: 1. Ensure everyone disconnects from that room.
Once the last client leaves, the room server will shut down after about 30 seconds of idleness. [Room server configs]
2. Wait at least ~30 seconds, then connect again to Room 01.
A new room server instance will be provisioned when the first client connects. [Room server configs]
If you’re using persistent models, note that the datastore is written to disk when the room server shuts down and then reloaded on the next connect. [Datastore persistence] This means a logic or data issue in the datastore could persist across restarts; in that case, the crash might reoccur even after a restart, and the docs don’t describe a way to manually clear or delete a single room’s persisted datastore from the client side. The knowledge sources do not mention any admin API or dashboard control to forcefully kill or reset a specific room server beyond the automatic shutdown behavior. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
<@185325614775926784> Kapa.ai is still learning and improving, please let me know how I did by reacting below.