Daniel86268

Client + Server mods are downloaded onto your client when you play on a server requiring said mod automaticially, because your client needs to have them as well. What you see in your screenshot is the server mod, which is deactivated until you actively activate it on a client hosted server. It won't cause issues, unless you activate it yourself in said way. If you wanna get rid of it, you can just delete the file (or Folder for that matter) on your hard drive, where your mods are saved.

If you delete your game, you don't have to buy it again. You just have to redownload it throught steam, which should be no issue unless you have REALLY crappy internet.

Looking at those specs the dedicated will probably run better, since it has mroe RAM, and more cores (2 physical vs 1), even though the cores themselves are clocked a bit lower. This will be more apparent on multishard servers (Overworld + Caves for example), since they have to run multiple worlds in parallel, so more cores + more RAM is what you want. Also you have the guaranteed performance at all times, so you have more of a constant reliable performance instead of potential performance drops during heavy load times. That being said, there might also be situations where your VPS will still perform better, for example if you need a high single core performance. (Heavy load spikes on a single shard, etc.) So as with most tech things, to answer your question: It depends. In general the performance will most likely be better on the dedicated one, but in other occasions it might be worse. You can always try it out. If the dedicated server is actually not really better after all, you can always go back to your VPS you had before. You might wanna look at Virtual Servers with dedicated cores, which many companies call "Root Servers". Essentially you'll have virtual cores of powerful processors for your server alone, and you aren't limited to weaker CPUs or lower amounts of RAM in case you decide to upgrade a bit. They usually are a bit more costly though, so always keep that in mind.

You have to create the file yourself. It's not there by default.

There are two things that come to my mind right now: 1. Does your brother have any mods installed? And which mods do you have on your server? They might conflict eachother while changing from overworld to caves. 2. Maybe the firewall on your Brother's PC is blocking the cave port, and therefore not letting him connect to the cave server. Try disabling the Firewall temporarily. (And enable it again after the tests, and if those tests turned out to be successful, open said port/service in that firewall.)

It kinda seems like something is not quite working with the sound part of the game. Try disabling "wegame" or whatever that is. Maybe it's not compatible with DST. (I'm running DST on W10 64bit as well without issues, so that's the only thing coming to my mind immediately.)

Check the VPS' and your system firewall settings. (Check if you still can't connect if you disabled both firewalls for testing purporses) If that works, you can open up the ports designated on your server on your server's, or both firewalls. What kind of network is the VPS running on, and on what kind of network is your PC? On a rented gaming VPS there shouldn't be a dedicated firewall set up blocking the gameserver, but in other cases, or if you host it yourself it might be worth checking if there is a firewall somewhere, that might block traffic. A private internet connection should be fine as well, but if it's for example a University network, they might be blocking things as well.

In about 95% in all cases when this error happens you copied the cluster_token.txt's content into the one on your server, which usually fails, since it also has controlsymbols such as spaces and <enter> symbols, especially at the beginning or the end, that sometimes get ignored during the copy process. Copy the entire file instead. If it'd say "token not found" it'd be in the wrong location, or the startup script has the wrong cluster locations, which isn't the case here.

Do you have any mods installed? And have you tried fresh maps? I know DST has been a little choppy at times, especially on older maps, but not that heavy drops.

You can also use screen -rx to reattach one screen session to your console again. This is useful if you want to just shut down all servers by reattaching and shutting them down after another without needing to reattach the sessions using their names individually, or if you only have a single screen session in the first place (Single world DST servers, or other game servers).

Do you have any mods installed? Does your friend have any mods installed?

I like to explore the map outlines (All edges, so I know what the map layout is, and I know where most things are) and decide for a nice base spot before the first winter hits. Needless to say lantern the earlier the better. Get ready for deerclobs... what was it, day 30? I think it was. Summer base in the caves equipped with the essentials before the first summer hits. Everything else just as I go, or feel like it.

