Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Cfg setting to adjust Palworld steam/query port #4469

Closed
Crimson-Decoded opened this issue Jan 27, 2024 · 2 comments
Closed

[Feature]: Cfg setting to adjust Palworld steam/query port #4469

Crimson-Decoded opened this issue Jan 27, 2024 · 2 comments

Comments

@Crimson-Decoded
Copy link

User story

As a server administrator, I want to be able to configure the Steam/Query port, so that I can host multiple servers

Game

Palworld

Linux distro

Ubuntu 22.04

Command

command: start, command: details

Further information

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 are two proposed changes.

One - lgsm/modules/info_game.sh

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

Modify the steamport so that it can accept variables configured in lgsm/config-lgsm/pwserver/.cfg
It appears info_game.sh is loaded after .cfg, so it overrides user configuration, even on ./pwserver start

Second, once that is done, in lgsm/config-lgsm/pwserver/_default.cfg

# 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

@Crimson-Decoded
Copy link
Author

actually, I suppose instead the info_game.sh edit would be
steamport="${steamport:-"0"}"
since by setting steamport in _default.cfg, we won't need to set its default value in info_game.sh, the way all other variables are handled.

@Crimson-Decoded
Copy link
Author

Closing in favor of 4454, as that was created first. transferring information to that thread.

@github-project-automation github-project-automation bot moved this from 🆕 New Issues to ✅ Done in LinuxGSM Backlog Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

1 participant