Search lobbies by attributes doesn't work with OSSv2?

I’m trying to follow the example from the documentation.

I can create the lobby correctly. It works!!

The problem is I can only find it using the LobbyID. (That is using my EOS account → dev.epicgames.com). If I search for it using attributes the lobby cannot be found.

That’s why I think something in my configuration may be wrong.

This is my lobby setup:
1

And This is the schema in my DefaultEngine.ini

It’s the first time I’ve made a schema like this… I more or less understand how it works.

But I don’t know if there is some syntax error, or maybe there is something missing to be done… the little information available about it is a big problem.

Do you see any error or something missing in it?
Thank you very much for your help!!

ok, i found that for some strange reason the name attributes are not being saved correctly in the lobby… that explains why the searches don’t work…


3
Now we just need to know why the text strings are not sent…

Ok, I have come to the conclusion that it is an internal bug of the system.

At least you can work in the meantime because the lobbyID works.

If any forum administrator sees this post, let them know about this BUG to the developers so they can fix it in the next release.

Thank you very much and best regards!!

This is crazy!!
it is impossible to work with this!!
This naming scheme system is wreaking havoc!!
The system unreasonably changes all the names of the lobby attributes and that breaks everything!!


I don’t understand how they can release this… it’s not a beta… it’s a zeta…

In case anyone is interested in testing (Until they fix the bug).
You can make it work if you do this.

Lobby attributes in your code:

In DefaultEngine.ini

Now you can find your lobby and read the attributes like this.

To the developers:

What do I think about this?
1-I think this bug is a disaster (it broke everything).
2-I think that the concept of schema is unnecessarily complicated.
3-I think that using DefaultEngine.ini to define the properties of the attributes is a bad idea (in my opinion it would be better to do it from the C++ code).
4-The “SchemaCompatibilityId” flag makes everything work even worse (it doesn’t help, but it does the opposite).

This is just constructive criticism from the point of view of a regular user. I really hope it helps to improve the API.

Thank you so much!!

2 Likes

Hi Ivan3z,

I just wanted to say thank you so much for posting this. Thanks to you, my lobby invites are finally working. Honestly, can’t thank you enough for taking the time to post your solution - you are a hero!

Believe me… It’s a very bad solution.
The lobby scheme was a disaster. I hope they have fixed this in version 5.2…haven’t tried yet.
Best regards!!