First off I apologize putting this in the general forum as I could not see a clear forum to post this in. https://www.dropbox.com/sh/63a40rpvpwizgdp/AADsGALZKrBm9S3bqpgeefOja?dl=0 I created mew server on Nitrado I went to my system D:\Steam\steamapps\workshop\content\383120\ and copied 2142575290\ into the scenario folder and renamed it to Purgatory Fresh Build server never started: Empyrion Dedicated.Yaml <Content> <Scenarios> <Default MultiPlayer> GameOptions.yaml <Purgatory> GameOptions.yaml <Saves> <Games> <DediGame> GameOptions.yaml So I changed Dedicated.Yaml to point to the Purgatory Scenario. I changed the GameOptions.yaml in the Scenarios Purgatory Folder to be how I wished I started server and connected just fine DiffDegradationSpeed: Off # default value Was a setting that was set and when I entered game and fired pistol it was taking degradation which led me to believe settings did not take. Also when I checked difficulties in game they were at default. I left game. Exited server. Downloaded gameoptions.yaml from the Purgatory save folder and it is the same file I set initially with my settings. So my settings are not being used and my seed is changed but not changing planet, what do I need to do to change play fields seeds? Any help would be appreciated. I did a lot of google checks and found some posts that should have helped but have not. I am confused as the save game settings appear to be what I wish but they are just not being applied to the actual game play. Thanks in advance
I went in and removed the Scenario from the Dedicated and put back to default multiplayer one. Loaded server, logged in, logged out, turned off server, there was no GameOptions.yaml in the NewGame0 folder save so I put a copy in there, and restarted server. Logged in checked and nothing. I was able to add myself to the admin of the server easily enough and that works just fine.
Nitrado is haveing an error in there GameOptions.yaml export. We contacted them to correct this error. Best is to write them a support assist ticked and ask them when they will fix this.
I have been having similar issues with Nitrado and raised a ticket a couple of days ago. Their reply was that the problem was with Eleon needing to patch the game: "Thank you for your support request. We have been communicating with the game developers and they have discovered something they need to patch that relates to this particular difficulty. Unfortunately, we have to wait for an update for this." This is very frustrating as you can imagine.
I was using Nitrado about a month and half ago for my Empyrion server, but they have been having multiple issues in relation to their management of config files. They normally offer as part of their service a GUI interface to allow less savvy admins ease of access in changing various parameters of their servers (and when it works, it's great!), but somehow the jobs that run this GUI have been fowling up configs pretty badly for Empyrion. They do this GUI interface for ARK servers as well as a few other games, and I've never run into issues in my 4+ years of using them, until recently with Empyrion. After weeks of non-response I finally shut down my Nitrado server and switched to a low.ms server. You might be able to request a refund from Nitrado, as I've heard they are usually pretty reasonable about honoring them if customers have issues, just be sure to follow their process. I didn't bother cause the amount wasn't worth the trouble for me, and I did get some playable time even if it was filled with more frustration than I would've preferred. Anyhow, if you are a savvy admin, low.ms should be no trouble as you can easily and directly update the configs and I have not seen any sort of automated jobs by low.ms which could cause problems so far. But you do need to know where everything is in the file structure of an Empyrion Dedicated server. All said, since switching to low.ms for Empyrion, my server has been stable, and as a plus, whenever there is an update to Empyrion, the "force update" feature low.ms has, has allowed me to get the server back online quickly. Nitrado I believe patches only at night which can leave your server version out of sync for a day. Anyhow, I'll be keeping both hosting companies in mind for future servers of various games I play, as this is the first negative experience I've had with Nitrado, and I have been using them for years, but I also must admit I'm pretty impressed with low.ms so far.
Yeah I switched to Low.MS that day and it has been great. Thier support is online in Discord too so the questions I had when getting it set up were answered quickly. I still have my ARK servers on Nitrado and have no reason to move them but the Empyrion is now on low.ms
I started a Nitrado-hosted Empyrion server about 2 months ago, and like you, I also had the really annoying gameoptions.yaml bug where it doesn't save and the file is overwritten everyday. You'll notice Nitrado's gameoptions.yaml file is formatted really awkwardly compared to a standard gameoptions.yaml. What I did temporarily was I uploaded my own gameoptions.yaml file every day (because Nitrado servers restart every morning - mine reboots around 5:35am ET) . You can use mine if you want - see attached but be sure to look at my settings. Nitrado provides FTP credentials, so you can upload it via FTP or use the web panel. Not sure how or why, but the problem disappeared for me about a month ago. I think it coincided with a game update back in mid-to-late July. I didn't think of it at the time, but you might be able to set the file as Read Only when you FTP in. To make sure your uploaded gameoptions.yaml truly worked: Make sure your Steam ID is listed as a level 9 admin. There is an adminconfig.yaml file that you can modify to do so. Nitrado's settings also has a box for you to enter in your Steam ID. Here's what mine looks like: Code: Elevated: - { Id: '00000000000000000', Permission: '9' } Insert your Steam ID where the 0's are. When in-game as an Admin, pull down the console (mine is the tilde ~ key) and type in "gopt". This shows you in-game all of the gameoptions.yaml settings. Changed settings should show up here.
Also, if you need more detail or have other Nitrado-specific issues (like the server not showing up in the game browser), check out my post on their forum. I was effin' livid, but happy to report that since late-July/early-August, I don't really have any of these issues anymore and it's been a smooth experience. Pure speculation but I think it has to do with some kind of "new server set up script" that trips the server up. Once a game update hits, the "update game script" takes over and is programmed correctly. It's likely why longtime Nitrado server hosts can't replicate the issue, and likely why their customer support looks at us new hosts as if we have 3 heads.
