starred/LinuxGSM

Fork 0

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

[GH-ISSUE #4454] [Feature]: QueryPort - pwserver #2784

New issue

Closed

opened 2026-02-27 03:05:25 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 03:05:25 +03:00

Owner

Originally created by @qwertynoone on GitHub (Jan 22, 2024).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4454

User story

As a dev, i want query port config for palworld, so that i can run multiple servers on the same host

Game

Palworld

Linux distro

Debian 11

Command

command: details

Further information

i tried to launch multiple servers for palworld using the same host but i can't update query port as the only available port variable for this server is the server port, would be nice to add queryport support so we can change the port used for steam (27015)

# Use game server config file to edit, used for port check script (workaround)
port="8211"

Originally created by @qwertynoone on GitHub (Jan 22, 2024). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4454 ### User story As a dev, i want query port config for palworld, so that i can run multiple servers on the same host ### Game Palworld ### Linux distro Debian 11 ### Command command: details ### Further information i tried to launch multiple servers for palworld using the same host but i can't update query port as the only available port variable for this server is the server port, would be nice to add queryport support so we can change the port used for steam (27015) ``` # Use game server config file to edit, used for port check script (workaround) port="8211" ```

kerem

2026-02-27 03:05:25 +03:00

closed this issue
added the
type: feature

distro: Debian

command: details
labels

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jan 22, 2024):

It doesn't appear you can change the 27015 port yet. This is currently a "feature" of the game server.

@dgibbs64 commented on GitHub (Jan 22, 2024): It doesn't appear you can change the 27015 port yet. This is currently a "feature" of the game server.

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@chaos-baum commented on GitHub (Jan 24, 2024):

https://gist.github.com/Toakan/3c78a577c21a21fcc5fa917f3021d70e

Maybe the stated startup parameters listed there can be implemented.

@chaos-baum commented on GitHub (Jan 24, 2024): https://gist.github.com/Toakan/3c78a577c21a21fcc5fa917f3021d70e Maybe the stated startup parameters listed there can be implemented.

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@derkalle4 commented on GitHub (Jan 25, 2024):

Hi, had the same problem and -queryport seems to default to 27015 and can be change on the startup parameters.

This works for me as a workaround. Somehow the game server itself has -port and -publicport

servername="Palworld.Party PVP Battle Arena"
port="8211"
qport="8212"
rport="8213"
players="100"

startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -port='${port}' -publicport='${port}' -queryport='${qport}' -RCONPort='${rport}' -players='${players}'"

@derkalle4 commented on GitHub (Jan 25, 2024): Hi, had the same problem and -queryport seems to default to 27015 and can be change on the startup parameters. This works for me as a workaround. Somehow the game server itself has -port and -publicport ``` servername="Palworld.Party PVP Battle Arena" port="8211" qport="8212" rport="8213" players="100" startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -port='${port}' -publicport='${port}' -queryport='${qport}' -RCONPort='${rport}' -players='${players}'" ```

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@Crimson-Decoded commented on GitHub (Feb 2, 2024):

Adding some additional information here.

While most other things can be configured in the PalWorldSettings.ini file, the Steam/query port is not one of them, so it needs to be configured as a start parameter.

Currently, there is a combination of two proposed changes.

One - lgsm/modules/info_game.sh

fn_info_game_pw() {
        servername="${servername:-"NOT SET"}"
        port="${port:-"0"}"
        steamport="${steamport:-"0"}"
        unknownport="1985"
}

Modify the steamport so that it can accept variables configured in lgsm/config-lgsm/pwserver/.cfg
The current line in this file is:

steamport="27015"

It appears info_game.sh is loaded after .cfg, so it overrides user configuration of that variable on ./pwserver start, ./pwserver details, and likely others

Second, once the above change is made, in lgsm/config-lgsm/pwserver/_default.cfg:
add in steamport as a configuration and append -queryport to the start parameters

# Configure Steam/Query port to allow for multiple servers
steamport="27015"

## Server Parameters | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters
## Game Server Docs | https://tech.palworldgame.com/dedicated-server-guide#linux
startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -queryport='${steamport}'"

With the current iteration, even if I create the variable 'steamport' in .cfg files, no matter what I set it to, it gets overwritten with 27015, and it appears to affect the actual game start (when the variable is steamport, it works fine if I name it something different)
The change to game_info.sh will also allow it to display the user-configured port in ./pwserver details

Verified these changes to info_game.sh and the .cfg on a test instance of Palworld

Command-line Parameters
============================================================================================================================================================================================================================================
 ./PalServer-Linux-Test EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='LinuxGSM' -port='8212' -queryport='27017'

Ports
============================================================================================================================================================================================================================================
Change ports by editing the parameters in:
/home/pwserver2/lgsm/config-lgsm/pwserver

Useful port diagnostic command:
ss -tuplwn | grep PalServer-Linux

DESCRIPTION  PORT   PROTOCOL  LISTEN
Game         8212   udp       2
Steam        27017  udp       1
Unknown      1985   tcp       1

