Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

7 Days To Die integration is BAD

  • Last Post 10 May 2020
  • Topic Is Solved
SpencerXZX posted this 23 May 2019

As the title says,

I am very disappointed in the way AMP integrates with 7 days to die. It's been a buggy experience from the start. After starting the server, a lot of times it seems like it doesn't find the process so it just sits there and displays "Abort" instead of Restart/Stop even though the server is up and running.

On the occasion that it does find the process, it shows Restart/Stop, however neither button works. I hit it, and then the "Kill" button shows up but my server never stops. I have to Kill it to stop it every time, no matter how long I wait.

Beyond all that, I am trying to use a custom port for the gameserver to listen on (24905), however if I reboot AMP, it's like my server config didn't save and it reverts the server back to 27015.

Mod support is out of the question, you have to jump through hoops to get it to work, I'm not even going to try. Which then also means you can't run Alloc's server fixes, which brings me to my next complaint of not being able to turn off the console. I like to manage my server from the Telnet console, however with no Alloc's and no way to disable AMP from automatically connecting to the telnet server, I'm unable to connect due to the limitation of one telnet connection at a time. The telnet in the console is not working for me either, I was able to execute a few commands but now when I try, I type it in and hit enter, nothing happens.. Great.

I think I'll go back to hosting using Linux scripts, this was a waste of money and I am displeased to put it nicely. Please fix your issues before releasing a paid product.

Order By: Standard | Newest | Votes
Mike posted this 24 May 2019

AMP actually starts the server, so there's no need for it to 'find' anything, but your description is very vague so I'm not entirely sure what the issue is. You'd need to put AMP into debug mode and check the logs.

For the ports you have to remap the port in ADS or it'll be reset on the next instance start. The port settings are going to disappear from within the individual instances soon. When using ADS it becomes the authority on all network usage within AMP.

You can use the ampinstmgr viewcommand to get a live console for a given instance. AMP will always be in charge of the telnet because it can't do its job otherwise, but you can use the rcon passthru mode to access it anyway despite this (and in a more secure manner)

Gandor posted this 30 May 2019

7dtd is broken in AMP. AMP writes "GameMode" value="0" instead of GameMode" value="GameModeSurvival" in the serverconfig.xml this breaks the game. There are also several option missing from the serverconfig.xml

Mike posted this 30 May 2019

I've sorted out the wrong value being written out for the GameMode, which settings are missing? The wiki page for the server config appears to be very outdated.

hollykeks posted this 31 May 2019

Hello! I'm using this thread since I've got some problems with 7Days as well. I updated it and to be sure changed the GameMode value manually as mentioned by Gandor. My problem is that after a while the game seems to desync for all players. This is (as far as i know) a known issue for a very long time but only happens if a lot of players are present and in the past only happend to players not connected through LAN. Since I switched to AMP it even happens to my wife and me playing locally, which gets pretty annoying having to kill the server every ~30minutes and losing a bunch of items. I absolutely love AMP and it is entirely possible that it isn't AMPs fault. Any ideas how I would go about narrowing the issue down? Thank you very much!

Gandor posted this 31 May 2019

Missing properties and there default values there are more but these are the important ones thats i have found

"BedrollDeadZoneSize" value="15"

"BloodMoonEnemyCount" value="8"

"PlayerKillingMode" value="3"

"LandClaimCount" value="1"

"ServerAdminSlots" "value="0"

"ServerAdminSlotsPermission" value="0"

"ServerReservedSlots" value="0"/>

"ServerReservedSlotsPermission" value="100"

"ServerLoginConfirmationText" value=""

"ServerDisabledNetworkProtocols" value="SteamNetworking"

"UserDataFolder" value=""

"BlockDamagePlayer" value="25"

Mike posted this 31 May 2019

There's been an update in Nightly which will have most of the new settings in (as applicable to AMP)

Gandor posted this 31 May 2019

Awesome, Thanks Mike

Gandor posted this 01 June 2019

Testing it now I'm not sure how it gonna work

The GameMode value is set to GameModeSurvivalMP insted of GameModeSurvival

ServerLoginConfirmationText value needs to be a multi line input box. There also needs to be an option to turn it on and off

also on the Server Config page in AMP you have heading "Server Reserved Slots Permission" in there twice The second one should be for ServerLoginConfirmationText

Gandor posted this 01 June 2019

Confirmed GameModeSurvivalMP does not work server still stops responding after a short time The value must be GameModeSurvival and correct me if I'm wrong but as far as I know GameModeSurvival is the only valid value for a dedicated server. Therefore there isnt any reason to have GameMode as a selectable option in the AMP config

Mike posted this 01 June 2019

Is there any up to date documentation for this? I'm going by the wiki page for 7d and it seems very outdated.

Gandor posted this 01 June 2019

I have no idea I'm going by the stock serverconfig.xml in a17 it gives a good discription of all the options and their values

hollykeks posted this 05 June 2019

So I downloaded the latest Nightly with the GameModevariable fixed but the server still stops responding after a while :/ I also downloaded another serversolution and tested it on the same machine (VM Ubuntu 18.04) which runs flawless for hours. Can you confirm this @Gandor?

Mike posted this 05 June 2019

If there's any difference in behaviour it'll be down to either configuration or startup arguments. Those aside it'll behave the exact same way regardless of how it's started.

Mike posted this 05 June 2019

This isn't an AMP issue if the server is crashing, its a common issue with the 7d2d server :

green112012 posted this 10 May 2020

Not sure if I should just add to this thread or make a new one as there is only one thread for 7 days to die it seems.

The amp installation is on windows 10 1903 1832.778

Amp version is AMP Release "Lapetus" v1.9.9.2, built 01/05/2020 17:15

I have everything setup to my knowledge but I can't connect to the server from steam at all. I have all of the ports forwarded on my router that are managed by amp for this instance. I can see the server started in the console but I can't connect to the server when I want to play on it.

Mike posted this 10 May 2020

Can you connect when you do it directly by IP address? Have you created the appropriate firewall rules? Really this should be a new post since the original thread is nearly a year old.

green112012 posted this 10 May 2020

No I couldn't get in by direct IP either. I'll double check the firewall rules and make a new thread if I have an update for it.