starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #4091] [BUG] Ark Survival Evolved: Unable to display game details #2613

New issue

Open

opened 2026-02-27 03:04:07 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 03:04:07 +03:00

Owner

Originally created by @ajdergute on GitHub (Jan 31, 2023).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4091

User Story

As a user, I want 'arkserver details' to output server name, password and admin password.

Basic info

Distro: Debian 11
Game: Ark Survival Evolved
Command: details
LinuxGSM version: [v22.2.1]

Further Information

The details command always display "NOT SET" as follows:

Server name:      NOT SET
App ID:           376030
...
Server password:  NOT SET
Admin password:   NOT SET

To Reproduce

Steps to reproduce the behaviour:

Install Ark as described on website
Execute details command

Expected behaviour

I expect to see server name and admin password to be displayed.

Ark seems to store GameUserSettings.ini with UTF-16LE encoding. Even if this file is converted with iconv, ark seems to rewrite it on next start. As sed is unable to parse this file we are faced with NOT SET strings.

With additional convertion sed works again.
See this for reference:

                iconv -f utf-16le -t utf-8 ${servercfgfullpath} -o ${servercfgfullpath}.utf8
                servername=$(sed -nr 's/^SessionName=(.*)/\1/p' "${servercfgfullpath}.utf8")
                adminpassword=$(sed -nr 's/^ServerAdminPassword=(.*)/\1/p' "${servercfgfullpath}.utf8")
                serverpassword=$(sed -nr 's/^ServerPassword=(.*)/\1/p' "${servercfgfullpath}.utf8")

Originally created by @ajdergute on GitHub (Jan 31, 2023). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4091 ## User Story As a user, I want 'arkserver details' to output server name, password and admin password. ## Basic info - **Distro:** Debian 11 - **Game:** Ark Survival Evolved - **Command:** details - **LinuxGSM version:** [v22.2.1] ## Further Information The details command always display "NOT SET" as follows: ``` Server name: NOT SET App ID: 376030 ... Server password: NOT SET Admin password: NOT SET ``` ## To Reproduce Steps to reproduce the behaviour: 1. Install Ark as described on website 2. Execute details command ## Expected behaviour I expect to see server name and admin password to be displayed. Ark seems to store `GameUserSettings.ini` with UTF-16LE encoding. Even if this file is converted with iconv, ark seems to rewrite it on next start. As `sed` is unable to parse this file we are faced with `NOT SET` strings. With additional convertion sed works again. See this for reference: ``` iconv -f utf-16le -t utf-8 ${servercfgfullpath} -o ${servercfgfullpath}.utf8 servername=$(sed -nr 's/^SessionName=(.*)/\1/p' "${servercfgfullpath}.utf8") adminpassword=$(sed -nr 's/^ServerAdminPassword=(.*)/\1/p' "${servercfgfullpath}.utf8") serverpassword=$(sed -nr 's/^ServerPassword=(.*)/\1/p' "${servercfgfullpath}.utf8") ```

kerem added the

game: Ark: Survival Evolved

labels

2026-02-27 03:04:07 +03:00

kerem commented

2026-02-27 03:04:08 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Feb 16, 2023):

Interesting problem. Something may have changed for the server as it has been working for several years at this point.

@dgibbs64 commented on GitHub (Feb 16, 2023): Interesting problem. Something may have changed for the server as it has been working for several years at this point.

kerem commented

2026-02-27 03:04:08 +03:00

Author

Owner

@Claiyc commented on GitHub (Feb 16, 2023):

ark is incredibly weird regarding the encoding of the .ini files. I ran into multiple issues with that a few years back as well. Not quite sure if we want to do something against that on lgsm side (as it is clearly an issue with ark). Normally you can work around it by changing values or the order of parameters in the .ini and restarting the server.

@Claiyc commented on GitHub (Feb 16, 2023): ark is incredibly weird regarding the encoding of the .ini files. I ran into multiple issues with that a few years back as well. Not quite sure if we want to do something against that on lgsm side (as it is clearly an issue with ark). Normally you can work around it by changing values or the order of parameters in the .ini and restarting the server.

kerem commented

2026-02-27 03:04:08 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Feb 16, 2023):

Sounds like it may require a bunch of messing around on our end. Would be nice for us to have workarounds but it sounds very much like a trial and error issue.

Alternatively the ark Devs sort it out but since ark 2 is in full swing I doubt they will bother

@dgibbs64 commented on GitHub (Feb 16, 2023): Sounds like it may require a bunch of messing around on our end. Would be nice for us to have workarounds but it sounds very much like a trial and error issue. Alternatively the ark Devs sort it out but since ark 2 is in full swing I doubt they will bother

kerem commented

2026-02-27 03:04:08 +03:00

Author

Owner

@Claiyc commented on GitHub (Feb 16, 2023):

yes, I don't really thinkt that something about this is gonna happen on arks side.. What makes it even more difficult to fix is that the issue is not really reproducable. At least I didn't find a scheme in which this issue occurs yet

@Claiyc commented on GitHub (Feb 16, 2023): yes, I don't really thinkt that something about this is gonna happen on arks side.. What makes it even more difficult to fix is that the issue is not really reproducable. At least I didn't find a scheme in which this issue occurs yet

kerem commented

2026-02-27 03:04:08 +03:00

Author

Owner

@ajdergute commented on GitHub (Feb 16, 2023):

As far as I understand, Ark reads the file on startup and re-encode it. If it contains characters which are not part of usascii it will encode the whole file with utf16le.

There are multiple sources out there, e.g.:
https://github.com/arkmanager/ark-server-tools/issues/1025#issuecomment-670036388

This is basically what I experience. Du you experience something different? This seems to be stable and reproducible. Just create an config and add some umlauts. Start the game and see what happens.

I think it's the most convenient way to treat this file as utf16le encoded. As a result of this LGSM should do some post-processing to get sed and other tools working.

@ajdergute commented on GitHub (Feb 16, 2023): As far as I understand, Ark reads the file on startup and re-encode it. If it contains characters which are not part of usascii it will encode the whole file with utf16le. There are multiple sources out there, e.g.: https://github.com/arkmanager/ark-server-tools/issues/1025#issuecomment-670036388 This is basically what I experience. Du you experience something different? This seems to be stable and reproducible. Just create an config and add some umlauts. Start the game and see what happens. I think it's the most convenient way to treat this file as utf16le encoded. As a result of this LGSM should do some post-processing to get sed and other tools working.

kerem referenced this issue

2026-02-27 03:55:35 +03:00

[PR #2613] [MERGED] code de-lint and correct using shellcheck standards #3725