[Server Request]: Generic Steam gameserver

Open
#4,534 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
linux, shell
Domain
cli, devops

Research direction

No files or tests are named. Start by reviewing the existing Steam server installation, configuration, and lifecycle command entry points, then compare them with the proposed generic settings. Done means a generic Steam server can be installed and managed with configured appid, executable, startup, stop, update, validation, and console behavior.

Written by the indexing model from the issue text.

Description

command: console command: install command: validate info: steamcmd status: no linux support type: game server request
Game server

variable

Linux support
  • Yes
Steam

Yes

Steam appid

variable

Guides

An idea, for the numerous steam games that aren't supported yet or won't be (unpopular, or need for wine/proton): A generic Steam gameserver install would allow users to essentially install whatever steam server they want, and manage/update it with LGSM.
This can be provided as-is, with no guarantee that it will work, placing most of the configuration on the user, but still allowing them to use lgsm commands for start/stop/update/validate/console keeping it normalized between multiple gameservers

With it, the configuration settings would be limited. Settings that would normally not be touched would become primary configurations.
For example, appid, executabledir, executable, preexecutable, startparameters, consoleinteractive, consoleverbose, stopmode would all be primary configurations in _default.cfg, querymode would probably just be session based for simplicity.
Possibly offering a custom stopmode command for some servers that do something particularly strange. essentially a stopcommand variable that allows a custom string to be sent to the server's console, rather than just "stop"/"quit"/etc,
It would be on the user to configure these to what they need to be for the server.
Almost all of this is already present in every steam server install, with the exception of preexecutable that only shows up on some servers (like minecraft for the java executable), but it would just be a very barebones install with no "fix_server.sh" module.

And as much as it has ever been avoided, adding a "windows version" variable that causes the steamcmd install/verify to use the flag to force windows version (steamcmd +@sSteamCmdForcePlatformType windows +login anonymous ...) wouldn't be so bad in a "as-is" generic steam game install. it would still be entirely on the LGSM user to overcome any issues they run into, but with the freedom to do what they wanted.

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Shell
Stars
4.9k
Forks
866
Avg merge
17h 58m
Merged PRs (30d)
100

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GameServerManagers/LinuxGSM

All issues in GameServerManagers/LinuxGSM

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.