BaseDataPaths parameter in ecwolf.cfg is ignored
Issue #237
new
At least on linux in ecwolf 1.3.3-1 it is ignored. When I put pk3 files in ~/.config/ecwolf and try to launch e.g. "ecwolf --file ECWolf_HQpack.pk3", the game is launched without the resources from the specified pk3. The same goes for any path that I try to add to the BaseDataPaths parameter. It's not a problem with a given pk3 file, because the game can use pk3 files if you first change into the directory where the files are and launch the game from there.
For now I use a workaround by creating a desktop file with Exec=sh -c "cd /mnt/Data/Games/Wolf-3d;ecwolf --file ECWolf_HQpack.pk3 --file ECWolf_hdmus_BrainStewX.pk3"
Still, I don't think it's intended behavior, so I thought I should report this.
The only places that ECWolf looks for the main pk3 is the current working directory and the directory in which the binary is located. ECWolf works through symlinks so you can install ecwolf to somewhere like /usr/lib/ecwolf/ and then symlink to /usr/bin or however you want to do it.
This is partially by design since the pk3 and binary are tightly bound to each other so it wouldn't make sense to install it into ~/.config/ecwolf. I could rework that to give more flexibility though.