Jump to content

7 Days To Die (Experimental)


Recommended Posts

7 Days To Die (Experimental)


  1. Download the config
  2. Go to TCAdmin > System > Settings > Game & Voice Hosting > Game & Other Voice Servers > Import
  3. Save the config as a new config or chose "Overwrite existing config" if you which to overwrite your current 7 Days to Die Experimental config. Remember to select 7 Days to Die Experimental in the 'Update Game' field if you do
  4. Leave all other settings


  • Shut down properly using custom script with rcon commands
  • Support for A20 Experimental
  • Support for Alloc's Server Fixes (easy install)
  • Support for "Darkness Falls: They mostly come out at night..." (easy install)
  • Configuration files are 100% configurable using Configuration Editor
  • Easy backup of worlds and configuration files

If you want any mods added, let me know. I'll see what I can do.

Switch between versions

Alpha config is available from here:

To switch between Alpha and Experimental, you should enable Game Switching: https://help.tcadmin.com/Manage_Game_%26_Voice_Services#Game_Switching

Once this has been enabled, you can switch between the versions. Please note that your server will be completely wiped when doing this.


Link to comment
Share on other sites

  • 3 months later...

What's New in Version 1.0.2  

This update only fixes issues for the Linux config.

  • [Fixed] "Relative Executable" was not set
  • [Fixed] "Files Folder Name" was not set
  • [Fixed] "Default Commandline" was not specifying the correct path to the logfile
    • This also fixes web console not working
Link to comment
Share on other sites

  • 1 month later...
  • 1 year later...

Hey Mr Dennis


Once again thanks for your config files, since the new release today, the way the configs setup looks changed once again...

<!-- Admin interfaces -->
    <property name="ControlPanelEnabled"            value="![ControlpanelEnabled]"/>                <!-- Enable/Disable the web control panel -->
    <property name="ControlPanelPort"                value="$[Service.CustomPort1]"/>                <!-- Port of the control panel webpage -->
    <property name="ControlPanelPassword"            value="![ControlPanelPassword]"/>            <!-- Password to gain entry to the control panel -->

Needs to be deleted or it wont start up, havent compared it to the new setup but yeah I can confirm you need to delete those 3 lines for a server to boot, I assume once it goes stable, your normal configs also will cause server crash 🙂

Link to comment
Share on other sites

looking at a default config file, seems they decided to call it "webdashboard"


<!-- Admin interfaces -->
    <property name="WebDashboardEnabled"            value="false"/>                <!-- Enable/disable the web dashboard -->
    <property name="WebDashboardPort"                value="8080"/>                <!-- Port of the web dashboard -->
    <property name="WebDashboardUrl"                value=""/>                    <!-- External URL to the web dashboard if not just using the public IP of the server, e.g. if the web dashboard is behind a reverse proxy. Needs to be the full URL, like "https://domainOfReverseProxy.tld:1234/". Can be left empty if directly using the public IP and dashboard port -->
    <property name="EnableMapRendering"                value="false"/>                <!-- Enable/disable rendering of the map to tile images while exploring it. This is used e.g. by the web dashboard to display a view of the map. -->

    <property name="TelnetEnabled"                    value="true"/>                <!-- Enable/Disable the telnet -->
    <property name="TelnetPort"                        value="8081"/>                <!-- Port of the telnet server -->
    <property name="TelnetPassword"                    value=""/>                    <!-- Password to gain entry to telnet interface. If no password is set the server will only listen on the local loopback interface -->
    <property name="TelnetFailedLoginLimit"            value="10"/>                <!-- After this many wrong passwords from a single remote client the client will be blocked from connecting to the Telnet interface -->
    <property name="TelnetFailedLoginsBlocktime"    value="10"/>                <!-- How long will the block persist (in seconds) -->


Hope this helps you 🙂

Link to comment
Share on other sites

  • 3 weeks later...

What's New in Version 1.1.0  

Support for A21

  • [Removed] Obsolete variables for the configuration file
  • [Added] New variables for the configuration file
  • [Changed] Web console now prints response from rcon commands
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Who's Online   0 Members, 0 Anonymous, 20 Guests (See full list)

    • There are no registered users currently online
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use