[0.17.52] Unable to enable whitelist on linux headles

[Hornwitser]

Using the --server-whitelist command line parameter on Linux headless causes it to fail with the message

Code: Select all

   0.522 Error Main.cpp:662: use-server-whitelist must be set when server-whitelist is set.

use-server-whitelist is undocumented. There's enable-whitelist in config.ini, but setting either of these option to true has no effect.

[Loewchen]

Did you follow up --server-whitelist with the path to the list?

[Rseding91]

Thanks for the report however as Steve Jobs said: "You're doing it wrong"

The error message says explicitly what you need to do.

Output of --help on the binary:

--help.PNG (11.88 KiB) Viewed 2054 times

If you use "--server-whitelist FILE" you must also set "--use-server-whitelist"

[Hornwitser]

Oh, I missed that one, but I still think this is really confusing. The error message would make more sense if it said "--use-server-whitelist must be set when --server-whitelist is set" it didn't occur to me that these where command line options. But what I really find objectionable with the whitelist is how incredibly different it's handled.

Assuming you start out without any of the json lists and no options other than --start-server passed on the command line, if you ban a user from ingame the server creates a server-banlist.json and puts it into there and it's loaded on the next startup. If you promote a user from the console the server creates a server-adminlist.json and puts it in there and it's loaded on the next startup. If you whitelist a user from ingame (and enable the whitelist) no server-whitelist.json is created and the list is discarded when the server shuts down.

Also the generated config/config.ini contains the lines

Code: Select all

; Options: true, false
; enable-whitelist=false

But this doesn't seem to do anything.

PS: there's also a verify-user-identity in config/config.ini that doesn't seem to do anything either.