After switching from OpenSuse to Manjaro as server OS the server just exits right after launch. It launches up quite fine, all configurations should be correct as well, since they worked on my old server. Unless there is a known fix, can a dev look into that? Note: The mods are downloaded and checked, but I deleted the modoverrides.lua, so all mods are disabled. This System is the as of now latest stable version of Manjaro linux (17.1.6), running on a virtual machine with 8gb of RAM, 4 CPU cores and 50gb of hard drive space. Edit: I did a bit more research, and found out that I got a segfault as listed in the systemjournal. Added the log as Systemjournal.txt as well. Hope this helps tracking down the issue. Edit2: According to the Journal I fiddled around a bit with the DSTServer/bin/lib32/steamclient.so file, and it seems deleting or renaming it/making it unreadable to the server allows the server to start properly. [00:00:11]: [Shard] Starting master server [00:00:11]: [Shard] Shard server started on port: 10894 [00:00:11]: Telling Client our new session identifier: 6CE27EBBC642FDE4 [00:00:11]: ModIndex: Load sequence finished successfully. [00:00:12]: Reset() returning [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10894) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10895) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10896) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10897) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10898) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10899) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10900) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10901) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10902) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10903) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so with error: steamclient.so: cannot open shared object file: No such file or directory [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Warning] SteamGameServer_Init failed [00:00:12]: Your server will still start, but some Steam functionality may be missing. [00:00:12]: Steam ports can be configured through command line by adding: [00:00:12]: -steam_authentication_port 12345 -steam_master_server_port 12346 [00:00:12]: or through settings.ini, under the [network] heading [00:00:12]: steam_authentication_port = 12345 [00:00:12]: steam_master_server_port = 12346 [00:00:12]: Auth port: 8768 Master server port: 10894 [00:00:12]: Validating portal[9] <-> <nil>[9] (inactive) [00:00:12]: Validating portal[10] <-> <nil>[10] (inactive) [00:00:12]: Validating portal[5] <-> <nil>[5] (inactive) [00:00:12]: Validating portal[1] <-> <nil>[1] (inactive) [00:00:12]: Validating portal[8] <-> <nil>[8] (inactive) [00:00:12]: Validating portal[6] <-> <nil>[6] (inactive) [00:00:12]: Validating portal[3] <-> <nil>[3] (inactive) [00:00:12]: Validating portal[2] <-> <nil>[2] (inactive) [00:00:12]: Validating portal[4] <-> <nil>[4] (inactive) [00:00:12]: Validating portal[7] <-> <nil>[7] (inactive) [00:00:12]: Sim paused Plainly copying the steamclient.so file from the steamcmd folder doesn't work either, it says [S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so. [00:00:12]: [Steam] SteamGameServer_Init(8768, 25574, 10903) [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. dlopen failed trying to load: steamclient.so From my testing the missing steam connectivity prevents the server from getting listed in the server lists. Direct connections over the console still work though. I hope this helps tracking down the issue and hopefully fixing it. Edit3: After even more fiddling around I managed to get it working by linking the steamclient.so file from the linux32 folder into the DST server folder to where the other steamclient.so file was. This bug can be closed and hopefully eventually fixed for everyone, maybe by using the steamcmd one if available, so it's compatible with other Linux Distributions as well. Systemjournal.txt

No, it's not related to any server location, because: Yes, outside of events you only get the usual single item. These event chests aren't the usual drops, they are event drops, only dropping during events instead of common or classy items.

Yes. Settings like max player count, etc. you can obviously set in your server.ini and cluster.ini files on a dedicated server. Worldgen settings like disease, etc you can set using the command TheWorld.topology.overrides.<game option> = "<setting>" You can find the list of game options here: For example the command to disable disease on plants looks like this: TheWorld.topology.overrides.disease_delay = "none" Keep in mind that some settings don't affect the world, such as "world_size", "branching" or "loop", since those ones are only active during the world generation. Edit: When using the command to change the settings make sure to check if the Infamous "Remote: " is still in front of your console, since it gets disabled when pasting commands in. Press <ctrl> to enable it again.