Open cltalmadge opened 2 weeks ago
It should already use it by default unless you tell it not to. If you haven't changed your older config settings, it'll override the default behavior. Check your values in your global and local config, specifically for nssCompiler.
Hello, sorry to take so long to get back to you. Yes, it seems to use it by default, now. Apologies for getting that tidbit wrong. However, it appears that it wants to find the userdirectory. I used to set userdirectory to the current working directory myself via nssflags, but it seems like nasher operates by appending its own nssflag arguments even if I provide my own:
--userdirectory /.local/share/Neverwinter Nights --root /nwn/nwn/data -c
I've tried to run Nasher from the container normally like so:
$ docker run --rm -t -u $(id -u):$(id -g) -v $(pwd):/nasher nasher:latest compile --clean --yes
Compiling target default
Updating cache for target default
Compiling 3776 scripts
Compile Error: rror: unhandled exception: Could not locate NWN user directory; try --userdirectory or set NWN_HOME (NWN_USER_DIRECTORY also
... works, but is considered alternate) [ValueError] ::
Hello! Nasher is currently using NWNSC by default, which seems to be no longer maintained. Would it be possible to have it updated to use the more actively maintained script compiler from neverwinter.nim? I know I can configure nasher to use this directly, but it might be more intuitive to have it use the newer compiler out of the box.