
relative path not working for linux
WxAaRoNxW opened this issue ยท 3 comments
global_packs/required_data
doesn't work
./global_packs/required_data
doesn't work
../global_packs/required_data
doesn't work (tried this cause I thought maybe it was checking the config folder so I stepped back the dir
~/global_packs/requried_data
doesn't work as well
/home/user/global_packs/required_data
works properly
I guess, to solve this is to use the $HOME environment variable, or wherever the current working directory minecraft is running on.
It's in a docker container, specifically a pero image. the content is simply just server jar files.
What launcher are you using?
Global Packs relies on multiple ways to find the installation location.
If none of them worked, the launcher is likely doing something wrong.
As a quick explanation, MC does have a launch parameter telling it the full path, if that's set the mod uses that.
If it's missing, there is also a "root" folder, which usually is where a .jar file is launched from,
in minecrafts case, launchers should change that to .minecraft though.
If it's in your root path, something likely went wrong in the launcher.
it's a dedicated server inside a docker container (specifically made by pterodactyl) running simply server.jar or I assume, fabric-installer.jar
I have no idea, but suddenly the default config works now
I just noticed that doing these paths, I found that it created a ~
folder, which I assume the server suddenly started understanding where its current directory is now, or I just missed it. Then I reverted the config it and it's all good again odd