This was originally a side question for this post, but is interesting on its own, therefore I am making a new post:
While waiting for a reply, I went ahead and attempted Solution 4 for bundling player attributes, using CloudScript (which was mentioned in private correspondence), build around a CloudScript function that
- obtains the original tickets from the matchmaikng_match_found event,
- obtains the connection information from Members[Creator].Attributes of each original ticket, then
- creates a Group containing the matched players, and finally
- adds the connection information to the group using SetObjects on this group.
- The players will have to poll ListMembership until they discover that they are members of such a group, then
- each member can obtain connection information from the group using GetObjects.
This, however, fails *before the first step*, since the rule never triggers.
Maybe this is because com.playfab.events.multiplayer.matchmaking.matchmaking_match_found is not a player event (it does not appear on the individual players' PlayStream tab, and its entity lineage has only null entries except for TitleId and NamespaceId)? This at least seems to be a current limitation it PlayStream-triggered CloudScript, according to this post.
The rule in the screenshot below yields no player_triggered_action_executed_cloudscript events (as opposed to an almost identical rule using an event triggered by WritePlayerEvent).
Please advice if this approach is at all possible given the current event trigger limitations.
