“the 200 results limit to the session search is by design”
Every time I query sessions using the BucketId, the same 200 sessions are returned.
As a result, other sessions are never displayed unless I explicitly query by attributes.
If there are 1,000 total sessions, how exactly does EOS select which 200 sessions to return?
What are the rules for EOS session filtering when a client searches for sessions?
thanks
itho
(itho)
2
Hello! The EOS Sessions Interface is not designed to be a classic server browser that offers a full list of available sessions with pagination.
Rather, it offers the client a selection of sessions that match the given criteria, designed around quick search and join behaviour.
The rules around which sessions are returned are not publicly documented nor intended to be relied upon.
If there is a specific session that you’re trying to find, using attributes to search for it is the intended solution.
If you want users to be able to specify a single session, you can add a short code to session attributes rather than using the session ID.
I truly appreciate your response. This has been very helpful
thank you