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

[Bug]: Can't set world or other settings for Stationeers server #4414

Open
hades200082 opened this issue Dec 13, 2023 · 7 comments
Open

[Bug]: Can't set world or other settings for Stationeers server #4414

hades200082 opened this issue Dec 13, 2023 · 7 comments

Comments

@hades200082
Copy link

User story

As a server admin I want to choose the map that the server runs so that my players can play on that map

Game

Stationeers

Linux distro

Ubuntu 20.04

Command

command: start

Further information

Partially referencing #4137 - the startup still complains that settings.xml is missing.

Additionally I've been unable to get the server to load any map other than the moon. There is no documentation for the GSM Stationeers server on how to change this.

Relevant log output

No response

Steps to reproduce

No response

@Twipped
Copy link

Twipped commented Jun 1, 2024

I'm also having this problem. I thought it might be a permissions issue with my bind, so I switched to a volume instead. No dice, still no settings.xml file, and I can't seem to find one anywhere.

docker-compose config:

version: "3.8"
services:
  # bind mount example
  linuxgsm-st-bind:
    image: gameservermanagers/gameserver:st
    # image: ghcr.io/gameservermanagers/gameserver:st
    container_name: statserver
    restart: unless-stopped
    volumes:
      - linuxgsm-st:/data
    ports:
      - 27016:27016/udp
    network_mode: host

volumes:
  linuxgsm-st:

@Twipped
Copy link

Twipped commented Jun 1, 2024

I finally got the server working by logging into a shell in the container, and curling this file into /data/serverfiles/setting.xml

I then still had to edit the file, because it's apparently missing the closing </SettingData> xml tag.

That got the server working, but I was stuck on the moon.

I then edited /app/lgsm/config-lgsm/stserver/common.cfg to add the line startparameters="-new Mars" and rebooted the server. That got it to create a new mars save. I edited the file again to change it to `startparameters="-loadlatest" and after another reboot, the server behaved the way I expected it to.

@hades200082
Copy link
Author

Honestly I gave up on LinuxGSM after this got no attention.

6 months to get a partial workaround for a system that's meant to make setting up and running game servers easy tells me that linuxGSM is DOA.

@Twipped
Copy link

Twipped commented Jun 1, 2024

@hades200082 I hear that. I would have given up on it too, but every other stationeers docker image I tried was even worse.

@dgibbs64
Copy link
Member

dgibbs64 commented Jun 1, 2024

Sadly time is always a factor and do this in my (very limited) free time for fun. I welcome PR's to fix the issue.

@hades200082
Copy link
Author

Since I'm no longer using LinuxGSM and no one seems interested in fixing it anyway I'm closing this to get it off my github open issues list.

@dgibbs64 I didn't mean for my comment above to be a dig at you or anyone else working on and releasing this stuff for free. It's just frustrating that something that is advertised as a feature of the system doesn't work as it should and no one seemed to care.

@github-project-automation github-project-automation bot moved this from 🆕 New Issues to ✅ Done in LinuxGSM Backlog Aug 14, 2024
@dgibbs64 dgibbs64 reopened this Aug 14, 2024
@github-project-automation github-project-automation bot moved this from ✅ Done to 📋 Sentenced Issues in LinuxGSM Backlog Aug 14, 2024
@dgibbs64
Copy link
Member

Re-opening as it needs to be recorded as a bug.

It's not that no one cares but that I have a lack of time to deal with it all. In between having a full-time job in IT and family commitments etc I fit this project (that I have been running for 10 years) in where I can. The reality is that this project could be a full-time job (I wish it was) with the volume of bugs and features. I heavily rely on volunteers submitting PR's to get some stuff fixed quickly. I share your frustration as well. Many similar projects by this point end up abandoned by the maintainers because of similar life commitments. I will however continue to maintain as best I can even if somewhat slow in fixing some issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Sentenced Issues
Development

No branches or pull requests

3 participants