Skip to content
Discussion options

You must be logged in to vote

That's quite a specific use case. Windhawk can't anticipate all forms of file corruption or deletion, and so far it hasn't been a common issue/request.

Currently, what you can do is delete the LibraryFileName entry for each corrupted mod in the registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\Windhawk\Engine\Mods\<mod-id>
Then Windhawk will detect it as corrupted, and will suggest to compile it. Right now, I don't think there's a simpler solution.

In the future, I plan on adding command line options, which will help with such automation tasks.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by mazany
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants