FEAT: Document OutputFile param #57
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t in tes3merge choosing to place merged objects.esp alongside engine resources
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Stupid git commands.
Documents the output file param, checks a system directory for tes3merge/TES3Merge.ini, and throw explicitly if no conifguration is found.
Also fixes a regression where weird setups that had a
resourcesdirectory defined, but nodata-local, would end up resulting in merged objects.esp being placed inresources/vfs, where it would be overridden sometimes and also nobody would ever look. Probably this would've happened if someone ran tes3merge against the OpenMW.cfg in Documents/, whilst also having some core shader mod installed (OWSE, Wareya's PBR), but not having an override directory configured.