The response to a master server open game request is now handled by clientProcessMessages() - this is because the game socket is being utilized to send the open game request so that the master server will be able to detect the proper game port over NATs.
I've moved the clientProcessMessages() function call out of netMain() and created a seperate thread that runs when the client is initialized. I've done this for two reasons: 1. clientProcessMessages() handles all the join game stuff and I think joining games and initial handshaking should be done before the core is started (the whole press F9 at the black emu screen isn't very elegant). 2. clientProcessMessages() doesn't need to be called from within the core via netMain(), all it does is handle packet receiving.. the queue and the frame sending are the only things that need to be timed via the core.
I realize these changes may not be in accordance with the wishes of others, they can be easily reversed if there is any disagreement. I've tested these changes on netplay and it works fine. My ultimate goal with this change is to begin cleaning up the netplay user interface (graphical and commandline) and make it all a little more elegant.
Let me know if there are any problems :)
Bob
