Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
I had NO TROUBLE, (really) getting Valheim and V-Rising servers to run on this machine recently... still can. But Enshrouded is not properly connecting.
ping 9,223,372,036,854 ms
It's not even a REAL ping time. Assuming this is a server error for something, but no one knows. I have an excellent machine to run the server, and on ethernet with 500 mbit Fiber with zero ping issues to anything outside of this server.
I found that the file "enshrouded_server.json" had changed, but that change was not automatically downloaded by Steam. So I backed up the Enshrouded server, then uninstalled then reinstalled the server files.
One major change was the ability to modify the difficulty settings. The other was to add a new section "userGroups". It has 3 types of groups. Admin, Friend, and Guest with varying permissions, such as an Admin "canKickBan", access inventories, edit base, extend base, etc., whereas the other two types have fewer permissions.
At the very bottom of each section is "reservedSlots":0
I had to change that to something greater than zero to be able to access the dedicated server. The *.json file has some randomly generated passwords as defaults to prevent other people from griefing your server until you had an opportunity to change them. My guess is that the passwords used to log in determines the level of permissions a player has.
I also had to do what Xyeth said - run the server as an administrator.
I also found that running the server made my PC's fans run louder than I've ever heard them. but the same PC could run several Ark clustered servers simultaneously.
Windows Task Manager reported high power usage, but each of the devices were barely loaded.
Then today I found that I can't connect to the dedicated server again. I'll wait and deal with this after Christmas.
I found on reddit a solution that worked for me.
Using SteamCMD, a separate steam program...
Launch SteamCMD.exe
It will open a command prompt window. In it, type (copy paste) :
force_install_dir enshrouded_server
(This will create a folder in your SteamCMD directory for the server. You can change this to anywhere else but for ease I put it here)
Then, type(copy/paste) :
login anonymous
Then, type(copy/paste) :
app_update 2278520 validate
close when done.
This will download the server files outside of steam. Edit the json file to change the name and passwords... Then launching enshrouded_server as administrator, usually makes the server appear in the server list in game (it sometimes work without admin. but not always).
I don't know why this works better than launching through steam.
It's seriously weird how I never had any issues with dedicated servers on other games, yet this one is a headache every time. Even when no updates were pushed, sometimes the server just refuses to appear in the list.
Sometimes I still have to essentially delete everything except the savegame folder and redo the previous steps to get the server files again. Other times I have to change the name of the server. Or even backup my savegame and recreate a new world before closing the server and putting the old files back. Other times I have to reboot the PC and somehow this can help fix it as well.
And, unless you are time travelers, I doubt anyone could have waited that long.
Time travelers confirmed?
I'm now getting the same ping. What's really odd is that I got the server working on Dec. 23, but the next day, it would no longer work. This means that everything was set up properly on my end, but it would not work the next day. I had not changed anything.
I am now in the process of trying to move the server saved file to my local files.