question

ashkan-saeedi-mazdeh avatar image
ashkan-saeedi-mazdeh asked

using the new match maker for a mobile MMO

We are currently using playfab's old AWS based servers and match maker because when we started the new one wasn't still in public preview and also because while the new match maker is much more customizable, it doesn't have some of our critically needed features.
Can we arrange a talk or some other way so we have access to newer features of it and we can shape it.
Specifically more than anything else we would like to know if we can issue match making requests from our servers on behalf of clients to make sure correct values are sent and strong players are not matched with weak ones and also can we keep servers running and let me players join them, what you call back filling tickets.

Our matches sometimes are strict sessions like a fortnite battle royal gme and sometimes are quests which when created can be joined later on by players meeting certain conditions>

Let's say we have a quest started for faction A and players of that faction can join it if they are in 3 levels around the playeror if they are in 5 levels of his range and waited more than 10 seconds in a queue
Then players of faction B also can join it if they meet certain criteria and players already in the match meet certain other criterias as well.

Now our queue values should be sent from our authoritative servers (currently written in Orleans) but we would be more than happy to skip building a custom match maker and zone manager as well if it can be avoided using the features of the new match maker.

Can you help us decide either here or in a short meeting so we know what features are coming to it and does it intend to support scenarios which a match is not just a session and can be a more persistent world.

Many cool scenarios comes to mind. let's say there is a PVE zone which players of faction A are fighting and one of them finds a golden ticket which allows all players in the room to vote for a great challenge and great reward, then the zone can go to a white list ( by setting a value/tag for the server) and then players which do match making and are higher in terms of progression and in a different faction can join these zones if they want to which makes a sort of player boss.

Two requirements
1- back filling tickets
2- server specific dynamic properties which affect match making
and implicitly, the ability to set player attributes and server attributes from an authoritative server instead of being client driven

Can we have this? also can we have any ETA with an indie plan?

10 |1200

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

1 Answer

·
JayZuo avatar image
JayZuo answered

Server backfill ticket is still in Beta. You can find some documentation here: Using server backfill tickets.

And for attributes used in tickets, they can be specified in two ways, either:

1. Within the create ticket request

2. In the player's entity

Since you don't want they can be specified by clients, then the only way would be using player's entity. You may use Entity Global Title Policy to deny the write access of specific objects that used in matchmaking from clients. However, there is also no detailed document about entity policy now.

So I'd think you can achieve what you want with new matchmaking system, but there is no ETA for it now.

1 comment
10 |1200

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

ashkan-saeedi-mazdeh avatar image ashkan-saeedi-mazdeh commented ·

Ah that's interesting to know. Well our actual release would be late summer so it probably will be ready until then unless you think still there is a possibility and we should not count on it.

Other than that, it seems that it supports our use-case, I should still think more and look more but should be good enough

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.