search

arkmanager / ark-server-tools

Set of server tools used to manage ARK: Survival Evolved servers on Linux
MIT License
678 stars 143 forks source link

Problem with using instance unique configuration (ini) files #1203

Open paytah232 opened 2 years ago

paytah232 commented 2 years ago

Hi there,

I seem to be having trouble ensuring that certain instances have their own custom ini. I believe I read the docs and understood that by naming the ini a particular way, and storing it in the same path at the instance .cfg file, that it would just work. From here: image Have I understood correctly the naming convention here? That the ini file goes in the same root folder where the cfg is, and is name instancename?

It doesn't appear to work currently, as the config that is being used is a general config set by me, and not the custom ini.

Can someone help me make sure I've set it up correctly please?

Before I launch the instance, I make sure that the files on the system are at least my general config: image

I then start the instance (using this program) and expect that the ini will be copied, and it reports that it worked: image

However this ini files are still incorrect. I know this because my general ini has a server message, whereas the custom ini does not.

This is where my instance file and custom inis are stored (the inis are exactly the same here, but different names as a test - neither work anyway). image

And this is the line in my arkmanager that calls this instance: image

For clarity, I will also upload my arkmanager.cfg and thenewinstance.cfg cfg.zip

Here are the custom ini files as well: thenewisland-ini.zip

klightspeed commented 2 years ago

Are you running only a single server from /ark/servers/ARK, or multiple servers each with their own custom ini?

If you are running multiple servers from a single directory, and each one has its own custom ini, then each new server that starts will clobber the Game.ini and GameUserSettings.ini files in /ark/servers/ARK/ShooterGame/Saved/Config/LinuxServer

Since you are using a staging directory, please make sure that there are no stray files in /home/steam/ARK-Staging/ShooterGame/Saved (or that it does not exist).

paytah232 commented 2 years ago

@klightspeed Thanks for the prompt reply!

I normally only run 1 server at a time, but I have the multiple instances set up to change game states/maps etc. If I did want to start 2 at once, I'm assuming I would have to copy the Ark directory and change arkserverroot="/ark/servers/ARK" -> arkserverroot="/ark/servers/ARK-2" and then place that line in the instance to override the arkmanager.cfg server root location?

It seems I have the staging directory set, but it is empty. image

Which naming convention that I used for the ini files stored in the same path as the instance.cfg is correct?

As a side note, I am also finding that the server is not reporting that it 'is up'. I get the waking up message, but it never says ready to rock and roll, even though the server indeed goes live. (should we discuss here or should I raise a separate issue?) image

paytah232 commented 2 years ago

@klightspeed Any ideas?

I also tried multiple servers (using different server roots), only the first started server can be connected to. Both of them and up listening, but only 1 can ever be logged in to. They both work separately of each other.

klightspeed commented 2 years ago

Are you giving each instance its own Game / Query / RCON ports?

paytah232 commented 2 years ago

Yep. Unique ports. All forwarded. All open. Plus 1 port up for each just in case, and just never allows a connection.

Anything on why the custom game inis wouldn't be working as well?