Tested on v1.82 arma3server_x64.exe.
The server does not follow the -config=<path> launch parameter and instead always loads a file called server.cfg in the same folder as arma3server_x64.exe.
It took me a few hours before I found out why my server didn't set the hostname properly...
Place a server.cfg config file in a directory DIFFERENT from the main server files.
Start the server with e.g. the following parameters:
"F:\games\steamapps\common\Arma 3\arma3server_x64.exe" cfg=C:\Arma3_server\basic.cfg -config=C:\Arma3_server\config.cfg
You can create another config.cfg in the same main server folder with different content to compare which file is being loaded
Hello.
Interesting if -config had any problems then our own Official servers wouldn't work. Are you sure it isn't a local issue?