- Newest
- Most votes
- Most comments
Can you explain why you need to allow duplicate PlayerIds in your matchmaking process?
Hey IndieGameDeveloperFromParallelWorld,
Matchmaking only restricts duplicate player ids in flight at the same time, so you couldn't matchmake the same id for multiple matches in one configuration at once. Matchmaking does allow re-use of player ids between matches or when a player leaves a match early.
If you want the same player matchmaking for multiple matches at once, you could have multiple player ids associated with each of your players (ex: <player-1-id>-0
vs <player-1-id>-1
); however, this isn't recommended because it makes your overall matchmaking experience more complicated. For example, it may seem to reduce match time for one player, but all the other potential matches for that player will be disrupted or canceled and end up taking longer.
Hope that helps, but if not, could you clarify the use case you are having trouble with?
Regards,
Relevant content
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago