0.15.1

Release

0.15.0

0.15.0: June 23, 2021

Support for Beamdog and GOG installs

(#65)

nasher should now work without without additional configuration for those who installed NWN using the Beamdog client, GOG, or non-default Steam locations. The preferred way of setting the install location is to set the $NWN_ROOT environment variable as this variable is also read by nwnsc and niv's tools. In the case of nwnsc, it allows the user to run with the default -l flag instead of having to set --nssFlags:"-n '/path/to/nwn/data'".

When nwnsc is called with the -l flag, it first checks the $NWN_ROOT environment variable to get the location of the NWN install. This value is also checked by the neverwinter.nim tools. If the variable has not been set by the user, nasher will check for Steam, Beamdog, and GOG installs and set the NWN_ROOT variable accordingly. This means users should be able to just use the default nwnsc flags (-lowqey) and it will find the NWN install without issue.

Similarly, the $NWN_HOME directory is used for the path in which modules, haks, etc. will be stored. If the --installDir flag was not passed, the environment variable will be checked. If the environment variable was not set, it will fall back to ~/Documents/Neverwinter Nights or ~/.local/share/Neverwinter Nights, depending on the OS.

gffFlags support re-enabled

(#75)

nasher returned to calling the nwn_gff binary when converting to and from json. This re-enables the --gffFlags setting, allowing (among other things) setting of alternate file encodings.

Allowed --key value parameter syntax

nasher now allows options to be passed to nasher using the --key value syntax rather than just --key:value and --key=value. The old way still works, but this will be more familiar to terminal users.

Executable scripts now checked after compilation

(#81)

Added a warning if compilation of an executable script does not yield a matching .ncs file, This helps to prevent nasher from reporting successful compilation in case of an uncaught nwnsc error. Thanks, @tinygiant98!

Fixed duplicate choices in source list

(#79)

nasher no longer asks the user to choose a file when multiple targets match the same file.

---

Details: 0.14.2...0.15.0

0.14.2

Release

0.14.1

Release

0.14.0

0.14.0: December 20, 2020

Support for git branch-based workflow (#54)

You can now specify a git branch to use when packing or unpacking a target. You can do this as a command-line parameter using --branch:foo or within your nasher.cfg using the branch field. The branch field can be used by the package or by targets. If a target does not have a branch specified, it will use that of the package. If neither has a branch specified, nasher will use whatever branch is currently checked out. The --branch command-line flag overrides any setting in nasher.cfg.

Thanks to @tinygiant98 for his hard work on this feature.

Support for NWNT format (#60)

Nasher now supports the nwnt file format. Based on nwn_gff from the neverwinter.nim tools, this output format utilises the libraries of those tools for a custom output language instead of json. The output language is designed to be similar to json that has been put through gron. A standalone conversion tool is also available at the project page.

To enable, use nasher config gffFormat nwnt (remember --local to only affect current package).

Thanks to @WilliamDraco for his hard work on this feature.

---

Details: 0.13.0...0.14.0

0.13.0

0.13.0: November 07, 2020

Display an error message when a resource filename is > 16 characters (#59).

When a file being packed into a module, erf, or hak is > 16 characters long (not including the file extension), nasher will now emit an error and ask if the user wants to continue packing.

Ask which file to pack when mulitple copies exist (#58)

When the convert command finds multiple versions of the same source file within the target's source directory, it will now ask which one the user wishes to use.

This change also stops nasher from automatically making the source filenames lowercase. Previously, if the user had both src/foo.nss and src/FOO.NSS in the source tree, the latter would be renamed to the former, wiping out any differences between the two. The converted file will still be lowercase, so the user must choose which file to use in this case.

Other fixes

• Passing relative paths to the -nssCompiler, --gffUtil, --tlkUtil, and --erfUtil flags now works correctly (#55)
• A help message is shown if an unknown command is passed. Previously, nasher would attempt to verify that required binaries were installed before checking if the command the user issued was valid. This caused a KeyError and prevented the help message from being shown.
• Bump required version of niv's tools to 1.4.0. Previous versions would not compile on nim >= 1.4.0.
• Issues with glob and regex 0.17.0 have been fixed upstream. Nasher no longer requires an old version of regex to work.
• The readme has been rewritten and is hopefully more welcoming to new users (#53). Thanks, @tinygiant98!
• The docker image is now being built against Alpine rather than Abuntu. This should result in a faster build and smaller download for docker users.

---

Details: 0.12.3...0.13.0

0.12.3

Release