From 3d021eda73e39bed2e36b4f477fe77474dc0ab61 Mon Sep 17 00:00:00 2001 From: Kaszanas <34846245+Kaszanas@users.noreply.github.com> Date: Thu, 13 Jul 2023 12:39:15 +0200 Subject: [PATCH] Fixed a typo in Overlapping MatchProfiles "This overlap is desired in some real matchmaking scenarios, . Inorder to [...]" -> ". In order" --- site/content/en/docs/Guides/Evaluator/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/en/docs/Guides/Evaluator/_index.md b/site/content/en/docs/Guides/Evaluator/_index.md index e0dfe9df..80555e18 100644 --- a/site/content/en/docs/Guides/Evaluator/_index.md +++ b/site/content/en/docs/Guides/Evaluator/_index.md @@ -36,7 +36,7 @@ The Director could request for the following Profiles: In this case, the MatchFunction executing Profile1 and Profile2 will have some common players they consider for generating Matches (Similarly with Profile2 and Profile3). Thus, the generated Matches may have overlapping Tickets. -This overlap is desired in some real matchmaking scenarios, . Inorder to generate high quality Matches, you may want your Ticket to be considered concurrently for multiple possible MatchProfiles and then be able to compare the quality of these overlapping Matches, picking the highest quality Match and discarding the rest. For instance in the above example, a Ticket with mmr 3 could be a part of a Matches generated by Profile1 and Profile2. Based on the game design and the mmr of other Tickets in these overlapping Matches, one of these two Matches may actually be a better fit for this Ticket - and thus, searching for Matches with overlapping mmr ranges resulted in considering 2 options for this Ticket and picking the better fit. +This overlap is desired in some real matchmaking scenarios. In order to generate high quality Matches, you may want your Ticket to be considered concurrently for multiple possible MatchProfiles and then be able to compare the quality of these overlapping Matches, picking the highest quality Match and discarding the rest. For instance in the above example, a Ticket with mmr 3 could be a part of a Matches generated by Profile1 and Profile2. Based on the game design and the mmr of other Tickets in these overlapping Matches, one of these two Matches may actually be a better fit for this Ticket - and thus, searching for Matches with overlapping mmr ranges resulted in considering 2 options for this Ticket and picking the better fit. The ability to provide this model of executing concurrent MatchFunctions on overlapping Ticket Pool is a core value proposition of Open Match.