Toolguy

No, there’s no API, but if you need to restart every three hours, you can just play with the “Automatic Restart” options in the center of the UI, with for example “Restarts per day” set to 8 (24 hours divided by 3 hours = 8 restarts).

Which type of API were you thinking of?

Nope, that’s part of the original design: Each Launcher is 100% in charge of managing (installing, updating, …) the entire server content, but migrating an existing server is simple (copy paste basically)

Or at least choose install folder location?

That is already supported.
By default the server folder is installed just under where the launcher is running from, but you can use a command line parameter to change the place where the server data is located:

DedicatedServerLauncher.exe -basefolder D:\MyServer\ConanServer1

That being said, it’s an option I added for development purpose so I can have my Visual Studio compiled ...

Are you running a modded server?
There was a Exiles patch released yesterday for PC around noon (UTC), and for chicken and egg problems, mods are generally not yet ready to work with the new version and they often fail.
Could that be this?

Ha, yeah it’s a known iss...

Svenska och norska har inte många skillnader

The trick is to enable the “Launch program on login” option (Preferences menu), that will make the Dedicated Server Launcher to automatically start when you reboot your pc, and then if you have checked “Start server if not running” (Automatic Restart box) the server will automatically get started.

Just for information, does it happen that the server name disappears when someone is modifying server settings in the game, or does that happen randomly?

What are the errors you get? (You can generally just CTRL+C on a Windows standard error dialog to copy the message)

This in general seem to happen when the attempt at connecting times out: Basically there’s some kind of back and forth between the client and the server to validate the authenticity, list of mods, version of the game, etc… and if all that does not complete in some amount of time, then the whole thing fail.

Known issues have been servers running super slow (because of a weak machine or too many people playing on it, slow hard drive, etc…) network issues (on the server or client side), firewall problems, routing issues with the player connection going through crazy paths (can be checked with “trace route” tools), etc…

The easiest way to diagnose if it’s client or server side, is to try to get other people to connect to the serve...

Not appearing in the Server Browser and Steam? That’s a know issue, it will be fixed for the next games, but for Exiles there would be way too many things to change for this to be safe.

What I recommend is to setup a Discord webhook, with a “Ready” message set to something like “The gates to {servername} are now open, please join us on {steamconnect}”, as soon as your server is ready, Discord will receive a message with a clickable link, people just need to click on it to direct connect to your server with the correct password.

The issue was signaled before Christmas, try to use version 1.0.39 and see if that helps.
I unfortunately did not have the time to do any work on the launcher, there’s been a lot of things I had to help with.

@Yipman can you confirm that it is fixed for you as well?

There’s not much you can do for that one, I’ve seen it happening now and then, even on my own server when doing tests, that seem to be highly dependent on internet topology, time of the day, weather, active volcanoes and if some butterfly was flying around…

tl;dr: It’s just a minor feature used to rank servers, see when they are active, etc… it’s not something that has effects in practice when it does not work.

Now, regarding the ability to join I would suggest two things:

• Use the discord webhook feature, it really helps making 100% certain that the server is up and running, and with an impossible to misuse “click here to connect” link to the ser...

Technically it’s not a Launcher issue, it’s probably something you should signal in one of the support forums (I guess “server stuck when shutting down” or something like that).

I guess on my side, I could probably add some kind of option to “force kill” the server process if it is still running after some specified amount of time, but that comes with serious risks of corrupting the data.

@Fritzli and @Yipman could you both click on the [?] button at the right of the Auto-Check combo sele...

I’ll be back at work tomorrow, I did a quick check on the messages, and apparently the issues to fix are:

• The check for update started failing on the first day of 2020
• The broken restart signaled since version 1.0.40

is there anything else I missed?

And to everybody: Happy new year, and sorry for the bug, I’ll try to see what happened!

This is this time of the year again, so let see a summary of what happened in the Dedicated Server Launcher in 2019.

We left 2018 with version 1.0.24 and we are now at version 1.0.44, so that’s another 20 releases this year alone (most of them being the struggle to get the mod update right!).

The big feature was the ability to check for updates of both the server and mods. This took quite some time and required many of you sending me logs and other details.

1.0.24 to 1.044 update1301×1552 358 KB

So 2019 changes in details:

• I...

I wonder if that could be a side effect of that change.

// 1.0.40:
// - Fixed the ModUpdate check to not trigger if the auto-restart has already displayed the first warning message

Could you try 1.0.40 and tell me if that still work? Basically trying to find out which version actually broke the feature.

The server part of the update system (server version, installed mods) is handled by the Dedicated Server Launcher tool, but the client side is normally a normal feature of the game itself: Basically when a client connects there is a negotiation between the client and the server to see if they have matching mods, and if not, then the client updates and retries - the launcher is not involved in this part at all.

That being said, you can try to use 1.0.39 again, but that would probably still do the same thing, if it does not, then there’s something fishy going on!

Is there anyone else having client side updates not working as expected?

Question for all of you people: Did you easily find the Dedicated Server Launcher when you were looking for how to manage your own servers, or do you think it should be more prominently placed (and if yes, where).

Bonus question: If you tried the launcher but eventually reverted to using something else, what was the main reason? (bug, missing feature, ease of use, etc…)?

I guess these few last answers clearly show the issue:

On one hand we have @Ashenda, @Rhomara and @drachenfeles who just did open the ports, making sure they were different for the client and server, and it worked out of the box.

On the other hand we have ...