Currently on windows you must pipe in a list of filenames to wad for it to add every file contained within a directory. For ease of use being able to specify a directory instead of individual filenames would be preferable.
This could be coupled with an argument to hard-replace an entire wad (deleting all entries before adding new ones). The use-case being maintaining a single folder of textures as a source directory, and using wad to generate a new wad file after making changes in the directory.
Piping dir /b into wad should work but currently I have not managed to get it working. If it did it would be possible to achieve this process with rm test.wad && dir /b test/*.png | wad test.wad, but this is clunky, and relies on test.wad already existing, creating an extra hassle.
Currently on windows you must pipe in a list of filenames to
wadfor it to add every file contained within a directory. For ease of use being able to specify a directory instead of individual filenames would be preferable.This could be coupled with an argument to hard-replace an entire wad (deleting all entries before adding new ones). The use-case being maintaining a single folder of textures as a source directory, and using
wadto generate a new wad file after making changes in the directory.Piping
dir /binto wad should work but currently I have not managed to get it working. If it did it would be possible to achieve this process withrm test.wad && dir /b test/*.png | wad test.wad, but this is clunky, and relies on test.wad already existing, creating an extra hassle.