Entity Global Title Policy for weaker bans

Question

question

radekpibil asked Apr 1, '20

Entity Global Title Policy for weaker bans

Hello,

Im wondering if there is a recommended way to create something like a limited ban. Which is not supported by the current ban framework. I am trying to only prevent the "banned" player from entering the matchmaking. Is there any detailed documentation of Principals and Conditions for entity policies? This seems like the most promising way of doing it. Im thinking about using either tags or segments or less likely entities to drive the check. Do you have any suggestions here? The documentation is practically non-existing for the current state of entity policies definition and the old block with the Unicorn is obviously outdated given the other questions here.

Best,

Radek

entities Matchmaking documentation

10 |1200

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

Answer 1 · 2020-04-02T07:48:49Z

Seth Du answered Apr 2, '20

Currently, PlayFab doesn’t provide a tutorial that can limit the entity API via Entity policy. You may consider send a thread on the Feature Request forum and votes from developers will help with the priority.

In addition, writing the ban information into Player Read-Only Data or Internal data for later retrieval can be a workaround, for example, client side verifies the ban state via player data and forbids players from creating Matchmaking tickets. Despite hackers can directly call API bypassing the condition judgement, you can also implement a punishment mechanism in your multiplayer server so that this banned player will have bad experience even he is able to join a match.

1

10 |1200

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

radekpibil commented · Apr 02, 2020 at 08:09 AM

Is there noone at playfab that can explain how that works, considering there is not tutorial?

What youre suggesting is something I considered the worst option, because it needs the most effort, just to do a workaround. Although, isnt what Im trying to do more like limiting the Entity policy using the entity API? Id be ok just with limitting the players based on Tags or something more readilly accessible. I basically want some way of saying that some kind of user cannot access /Match/CreateMatchmakingTicket and Im asking what are the options for "some kind of user" on the server side.

0 ·

question