-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata for SimplyKnock.esp uses improper condition #3005
Comments
The original PR that added the relevant data was this one. sibir's reasoning back then was Therefore, doing something like All that being said, we can change the condition to simply say |
Thank you for the detail and more info about the prelude so I better understand the tooling. Sounds good to me :) My proposition then (given any instance of PapyrusUtil will almost certainly be a newer version) would be:
Result:
|
The condition operator for SimplyKnock.esp's PapyrusUtil dependency is a checksum rather than a version check. This throws errors on later versions of the PapyrusUtil .dll file, contradictory to the error message given. Unfortunately, the .dll file does not contain version information, so we can't do a version check.
I read through the condition types list in the LOOT docs and none of the available conditions are suitable for this particular file.
One option I would use if supported would be a pseudo check that the date modified property on the file is greater than the date value specified in the condition (i.e. the date for the oldest supported version of a given file). This would require creating a condition for 'filemodified' or 'datemodified' which does not currently exist (more work).
Another option may be to convert the error into a warning (if the file exists), with a message to say to ensure it is at least the supported version - in this case v3.9 or greater. Only throw an error if the file does not exist (less work).
Current YAML for the SimplyKnock.esp:
Proposed YAML for option 2 (untested):
Thanks for consideration.
The text was updated successfully, but these errors were encountered: