You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it came out in #48, and at least one informal bug report before that, if any NPCs in a profile point to invalid mods - including mods that were removed or renamed later on - the build is always going to crash.
These should already be reported as build warnings, but this isn't really a warning, it's an error. We know that the build cannot complete in this state and therefore it requires a different UI. Arguably, this should be shown prominently before even starting/showing any other build checks, and be required to be corrected.
Making this easy to correct would also be helpful, such as a filter on the Profile page by mod name (not plugin, because in this case the plugin was still valid).
The text was updated successfully, but these errors were encountered:
Each build check is now independent, and implements an interface so that an IoC container can inject them all into a build checker as a list/enumerable.
Checks have also been rewritten to use the new analysis system, and not have any generic parameters. The facegen check in particular now compares head parts and produces virtually no false positives - the only ones remaining are template NPCs, to be handled in #90.
A few minor features may be missing and labeled as todos.
#26#37#50#64
I'm fairly certain it's no longer possible to encounter this under normal conditions, since the default build process starts from the plugin and finds any relevant mods that do exist, and the facegen override will be ignored when creating the profile if the mod doesn't exist anymore.
As it came out in #48, and at least one informal bug report before that, if any NPCs in a profile point to invalid mods - including mods that were removed or renamed later on - the build is always going to crash.
These should already be reported as build warnings, but this isn't really a warning, it's an error. We know that the build cannot complete in this state and therefore it requires a different UI. Arguably, this should be shown prominently before even starting/showing any other build checks, and be required to be corrected.
Making this easy to correct would also be helpful, such as a filter on the Profile page by mod name (not plugin, because in this case the plugin was still valid).
The text was updated successfully, but these errors were encountered: