Add: StarRupture

[SavageCore]

Description

Not sure if we want this to be Wine based like in #366 or not but this one works for me with Proton out-of-the-box whereas #366 doesn't seem to be working and I'd already done the work so thought I might as well send it. Merged with the README of #366 as that had some very nice documentation, I just cleaned it up a bit.

Closes #344

Checklist for all submissions

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change? 🙊
• Have you tested and reviewed your changes with confidence that everything works?
• Did you branch your changes and PR from that branch and not from your master branch?
  • If not, why?:

• You verify that the start command applied does not use a shell script
  • If some script is needed then it is part of a current yolk or a PR to add one
• The egg was exported from the panel

New egg Submissions

1. Does your submission pass tests (server is connectable)?
2. Does your egg use a custom docker image?
   • Have you tried to use a generic image?
   • Did you PR the necessary changes to make it work?
3. Have you added the egg to the main README.md and any other README files in subdirectories of the egg according to the alphabetical order?
4. Have you added a unique README.md for the egg you are adding according to the alphabetical order?
5. You verify that the start command applied does not use a shell script
   • If some script is needed then it is part of a current yolk or a PR to add one
6. The egg was exported from the panel

[brainshead]

maybe we can have 2 one base on wine and one on Proton?
i fixed the startup for wine egg.
btw i have copied your readme , it has better layout ;) , is that ok ?

[SavageCore]

btw i have copied your readme , it has better layout ;) , is that ok ?

That's great, I pushed another update to it.

[brainshead]

added extra text.

[SkippTekk]

Just did a fresh install, it's complaining about a Log file not created. Gonna create and see if it works.

[brainshead]

Just did a fresh install, it's complaining about a Log file not created. Gonna create and see if it works.

thats still old egg. and the wine one #366 , not for this egg.

[SkippTekk]

thats still old egg. and the wine one #366 , not for this egg.

Then how would i use the Proton on? I followed the link https://github.com/SavageCore/game-eggs/tree/feature/StarRupture and that's what i got? Or em i totally wrong in the case.

Edit: I'm an idiot... i totally forgot i had to save after doing the Egg update...

Edit 2: Never mind... Not sure what im doing wrong as the above is still showing and i think im downloading the correct .json file?

Edit 3: Make sure the Startup line is updated... that's what i missed and it's running

[SavageCore]

Glad you're up and running. Both eggs should work fine now. But yeah, when switching eggs it is better to remove from the nest and re-add as various config like that can "stick" and cause issues. I learnt that myself doing this!

[Tankdoz]

thanks for creating an egg so quickly. Unfortunately I can not get a New World to be created. I follow your instructions up till the point to wait for the server to load and I was able to set both the admin as well as the game password, but an Autosave0.sav never shows up in /home/container/StarRupture/Saved,. I even waited for 5 minutes to see if the autosave would kick in , but never. I do get access to the server with the Manage Server option, but the join option never finds the server. Would you be able to point me in the right direction?

[brainshead]

Which option did you go for ?
Option 1: when creating a world and joining , you can save in menu , this would make a save on the server and auto save is on 15 min it look likes.
Option 2 : It should make a save file when setting is used:

"StartNewGame": "true",
"LoadSavedGame": "false"

[Tankdoz]

I used both options, neither one worked for me. Should the logs tell me why they cannot create a savefile?

[SavageCore]

After the 0.1.1 hotfix I had trouble getting DSSettings.txt to take affect. I figured out the only time it worked was if the file existed BEFORE first launch of the server, so I added the Recommended Production Configuration to the install script.

Thanks to @gOOvER for the implementation.

[Tankdoz]

I tried the updated workflow from a clean server install, but I get stuck at bullet 5:Start the server and join to verify it works. Unfortunately my game client says: cannot find server. It was able to find a server and create passwords when I used Manage Server earlier, so I'm not sure why the Join Game option does not work. I use the same IP:port to connect. It says 'no sessions available in the list so I try the Dedicated Server button, enter the IP:port and get a cannot find server.

[HoudayerPierre]

I tried the updated workflow from a clean server install, but I get stuck at bullet 5:Start the server and join to verify it works. Unfortunately my game client says: cannot find server. It was able to find a server and create passwords when I used Manage Server earlier, so I'm not sure why the Join Game option does not work. I use the same IP:port to connect. It says 'no sessions available in the list so I try the Dedicated Server button, enter the IP:port and get a cannot find server.

I tried so mutch like you for hours to finally discover this thing :
Use your public IP insted of the local one witch is not working for me, very strange, (maybe a network bug on the server as it's 172.18.0.2).

[SavageCore]

That's correct. Essentially server registers with EGS, "Hey, I'm new here", EGS stores WAN IP. When clients are connecting EGS looks in its table for the IP it has stored and returns that to the client.

Anyway, these conversations are off-topic for this PR. Join the Discord and use #tech-support channel. There's a few of us in there helping out with server issues when we can.

[Frostbyt3]

I used Icarus as a base for mine and have had no issues if you guys would like to take a look at my branch.