escapingnetwork / core-keeper-dedicated

Dockerfile for automated build of a Core Keeper Dedicated Server
https://hub.docker.com/r/escaping/core-keeper-dedicated
MIT License
97 stars 26 forks source link

Cant find "DedicatedServer" anywhere #50

Closed SuperNov4DZN closed 1 week ago

SuperNov4DZN commented 1 week ago

Hi, I used docker-compose to create a server using the image provided here and after some trouble with permissions (running with wrong user) I was able to get the server up and running, I can connect fine and play fine.. the only problem is there I cant find the "config folder" anywhere, it looks like the server isnt even creating it, the folders that I have right now (inside of server-files) are the following:

image

"server-data" has nothing in it.

can anyone help me with that?

SuperNov4DZN commented 1 week ago

This is my core.env file right now:

WORLD_INDEX=0
WORLD_NAME=Core Keeper Server
WORLD_SEED=0
WORLD_MODE=0
GAME_ID=(I've set the game id to something 29 chars long)
DATA_PATH=
MAX_PLAYERS=10
DISCORD=1
DISCORD_HOOK=(myhook was here)
SEASON=-1
SERVER_IP=
SERVER_PORT=
Micke90s commented 1 week ago

Hi, I just looked on my running container:

image

There are the two main folders core-keeper-data and core-keeper-dedicated

I think the file you are looking for should be ~/core-keeper-data/ServerConfig.json

SuperNov4DZN commented 1 week ago

Uhm, this is inside the container, right? But wasn't it supposed to be "accessible" via the folder "Server-Data" that I created "locally" ? My folder structure is:

~/corekeeper_server/server-files ~/corekeeper_server/server-data ~/corekeeper_server/core.env ~/corekeeper_server/docker-compose.yml

Inside of docker-compose.yml I've set the volumes to:

- ~/corekeeper_server/server-files:/home/steam/core-keeper-dedicated
- ~/corekeeper_server/server-data:/home/steam/core-keeper-data

By doing that I thought my server config files would go to my server-data, the server-files work just like that, have I done something wrong?

SuperNov4DZN commented 1 week ago

Another strange thing, just looked at what was inside my container and I have nothing under core-keeper-data

Screenshot_20240906-094625_1.jpg

Micke90s commented 1 week ago

Could you please try to set the line DATA_PATH= from your core.env to DATA_PATH=/home/steam/core-keeper-data.

Update: Should already be fixed with #28 - Fix may only work if environment variable is not present. 🤔 Could be the problem.

Your save games should be available under /home/steam/.config/Pugstorm/Core Keeper/DedicatedServer within the container.

Makerblaker commented 1 week ago

I am facing the same issue. Anytime the container is restarted, all data is lost. It looks to be saving the data in

~/core-keeper-dedicated/CoreKeeperServer_Data
Screenshot 2024-09-06 at 9 40 44 AM
SuperNov4DZN commented 1 week ago

Could you please try to set the line DATA_PATH= from your core.env to DATA_PATH=/home/steam/core-keeper-data.

Update: Should already be fixed with #28 - Fix may only work if environment variable is not present. 🤔 Could be the problem.

Your save games should be available under /home/steam/.config/Pugstorm/Core Keeper/DedicatedServer within the container.

Uhmmm, got it.. I'll make a backup of this folder (since I already played in the server for almost 2 hours), set the env path and try again, question, do I need to build the whole thing again running docker-compose up or just restarting the container is enough?

Makerblaker commented 1 week ago

I set the DATA_PATH= in the env file, and it seems to work now.

-batchmode -logfile CoreKeeperServerLog.txt -world 0 -worldname Purple Drop Server -worldseed 0 -worldmode 0 -datapath /home/steam/core-keeper-data -maxplayers 10 -season -1
SuperNov4DZN commented 1 week ago

I set the DATA_PATH= in the env file, and it seems to work now.

-batchmode -logfile CoreKeeperServerLog.txt -world 0 -worldname Purple Drop Server -worldseed 0 -worldmode 0 -datapath /home/steam/core-keeper-data -maxplayers 10 -season -1

Okay, so, no need to compose again? Just a simple restart is enough?

Makerblaker commented 1 week ago

I set the DATA_PATH= in the env file, and it seems to work now.

-batchmode -logfile CoreKeeperServerLog.txt -world 0 -worldname Purple Drop Server -worldseed 0 -worldmode 0 -datapath /home/steam/core-keeper-data -maxplayers 10 -season -1

Okay, so, no need to compose again? Just a simple restart is enough?

Yes, you will. I would suggest connecting to the container and copying the ~/core-keeper-data/CoreKeeperServer_Data so you don't lose your save.

Micke90s commented 1 week ago

@SuperNov4DZN I think that you have to use docker-compose down and docker-compose up to set the environment variables. This will cause that the container is rebuild. Please backup your save games to the host and rebuild it.

SuperNov4DZN commented 1 week ago

@SuperNov4DZN I think that you have to use docker-compose down and docker-compose up to set the environment variables. This will cause that the container is rebuild. Please backup your save games to the host and rebuild it.

Ok, thanks for the help! Appreciate it ♥️, I'll give it a try asap.

arguser commented 1 week ago

Could you please try to set the line DATA_PATH= from your core.env to DATA_PATH=/home/steam/core-keeper-data.

Update: Should already be fixed with #28 - Fix may only work if environment variable is not present. 🤔 Could be the problem.

Your save games should be available under /home/steam/.config/Pugstorm/Core Keeper/DedicatedServer within the container.

I just created a server without the DATA_PATH environment variable and worked as expected. So you are probably correct.

SuperNov4DZN commented 1 week ago

Okay, I did what @Micke90s told me to:

Changed core.env DATA_PATH:/home/steam/core-keeper-data

Then docker-compose down docker-compose up -d

Waited for a few seconds, got the notification on discord with the GameID, and after checking I now have everything on the right place, I have access to the server config files both on host/server-data and container/core-keeper-data

Worked like a charm, again, thanks for the help everyone, I'll be closing this issue.