Robin C. Ladiges 69cef89953 fix: on reconnect do not disconnect the new client ... Currently when a client connects that is already there, the old socket is closed, and the code tries to reuse the existing client object by exchanging its socket. Reusing the same client object and just changing its socket does cause issues though with copies of the client in other threads. In the situations that I could reproduce, it always disconnected both sockets, the old one and then the new one. Instead I make a copy of the client object, use the new socket, remove the old object and add the new object to the collection. (cherry picked from commit 9e6c312c8e)		2022-10-10 11:12:28 -06:00
..
Client.cs	fix: on reconnect do not disconnect the new client	2022-10-10 11:12:28 -06:00
CommandHandler.cs	Added quotable arguments, potential fix for ban * not banning anyone.	2022-07-27 12:14:56 -06:00
DiscordBot.cs	better DiscordBot channel exceptions	2022-09-07 10:36:57 -06:00
FlipOptions.cs	Add scenario merging and run reformatting on solution	2022-03-01 15:08:53 -06:00
Program.cs	move the client.CurrentCostume update to the PacketHandler and log the packet	2022-10-10 11:09:39 -06:00
Server.cs	fix: on reconnect do not disconnect the new client	2022-10-10 11:12:28 -06:00
Server.csproj	Add a simple discord bot to manage the server	2022-06-12 18:48:24 -06:00
Settings.cs	Differentiated command channel and log channel	2022-08-22 18:58:42 -06:00
Time.cs	Add tag commands and improve command handling	2022-03-14 23:59:23 -06:00