Status: STARTED

pwserver2@obsidian:~$ ss -tuplwn | grep PalServer-Linux
udp   UNCONN 0      0            0.0.0.0:8212       0.0.0.0:*    users:(("PalServer-Linux",pid=799165,fd=42))
udp   UNCONN 0      0            0.0.0.0:27017      0.0.0.0:*    users:(("PalServer-Linux",pid=799165,fd=23))
tcp   LISTEN 0      1            0.0.0.0:33871      0.0.0.0:*    users:(("PalServer-Linux",pid=799165,fd=43))
tcp   LISTEN 0      8            0.0.0.0:8213       0.0.0.0:*    users:(("PalServer-Linux",pid=799165,fd=40))
tcp   LISTEN 0      128        127.0.0.1:46303      0.0.0.0:*    users:(("PalServer-Linux",pid=799165,fd=15))

note the steam port is listed updated, and that it's actually listening on 27017 as configured:

# Use game server config file to edit, used for port check script (workaround)
port="8212"

# Configure Steam/Query port to allow for multiple servers
steamport="27017"

startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -port='${port}' -queryport='${steamport}'"

@Crimson-Decoded commented on GitHub (Feb 2, 2024): Adding some additional information here. While most other things can be configured in the PalWorldSettings.ini file, the Steam/query port is not one of them, so it needs to be configured as a start parameter. Currently, there is a combination of two proposed changes. One - lgsm/modules/info_game.sh ``` fn_info_game_pw() { servername="${servername:-"NOT SET"}" port="${port:-"0"}" steamport="${steamport:-"0"}" unknownport="1985" } ``` Modify the steamport so that it can accept variables configured in lgsm/config-lgsm/pwserver/.cfg The current line in this file is: ``` steamport="27015" ``` It appears info_game.sh is loaded after .cfg, so it overrides user configuration of that variable on ./pwserver start, ./pwserver details, and likely others Second, once the above change is made, in lgsm/config-lgsm/pwserver/_default.cfg: add in steamport as a configuration and append -queryport to the start parameters ``` # Configure Steam/Query port to allow for multiple servers steamport="27015" ## Server Parameters | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters ## Game Server Docs | https://tech.palworldgame.com/dedicated-server-guide#linux startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -queryport='${steamport}'" ``` With the current iteration, even if I create the variable 'steamport' in .cfg files, no matter what I set it to, it gets overwritten with 27015, and it appears to affect the actual game start (when the variable is steamport, it works fine if I name it something different) The change to game_info.sh will also allow it to display the user-configured port in ./pwserver details --------------------------------------------------------------------------------------- Verified these changes to info_game.sh and the .cfg on a test instance of Palworld ``` Command-line Parameters ============================================================================================================================================================================================================================================ ./PalServer-Linux-Test EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='LinuxGSM' -port='8212' -queryport='27017' Ports ============================================================================================================================================================================================================================================ Change ports by editing the parameters in: /home/pwserver2/lgsm/config-lgsm/pwserver Useful port diagnostic command: ss -tuplwn | grep PalServer-Linux DESCRIPTION PORT PROTOCOL LISTEN Game 8212 udp 2 Steam 27017 udp 1 Unknown 1985 tcp 1 Status: STARTED pwserver2@obsidian:~$ ss -tuplwn | grep PalServer-Linux udp UNCONN 0 0 0.0.0.0:8212 0.0.0.0:* users:(("PalServer-Linux",pid=799165,fd=42)) udp UNCONN 0 0 0.0.0.0:27017 0.0.0.0:* users:(("PalServer-Linux",pid=799165,fd=23)) tcp LISTEN 0 1 0.0.0.0:33871 0.0.0.0:* users:(("PalServer-Linux",pid=799165,fd=43)) tcp LISTEN 0 8 0.0.0.0:8213 0.0.0.0:* users:(("PalServer-Linux",pid=799165,fd=40)) tcp LISTEN 0 128 127.0.0.1:46303 0.0.0.0:* users:(("PalServer-Linux",pid=799165,fd=15)) ``` note the steam port is listed updated, and that it's actually listening on 27017 as configured: ``` # Use game server config file to edit, used for port check script (workaround) port="8212" # Configure Steam/Query port to allow for multiple servers steamport="27017" startparameters="EpicApp=PalServer -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS -servername='${servername}' -port='${port}' -queryport='${steamport}'" ```

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@PlayMTL commented on GitHub (Feb 11, 2024):

I think the PR https://github.com/GameServerManagers/LinuxGSM/pull/4479 should close this issue. It's release in v24.1.3

@PlayMTL commented on GitHub (Feb 11, 2024): I think the PR https://github.com/GameServerManagers/LinuxGSM/pull/4479 should close this issue. It's release in v24.1.3

kerem commented

2026-02-27 03:05:26 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 17, 2025):

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 (Feb 17, 2025): 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.