Oh my gosh, we went to a new planet to try and build a base, a place where we've placed zero bases, ships, or blocks of any sort (we've only mined there) and we are getting the same error message. We can't even place a base starter on a brand new planet! If anyone has any other ideas to help with this, I'd greatly appreciate it. This is proving to be a huge problem.
I'd be more that happy to jump on teamspeak this evening after probably after 8PM eastern time if that helps. Shoot me a PM on the forum if you like.
I appreciate that. I've put in a ticket with Nitrado, but if (more likely when) they prove to be no help, I will reach out to you. Thanks
Update: I was able to fix the problem by putting 0 in the value for MaxStructures. Something very glitched is going on there, if upping it from 64 to 100 didn't work, and even up to 700 and 999 with no luck. Only luck was putting it to zero.
Well, we are running a Project Eden Server with 1000 max so not sure what you have going on. Likely the hosting.
I have had a lot of people mention problems with the max structure count or POIs disappearing on Nitrado servers (but not exclusive to them either). Alpha 12 is changing a lot though so maybe it will work better then.
Update: So I'm not convinced the MaxStructures setting to 0 worked at all, I think it just bugged out and let us build once. Pretty sure we found the actual fix to this: We ended up moving the server to our own physical server, going away from Nitrado, and found that the actual setting is in a different file: gameoptions.yaml In there is where the server reads MaxStructures. dedicated.yaml doesn't seem to do anything with MaxStructures Warning: Setting MaxStructures to zero will start deleting a bunch of your stuff - DON'T EVER DO IT! We had a bunch of portable constructors and auto miners just disappear once getting near them. We set the MaxStructures to 500 in gameoptions.yaml and everything worked exactly as expected (and right before joining the server, when viewing the server info, it displayed MaxStructures correctly as well). Case closed, here!
I've recently rented an empyrion server. I am still learning about the settings and I've been having a problem with the poi's. The core of the poi's can't be damaged. Is there a setting in the dedicated_config.yaml or the gameoptions.yaml file to enable the players to destroy the faction core on the poi's?
This can be fixed by disabling POI regeneration in game options *or* removing the POI's RegenAfter property. This isn't something particularly relevant to EAH, consider reading the example gameoptions.yaml file for more info.
I'm having some issues with getting EAH Lite to work with Host Havoc. Everything seems set up correctly (I followed their KB article), and Refresh from FTP says it was successful, but the power button is stubbornly red. I check the log file multiple times - it appears that whenever I click the button, this is generated: Code: 07.06.2020 18:49:22.887 I Telnet Connect: Port emtpy I've verified that my dedicated.yaml does have a port listed for Tel_Port and that Tel_Enabled=true, but when I check EAH's Config/Settings.xml, it doesn't appear to be picking it up. Not sure if that's the driving issue, but it's the only one I'm seeing. Any help is greatly appreciated, thanks!
Hey, did you select the right dedicated.yaml in the EAH config? You have to enter the name of the dedicated yaml file that you are using in the EAH config. Then click on FTP: REfresh. Any errors when doing so? Is the FTP path correct? I think wiht host havoc it should be just a "/" See here for some examples (Forum has also multiple Host Havoc posts): https://forum.empyrion-homeworld.net/t/eah-wont-regonize-yaml-files/15755/12
*facepalm* Apparently I glossed over the fact that HH uses "dedicated_config.yaml", not "dedicated.yaml". However, "dedicated.yaml" is present, so no file-not-find errors to tip me off. Power is green now, thank you.
Could use some help here.... Since A12 experimental I have not been able to set playfields / planets to PVE only. I have ZERO interest in pvp and I used to be able to set at least the starter planets to pve. I uncheck the option in the tool yet after restarting the tool and server, etc I have the same issue over and over. I am not sure this is a tool issue or a game setting that is causing me trouble but I would like to set everything to PVE at least for players. This is a Steam CMD server freshly installed again this evening. Suggestions on what I might be missing and do I have to set this manually?
Hello, Let me ask you for your help on creating admin rights on a personal server. Since the exp12 update I can't configure the admin of my server. Before I was going to create in the directory "Empyrion> Saves>" the file "adminconfig.yaml" to configure access with this command: Elevated: - Id: xxxxxxxxxxxxxxxxxxxxxxxxx (this is not a bp of ID) Permission: 9 but this method no longer seems to work Since exp 12 I does't also find a basic file "adminconfig.example.yaml", so maybe the method has evolved. If a server admin can bring me a solution. Thanks in advance
I need some help getting a dedicated server running. so far i have tried various ways to download the dedi files. steamcmd steam tool i have also tried using the EAH. and i have tried manual editing of the config files. i do have the ports open for tcp and udp in and out. Hardware is not an issue as i have a bare metal from OVH Canada. I am using windows server 2019. the system specs are listed in teh log file. network is 1 Gpbs in and out NVMe drives. only the dedicated icon shows up in the task manager no playfields show up. no matter what i do i get the same result. I will be grateful for any help offered.
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads x64: vc_redist.x64.exe Install that
So I was having the same issue and installed the VC redistributable and that got our server running. I shut it down and then tried to restart and now it won't fully restart. I even tried repairing the install of the VC file and it still is not working. Something is broken and I don't know what.
