question

aaronbuhr avatar image
aaronbuhr asked

Matchmaking: Implement block list via exclude tag filters?

We plan to use Playfab matchmaking. We would like to support "block lists" during matchmaking - preventing players that have been designated as "blocked" from being matched with the blocker. This could mean up to ten tag filters just for the block feature per individual being matched. Is this a good approach or is this going to too-much-stress the Playfab matchmakers?

Matchmaking
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JayZuo avatar image JayZuo ♦ commented ·

May I know which matchmaking system you are using? Is the legacy one with Matchmake API or the new Matchmaking?

0 Likes 0 ·
aaronbuhr avatar image aaronbuhr commented ·

Although we'd like to use Matchmaking 2.0 our understanding is that it isn't going to be ready for full production use in our planned timeframe. So this would be with the legacy matchmaking implementation.

0 Likes 0 ·

1 Answer

·
JayZuo avatar image
JayZuo answered

According to your description, it seems you want to filter between players e.g. player A blocked player B, then in matchmaking, player A won't matched with player B.

However, in legacy matchmaking, tags is used to filter Game Server Instances. Each Game Server Instance can be associated with certain Tags. And you can use TagFilter in Matchmake to find the proper Game Server Instance. So the TagFilter won't work between players. You may update tags for the Game Server Instance that player A matched. But it's still possible that player B also matched into this instance before the updating finished. So I'm afraid we can't not use exclude tag filters to implement block list.

AFAIK, blocking some players from matchmaking together is not supported either in legacy system or the new Matchmaking. Please feel free to post a feature request here so that PlayFab may add this in new Matchmaking system based on the community's feedback.

2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

aaronbuhr avatar image aaronbuhr commented ·

I understand complete blocking coverage cannot be obtained but would say that partial success is better than none. We are using matchmaking to join players into a player-hosted match, and the usage I envision is for the host of the match to have a list (of hashes likely) of players that the host player does not wish to match to. Then prospective matching players to be evaluated by the matchmaker would have an exclude list for matchmaking consisting of their own hashed id. This would cause the exclude tag filter for the player to be blocked to have a hit against the multiple tags listed on the hosted match. So are you saying that this will not even produce partial block coverage, which is potentially acceptable, or is there some technical reason not to do this? Thank you.

0 Likes 0 ·
JayZuo avatar image JayZuo ♦ aaronbuhr commented ·

For your scenario, if you only need the hoster can block some players, then it would be able to work.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.