Dont support. about docker-palworld-dedicated-server

[jammsen]

Hey @brandonnorsworthy

my docker-compose is based off your readme and has not changed ...

That might be true, but thats like 2-3 weeks old

... it should be considered in additions going forward to accomidate people who have had servers running from the beginning.

I actually did that, i extended that docker-compose and the default.env as the community requested and after time the ENVs got so massive with feature that we needed to make it more readable, thats why we use a SLIM docker-compose.yml and a big default.env .... WHILE preserving downwards/backwards compability in the Dockerfile, IF you dont have the right ENV-Vars.

If you change your work pipelines you are setting the expectation that this might not work in a week which is kinda lame

Huh??? You are free to use the old image, with old bugs, not much improvements and not more features .... What are you talking about?! Thats why i tag all the releases with SHA7 hashes, so you can use version pinning and go back IF you want .... ?!?!

Also thats why we added a changelog, to inform you of changes and if they are Breaking Changes ....

Or do you expect me seriously not to make things better, to not listen to community, to not add more features, because that way your docker-compose.yml doesnt change?!?! How is that "kinda lame" ... why are you mean to me ... just because you dont like the progress?

Stagnation is the enemy of progress. - Ever heard that?

[jammsen]

Hey @brandonnorsworthy - your Docker-Compose is very very old. Please update to the new format, see Readme-Getting Started, but its best to wait until tomorrow, when the new big-release gets live. I will announce it in Discord.

The server will only be reinstalled when this condition is met: https://github.com/jammsen/docker-palworld-dedicated-server/blob/develop/scripts/servermanager.sh#L58