Pseudocode of possible solution of lobby connections #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current problem with the lobby is that ConnectToPeer on lobby side seems to block connections completely, even the NAT processing ones.
If we instead establish connections first before we start ordering everyone to connect to eachother we will fix the problem with ppl using proxy connections when they still are able to connect.
The code in this PR isn't complete, I don't have a python work-environment so can't test the actual changes either.
Would be great if someone (@Sheeo ;)) could take a look at this, should be a quick change. What's needed is to be able to get the result from each EstablishConnection() to the later called ConnectToPeer. Either by putting that data on each peer object? Or maybe change the arguments of the function.