Kegath

All good, thanks for all you do!

Is there a way to set up Palworld to auto restart when a new update is available? I have it restarting daily at the same time, but if an update releases, players need to wait until the scheduled restart to play unless i manually restart it.

Unraid version 6.12.3 Hello, I am having this issue with allthemods8 and allthemods9 when I try to start the containers. The containers immediately stop when I try to start them. I wait for the container to stop by itself, but then I get the following message in the log. + FORGE_VERSION=1.19.2-43.2.14 + cd /data + [[ true = \f\a\l\s\e ]] + echo eula=true + [[ -f Server-Files-1.0.25a.zip ]] + [[ -n -Xms20480m -Xmx20480m ]] + sed -i '/-Xm[s,x]/d' user_jvm_args.txt + for j in ${JVM_OPTS} + sed -i '$a\-Xms20480m' user_jvm_args.txt + for j in ${JVM_OPTS} + sed -i '$a\-Xmx20480m' user_jvm_args.txt + [[ -n '' ]] + [[ -n '' ]] + [[ -n '' ]] + sed -i 's/server-port.*/server-port=25565/g' server.properties sed: can't read server.properties: No such file or directory + chmod 755 run.sh chmod: cannot access 'run.sh': No such file or directory + ./run.sh /launch.sh: line 47: ./run.sh: No such file or directory What am I doing wrong? I cannot find any information when I search for it. I am "Deleting the downloaded server file in /data will restart the install/upgrade process." to see if that resolves it. Deleting the zip file resulted in same issue. Changing permissions to read/write for owner, group, and other results in same issue I noticed this in the log while attempting to reinstall again. "Failed to connect to files.minecraftforge.net port 443: Connection timed out" Edit: issue appears to be resolved after many attempts of reinstalling the container. My guess is the minecraftforge site has issues