whitelist.txt still looks correct with all 22 entries in there
Try to add player again via rcon command
whitelist.txt gets rewritten, line 1 is a corrupted/malformed entry, line 2 is new whitelist entry. Rest of entries is gone
Fix? Modifying whitelist to JUST steam64id with no :Playername#number behind it correctly reads the whitelist on server restart
‘[2020.09.21-12.07.38:570][ 0]ConanSandbox:Display: AServerBlacklist::LoadSettings(): Whitelist contains 22 unique entries’
I can provide the whitelist.txt that’s not being read correctly privately if needed
It doesn’t happen on my server. I haven’t had any issues with the whitelist since the update. What rcon do you use? Do you use the dedicated server launcher or renting a server?
Alright, I use the rcon provided by my host and I don’t use the dedicated server launcher. My whitelist uses the format Steam64ID:Playername#number and it works without an issue, even when it shows Steam64ID:Unknown. I have had multiple restarts so far.
EDIT: Maybe something to do with the dedicated server launcher and its configuration? - Probably not it:
The entire whitelist doesn’t get loaded, it only loads 1 entry that’s corrupted.
Because if you add another entry via rcon, it seems do do an entire rewrite of the whitelist.txt from what the server has in memory.
I just added another player via rcon, it restored all steam64id:PlayerName#number entries it knew from connects since last restart.
And when you do an rcon add from the corrupted load, the 1 ‘valid’ loaded entry it adds, is a corrupted entry in the whitelist.txt, followed by the just added new entry
Additionally, I can replicate this. Currently I have a Conan Exiles and the Isle of Siptah running on different ports for game, rcon, etc. They both have this same issue.
It might’ve only started happening since the latest patch/hotfix, because we played Siptah for about a week, only last weekend it started acting up. But we did not add a lot of players at that time yet, so I’m not entirely certain.
