Ciao Greg,

yes this thing would be great, it would be perfect for what I need!

I'm currently trying this solution, please tell me if you think there might be any problems:

when a user enters in the view with the lobby browser I invoke a script on the BC side in which I save the user's profileId in a Global Entity. When the user leave the browser view, I invoke the same service that removes him.
when a user creates a lobby, I develop an API Hook which at the CreateLobby event (post) takes the IDs saved in the list and with SysSendEventToProfiles informs the users to update the lobby list
when a user leaves, with the LeaveLobby Hook API (post), I check if the lobby has been removed, if so, as per point 2, I inform the users to update the list

The change you suggest would be an excellent further optimization and would be fantastic

My doubts now are these:

although the number of users in the list saved in Global Enity is less than 1000 (average 400 users), do you think there could be performance problems?
if the app crash or closed unexpectedly, the user list in the Global Entity may not be updated because the removal event does not arrive at BC, at that point if SysSendEventToProfiles sends to non-connected profileIds, what happens? I have to try and find a way to clean the list.

Suggestions?

Thank you!

Alessio

Alessio Falsetti