Open Deliphin opened 8 months ago
Hmm.
This is a bit of a tricky one with the current architecture, as there's a fair bit more than config discovery that relies on cwd.
Are you able to modify the startup command itself? If so, you could add a cd
to the start and remove the mods/
from the path to the jar.
If not, I'd suggest running the manual restoration steps.
I'll likely be rewriting the commandline the update after next (so, 3.6), so I'll fix this bug then.
Describe the bug I'm using a server host (HumbleServers), which uses Pterodactyl for its game management. My servers' mods including this one are stored in
/home/container/mods/
and configs in/home/container/config/
, but if I try to run the Jar on its own for its terminal interface, it fails to load because it's expecting the properties file to be in/home/config/
, skipping over the container folder. Note: It does correctly create the properties file in the correction location (/home/container/config/AdvancedBackups.properties
) when the game server is run.Pterodactyl doesn't allow users to access the
/home/
folder, so making a copy of my config folder there is not an option.To Reproduce Steps to reproduce the behavior:
/home/container/mods/
Expected behavior It to correctly find the config and allow me to use the terminal interface.
Versioning (please complete the following information):
Additional context What I believe is going on is its starting directory is up 1 level from the mods'. This would make sense given Pterodactyl is probably expecting to run whatever jar it's given from the container folder. If that's the case, then the solution should be as simple as adding more checks for config locations. Instead of just
../config/AdvancedBackups.properties
, also check/config/AdvancedBackups.properties
.My full startup tab in Pterodactyl: