Saishy
Example project does not change back to menu on remote host quit
Machine A: Windows 7 x64 Japanese on an Atom CPU Machine B: Windows 10 x64 English on a Ryzen 3 CPU
Problem: Machine A runs the Example Project included with TinyBirdNet as host mode. Machine B connects to Machine A and everything is synchronized correctly, etc. However, when the host instance of the example project on Machine A is quit, Machine B remains "connected" and does not get kicked back to the main menu. This leaves Machine B in a limbo state.
Severity: Low if it's just the example project at fault. High if the actual library (TinyBirdNet) is at fault.
Expected behaviour: If Machine A goes down and it was the host, then Machine B should be taken back to the main menu.
I guess the fix would be very trivial and I could probably fix it in a few lines of code. It just needs to load the main menu scene if the disconnection event is fired.
