You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked the repository for duplicate issues.
What feature do you want to see added?
Add a single "matchmaking" package which combines all 3 protocols implementions into a more unified API.
Why do you want to have this feature?
Seemingly every game which we support uses at least one method from all 3 match making protocols. This makes implementations a bit messy/verbose, especially since each server will implement basically the same things every time.
Having a single "matchmaking" package which combines what we use from the other 3 into a single package would drastically simplify this. This is also what Nintendo does, there is a single MatchMaking library/API which manages each of the 3 protocols under the hood.
This would also drastically simplify implementations for tools like the server creation command.
Any other details to share? (OPTIONAL)
This may not be the best place to implement this? I'm wondering if a 4th library would be best for this. Only because there's already 3 "match making" related packages, and those are for the actual protocols. We wouldn't want to confuse people.
The text was updated successfully, but these errors were encountered:
Checked Existing
What feature do you want to see added?
Add a single "matchmaking" package which combines all 3 protocols implementions into a more unified API.
Why do you want to have this feature?
Seemingly every game which we support uses at least one method from all 3 match making protocols. This makes implementations a bit messy/verbose, especially since each server will implement basically the same things every time.
Having a single "matchmaking" package which combines what we use from the other 3 into a single package would drastically simplify this. This is also what Nintendo does, there is a single MatchMaking library/API which manages each of the 3 protocols under the hood.
This would also drastically simplify implementations for tools like the server creation command.
Any other details to share? (OPTIONAL)
This may not be the best place to implement this? I'm wondering if a 4th library would be best for this. Only because there's already 3 "match making" related packages, and those are for the actual protocols. We wouldn't want to confuse people.
The text was updated successfully, but these errors were encountered: