You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the #39 , the HC's aren't connecting to the main web server.
After some investigation, I believe the problem is the template (config.tpl) in the node arma server library, responsible to write a server config to the spawned server.
That's odd, I can use multiple HCs without any issues. Tested on Windows 10. Works fine with and without BattleEye enabled. Do you have any custom parameters or other quirks?
Well, that's strange...
Tried to undo my modifications and it worked...
I believe this could be a local problem, so I will close this issue :)
Thanks for the help, @Dahlgren!
Hi all, hi @Dahlgren
After the #39 , the HC's aren't connecting to the main web server.
After some investigation, I believe the problem is the template (
config.tpl
) in the node arma server library, responsible to write a server config to the spawned server.Using this way, both
headlessClients
andlocalClient
would be inserted with a comma in the end, like this:Also, I inserted
battleyeLicense = 1;
in the template as some guides recommend you to do it but I don't know if this will be of any difference.To make this work again, I changed the template to:
After this change, the HCs were able to connect again in the server.
Server is Windows 10, by the way.
Thanks!
The text was updated successfully, but these errors were encountered: