We have another question that involves the destroy session node or eventually the end session node.
What is the best place to run them?
First thing we try’d was running the destroy session when ever someone would leave a game, but if you did not set it up so that on success you would leave to the main menu they destroy session would never happen and the search for session would never end and creating a games would fail. Main problem with this method was if the client was dropped from a game the session would never be ended for them and the same issue would happen. Even when you connected the leave or quit to on success it would never succeed for the client.
Now we are currently running the destroy session node from our main menu controller into our game instance. the reason being so that we can store a variable on the client side that says weather or not your still in a session and not let the client try and create a game or search for games until there out of there old session. The only issue now is that sometime the end/destroy session doesn’t happen and you have to restart the game to search and create.
we also have for quit on the sever to run destroy session and then quit and sometimes it takes forever and it seems like it wont ever quit. Not sure if there is a better way to do this.
Were just looking for how others set up there destroy sessions and best practices for it.