Running trying to use OneClick on NixOS results in BSMM not finding its dotnet runtime because the binary under lib/ is unwrapped (We automatically wrap the binary under bin/.)
BSMM should register the path it was run from (i.e. a wrapper script), not where it's raw binary lies. When distros wrap, it's for good reason; as is the case here.
A related issue is that it registers the dereferenced binary. We only install a symlink into a global path (i.e. /run/current-system/sw/bin/BeatSaberModManager). The app should register this symlink rather than it's absolute path which will change every ~2 weeks (i.e. /nix/store/nsxgxqhddz7klxcgwbn03gyh4wisx4lh-BeatSaberModManager-0.0.5/bin/BeatSaberModManager).
Running trying to use OneClick on NixOS results in BSMM not finding its dotnet runtime because the binary under lib/ is unwrapped (We automatically wrap the binary under bin/.)
BSMM should register the path it was run from (i.e. a wrapper script), not where it's raw binary lies. When distros wrap, it's for good reason; as is the case here.
A related issue is that it registers the dereferenced binary. We only install a symlink into a global path (i.e.
/run/current-system/sw/bin/BeatSaberModManager). The app should register this symlink rather than it's absolute path which will change every ~2 weeks (i.e./nix/store/nsxgxqhddz7klxcgwbn03gyh4wisx4lh-BeatSaberModManager-0.0.5/bin/BeatSaberModManager).