From 2fb0df5ae3070b91a645f6d3085695c3500f1195 Mon Sep 17 00:00:00 2001
From: Jesse Fish <jesfish+git@gmail.com>
Date: Tue, 13 Mar 2018 20:11:28 -0700
Subject: [PATCH] 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.
---
 Facepunch.Steamworks/Client/LobbyList.cs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Facepunch.Steamworks/Client/LobbyList.cs b/Facepunch.Steamworks/Client/LobbyList.cs
index a8ed9a2..4470973 100644
--- a/Facepunch.Steamworks/Client/LobbyList.cs
+++ b/Facepunch.Steamworks/Client/LobbyList.cs
@@ -41,6 +41,8 @@ public void Refresh ( Filter filter = null)
             {
                 filter = new Filter();
                 filter.StringFilters.Add("appid", client.AppId.ToString());
+                client.native.matchmaking.RequestLobbyList(OnLobbyList);
+                return;
             }
 
             client.native.matchmaking.AddRequestLobbyListDistanceFilter((SteamNative.LobbyDistanceFilter)filter.DistanceFilter);