Barotrauma icon indicating copy to clipboard operation
Barotrauma copied to clipboard

Error while reading a message from server. {Value cannot be null. (Parameter 'paths')}

Open JoneKone opened this issue 2 years ago • 3 comments

Disclaimers

  • [X] I have searched the issue tracker to check if the issue has already been reported.
  • [X] My issue happened while using mods.

What happened?

Can't join Dedicated server, I think it's due to over sized ban reason. (I accidentally pasted the server rules/Message of the day)

xxxx,STEAM_1:1:xxx99xxx9,,VIP's can join our filled servers! Pass the queue.

Support this server? Ask in discord, if you want to donate bottle of Cola. As this server is run by the power of Cola! And get a VIP, for your trouble.

Want to make changes and or contribute! Know, Lua or C#? join us! Discord link below.


Ru

Rule 1.2: Captains and Security cannot punish crew members unless they are disobeying achievable orders. Security is ALWAYS loyal to Captain! Captain and Security can NOT join a mutiny.
Rule 1.3: You may fight back if is in self defence the only exceptions to this is the use of husk eggs.
Rule 1.4: you can use explosive to dispatch enemies as long as you kill more enemies then innocent crew.

Rule 2: Mutiny needs at least 3 Members to declare.
Rule 2.1: Mutiny needs to be announced in the radio (!!text!!) chat before any hostile action.

Rule 4: Players behaving in a toxic manner will 

Reproduction steps

  1. Ban somebody with a wall of text copy paste the reason.
  2. try to join the server. not 100% sure this is the issue.

Bug prevalence

Happens regularly

Version

0.18.12.0

-

No response

Which operating system did you encounter this bug on?

Linux

Relevant error messages and crash reports

Error while reading a message from server. {Value cannot be null. (Parameter 'paths')}
   at System.IO.Path.Combine(String[] paths)
   at Barotrauma.Networking.GameClient.ReadInitialUpdate(IReadMessage inc) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/GameClient.cs:line 1935
   at Barotrauma.Networking.GameClient.ReadLobbyUpdate(IReadMessage inc) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/GameClient.cs:line 2108
   at Barotrauma.Networking.GameClient.ReadDataMessage(IReadMessage inc) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/GameClient.cs:line 780
   at Barotrauma.Networking.LidgrenClientPeer.HandleDataMessage(NetIncomingMessage inc) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/Primitives/Peers/LidgrenClientPeer.cs:line 135
   at Barotrauma.Networking.LidgrenClientPeer.Update(Single deltaTime) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/Primitives/Peers/LidgrenClientPeer.cs:line 105
   at Barotrauma.Networking.GameClient.Update(Single deltaTime) in <DEV>/Barotrauma/BarotraumaClient/ClientSource/Networking/GameClient.cs:line 634

JoneKone avatar Jun 27 '22 19:06 JoneKone

I removed the "bad" ban and it started to let ppl in.

JoneKone avatar Jun 27 '22 20:06 JoneKone

Thank you for the report!

We're switching the banlist from this comma-separated text file to an xml file, and will take this into account in the new format. Linking to a ticket in our private repo to make sure we check this is fixed after we've switched to xml https://github.com/Regalis11/Barotrauma-development/issues/3410

Regalis11 avatar Jun 28 '22 07:06 Regalis11

Tested against dev commit https://github.com/Regalis11/Barotrauma-development/commit/d831645a3ccb4aadec718cb7146f0522c1ef4dae.

Initially I tried the dedicated server console and client console to give very long ban reasons (the one above copy pasted over itself even a few times) and there wasn't any visible issues, even if joining a dedicated after they were added. I had even tried copy pasting the above text over itself with no issues.

I figured perhaps its fine with the XML bans now, but when I went back to 0.18.15.1 I was unable to replicate the issue, so I am also unable to check if this is actually fixed. Trying to ban with a comma in the reason on a dedicated server console will simply think you are doing a different command and not work that way either.

NilanthAnimosus avatar Sep 28 '22 11:09 NilanthAnimosus

Has been fixed

Regalis11 avatar Mar 08 '23 14:03 Regalis11