We’re patching tomorrow morning (March 13) for a couple fixes. at 10:00 AM EDT / 14:00 UTC. Downtime ETA is 2 hours. We are not raising the level cap with this patch.

Time Zone Converter

Hi there @Mrsmoov! Sorry to hear you’re having billing issues. We are not able to directly assist you with billing and money issues on the forums here, but I can confirm your ticket has been received and will be addressed as quickly as possible. We’ve been slammed with requests recently so wait times are longer than anyone would like.

We appreciate your patience and understanding while we work to get to your ticket. In the meantime, however, we must remind you to not fight with other users and mind our ...

Just for the sake of testing, you can just put “http://test” (or whatever really) and check Enable in the Discord tab, then after clicking Check you will see the result in the server launcher logs:

C:\DedicatedServerLauncher\Logs\DedicatedServerLauncher(1.0.29).2019.03.12 19.55.39-0370.txt

[2019-03-12 19:58:44.527] [TID:15892] DATAERROR: DedicatedServerLauncher - SendDiscordWebhookMessage: Failed sending the message 'Checking t...

Ok, if you want to give a shot:

Dedicated Server Launcher 1.0.29

• The MaxPlayers parameter is now passed on the command line, should help keep it sticky
• First pass implementation of the mod update check

The “check” button is on the top, at the right of “Don’t auto-update Server and Mods” and the information is displayed on the Discord webhook (It’s temporary, but that was practical to test).

What I could do, is to release a test version that does not do the restart, but has a “Check” button that allows you to check your mods toward the Steam Workshop releases.

That would be an easy way to start verifying if my check code is working as expected.

In my current test case, I have the following mods installed: 860241645,880454836,1382120864,1386650198,1422434062

Only Pipi was up to date, when I pressed my Check button I got that:

As you can see, Pippi was not flagged as out of date, and 1422434062 has a quest...

Please let us know if this issue still happens in an unmodded game.

It seems that this issue could be caused by some mod, as other people have reported.
We tried to reproduce this issue internally and elevators looked fine on our end.

It’s in the new version, 1.0.28 has not changed.

What you mean by ‘force installing old version’? If a server add a new mod it is installed automatic when restart.

It’s for development purpose: I need to be able to revert to an older version to make sure my tool detect new versions… when I’m all “up to date” it’s getting difficult to test.

Hey @Palm522

Which server was this happening on? (sorry if you mentioned it before, my memory can be a little fuzzy these days)

Hey there,

It is unlikely that the patch will hit consoles this week. We’re trying to squeeze in the server and building optimizations (as well as for PC) as it would potentially improve performance significantly.
Once we have an estimate date we can confidently assure the patch will be out, we will let you all know.
Thanks for your patience and support.

Merging thread with a similar issue into this one.
@Scuga, is the server you’re playing on modded?

Hey @Nomad3894

We’re aware of that issue and a fix for it will come bundled in the upcoming parity patch.
Please keep this thread for performance issues only (framerate, stuttering and so on)

Hey there @MediocerSpeller (nice username)

We fixed this issue internally and should be included in the upcoming parity patch that will be released on consoles.
Thanks for your feedback

Hey there @R3DPhantom

Have you tried some of the solutions we have in this thread?

Hey @Ava

Could you please create a thread for each bug so we can track each report more easily?

There you go!
1.0.28 is now the official version

And a small sneakpeak of the new version:

It’s getting there.

N...

Hey @ManiacalOwl

We’re sorry you’re experiencing issues while trying to connect. Could you clarify which box is the one checked initially?

Hey there,

Our team is aware of this issue and is trying to find a way to fix it. Until then, some users reported a temporary workaround if it happens around their base, which is to put all your stuff in a nearby chest and remove your bracelet. It’s not an ideal workaround, but until we release a fix for this it can be less aggravating than dealing with this issue.