Added .packignore support to exclude files from PAKs #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
.packignore
support to exclude files from PAK archivesThis PR introduces support for a
.packignore
file, allowing modders to exclude specific files and directories from being packed into.PAK
archives. This prevents unwanted files, such as source control folders, temporary logs, or build artifacts, from being included in the final package.Why This Feature is Needed
Currently, LSLib includes all files within a directory when creating a
.PAK
, which can lead to temporary build files and other unnecessary files being packed. Until now, modders had to manually remove these files before packaging. This PR provides a clean solution by allowing modders to define exclusions in a.packignore
file.How It Works
The
.packignore
file is placed in the mod directory and follows a similar syntax to.gitignore
, supporting:debug.log
,config.json
)bin/
,obj/
,.git/
)*.log
,*.tmp
)Example
.packignore
file: