setting up caves

[thegamedude221]

hi i have had  my dst server for a bit now but have been unable to get caves i have read several post about seating them up but i dont understand i find of of the way i see people showing how to do it confusing any help 

ps i have my basic dst already set up

[Daniel86268]

A cave on a dedicated DST server is basicially a second DST server running parallel to the overworld one. This way a DST server only has to manage one world and has a better performance than a server that would have to handle multiple worlds parallel. When entering a cave entrance the player file gets transferred to the other server.
To do this you basicially set up the shards (For clarification: a shard is a single world server by itself, a cluster is a combination of two or more shards connected to eachother) the way that they have the same master port (the port they communicate over to eachother), but different connection ports for the player connections.
Then you also add the line that changes the cave shard world gen to cave world as you've probably already read in tutorials in the worldgenoverride.lua.
If you start up both servers now they should find eachother after starting up and connect their portals (sink holes in the overworld, staircases in the caves) to eachother automaticially.

[thegamedude221]

2 minutes ago, Daniel86268 said:

Daniel86268 thank you this is very helpful im going to try it right now if i have any more issues il contact you if thats alright 

 

[thegamedude221]

Daniel86268  how do i set the start2.bat which is  the launcher for my caves how do i make it launch from diffrent location

 

[I Heart Popcorn]

Don't create another bat file.  Simply add another line to the existing bat file.  Copy the same start command line but change the "-shard Master" to "-shard FOLDERNAME" where FOLDERNAME is the new location of the cave shard.

[Daniel86268]

What I usually do is create two script files to launch the servers seperately. This has the major advantage that you can monitor them independantly of eachother. To each their own I'd say. If you want to monitor everything, track down errors, and check if stuff is still running do seperate startup scripts. If you don't care about all of that and instead just want to run everything as easy as possible go for a single file. To do either of this you basicially copy your normal startup string and modify it just like I Heart Popcorn described and either pack it into a seperate file so it looks just like your main one with the one modification, or add it to your main one to start up both with one script.