Correctly handle lobby refresh with null filter

Currently if a null filter is given, more filters are added to the call
than expected. This change makes a lobby request after the appid filter
is added and returns immediately resolving the issue.
This commit is contained in:
Jesse Fish 2018-03-13 20:11:28 -07:00
parent aa3a6d4d24
commit 2fb0df5ae3

View File

@ -41,6 +41,8 @@ public void Refresh ( Filter filter = null)
{ {
filter = new Filter(); filter = new Filter();
filter.StringFilters.Add("appid", client.AppId.ToString()); filter.StringFilters.Add("appid", client.AppId.ToString());
client.native.matchmaking.RequestLobbyList(OnLobbyList);
return;
} }
client.native.matchmaking.AddRequestLobbyListDistanceFilter((SteamNative.LobbyDistanceFilter)filter.DistanceFilter); client.native.matchmaking.AddRequestLobbyListDistanceFilter((SteamNative.LobbyDistanceFilter)filter.DistanceFilter);