Hi,
As per this article https://dev.epicgames.com/community/learning/knowledge-base/mXRKv/epic-online-services-how-can-i-ping-the-lobby-or-session-owner, it seems there is a feature request in Epic backlog to help with the latency and bandwidth testing.
Is there any update in this feature ?
Can we expect it in one of the upcoming releases ?
Thanks in advance,
Alvaro
There’s no update on this feature request, and no ETA.
Do you use BucketId? This is a special Session / Lobby attribute. You can use it to store information on the host, like geographic region. Then in searches, search by BucketId. As it’s the primary key on our backend, it dramatically improves search performance, and this is one way to get folks in the same region playing together. You can also store other info in addition to geographic region, like map, game mode, etc…
Hey,
Yeah, that is correct.
BucketId matching on the backend is exact-match only. The supported comparison operators when searching on EOS_LOBBY_SEARCH_BUCKET_ID (and EOS_SESSIONS_SEARCH_BUCKET_ID) are EOS_CO_EQUAL and EOS_CO_ANYOF (semicolon-separated list of exact values). There is no partial, prefix, or wildcard match, and BucketId is a single opaque string as far as the service is concerned.
So if you pack both region and game mode into the BucketId (e.g. “EU:TDM”), the client must know the exact combination to match, or must enumerate every valid game mode in a EOS_CO_ANYOF list (e.g. “EU:TDM;EU:CTF;EU:DM”). There is no way to say “any game mode, region=EU” with BucketId alone.
Recommended pattern for your case:
- Put dimensions that the user will always filter on (region) in the BucketId. This is what the BucketId is designed for and it significantly improves search performance once your lobby counts grow.
- Put dimensions that the user may want to leave open (game mode) in a regular lobby attribute. Omitting the attribute from the search parameters then returns lobbies with any value for it, which gives you the “any game mode” behavior you want.
Thanks,
Seb
Hey Alvaro,
No special restrictions compared to other attributes for updating it after lobby creation (needs to be updated by the owner, etc..).
Thanks,
Seb
Hi [Content removed] Bergeron ,
Thanks for the quick reply.
Indeed, we’re planning to have a region filter in our matchmaking query but we were unsure if we should use the BucketId or just a regular Lobby attribute.
I assume the BucketId doesn’t allows partial matches, so when you mention that we can also store the “game mode”, I guess we can’t use it on a scenario the user wants to match sessions with “any” game mode ( if we use lobby attributes the user can just omit this attribute during the search to match “any” game mode ).
Can you confirm is that’s correct ?
Thanks again !
Hi [Content removed] Bergeron ,
Thanks a lot for the clarification, we’ll implement as you suggests.
One last question, since the “bucketId” is a special lobby attribute, is there some restrictions if we try to update it after the lobby is created ? ( using EOS_LobbyModification_SetBucketId
)
Regards,
Alvaro