starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #2524] Arma Headless Client not using parms #1852

New issue

Closed

opened 2026-02-27 02:59:23 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 02:59:23 +03:00

Owner

Originally created by @ghost on GitHub (Sep 25, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2524

User Story

As a server admin, I want that the parms parameter is actually used so that the option -client is used in the start script.

Basic info

Distro: [Ubuntu 18.04]
Game: [Arma 3]
Command: [start]

Further Information

I followed the steps on this site and added a second arma 3 instance. I added to the lgsm/config-lgsm/arma3server-hc.cfg the option parms="-client -connect=${ip}:${port} -password=myserverpw" and started the server but the server started without these settings.

To Reproduce

Steps to reproduce the behaviour:
follow the steps described above.

Expected behaviour

server starting WITH -client

Originally created by @ghost on GitHub (Sep 25, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2524 ## User Story As a server admin, I want that the parms parameter is actually used so that the option `-client` is used in the start script. ## Basic info * Distro: [Ubuntu 18.04] * Game: [Arma 3] * Command: [start] ## Further Information I followed the steps on [this site](https://docs.linuxgsm.com/game-servers/arma-3#headless-client-setup-and-usage) and added a second arma 3 instance. I added to the `lgsm/config-lgsm/arma3server-hc.cfg` the option `parms="-client -connect=${ip}:${port} -password=myserverpw"` and started the server but the server started without these settings. ## To Reproduce Steps to reproduce the behaviour: follow the steps described above. ## Expected behaviour server starting WITH `-client`

kerem

2026-02-27 02:59:23 +03:00

closed this issue
added the
type: bug

game: ARMA 3
labels

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Sep 25, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.65. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Sep 25, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.65. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@Vexarii commented on GitHub (Dec 7, 2019):

I'm also facing the same issue trying to create headless clients.

The crux of it, after conducting some testing, appears to be that instance.cfg isn't reading properly.

_default.cfg reads fine, common.cfg reads fine...unfortunately instance.cfg does not.

I found that instance.cfg wasn't automatically created for each instance, so I created an instance.cfg for each of them and lgsm isn't reading these. Would you agree that this a similar experience to yourself @Fuggschen ?

@Vexarii commented on GitHub (Dec 7, 2019): I'm also facing the same issue trying to create headless clients. The crux of it, after conducting some testing, appears to be that instance.cfg isn't reading properly. _default.cfg reads fine, common.cfg reads fine...unfortunately instance.cfg does not. I found that instance.cfg wasn't automatically created for each instance, so I created an instance.cfg for each of them and lgsm isn't reading these. Would you agree that this a similar experience to yourself @Fuggschen ?

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@Vexarii commented on GitHub (Dec 7, 2019):

Fixed in an update 5 days ago - update lgsm per the below thread.
#2635

@Vexarii commented on GitHub (Dec 7, 2019): Fixed in an update 5 days ago - update lgsm per the below thread. #2635

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@ghost commented on GitHub (Dec 20, 2019):

sorry for the late answer (I don't check my mails so often)
unfortunately I'm not using lgsm anymore 'cause of this problem and I can't test it anymore

@ghost commented on GitHub (Dec 20, 2019): sorry for the late answer (I don't check my mails so often) unfortunately I'm not using lgsm anymore 'cause of this problem and I can't test it anymore

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@Claiyc commented on GitHub (Mar 23, 2022):

Fixed by #2635

@Claiyc commented on GitHub (Mar 23, 2022): Fixed by #2635

kerem commented

2026-02-27 02:59:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 24, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Mar 24, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.