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
We need to ensure that no mods claim to contain assemblies that have the same name. During mod enumeration and metadata loading, similar to when dependency resolution happens, is the best time for this to happen. If two mods have the same name, we should take appropriate action, by warning the user that ModA and ModB and ModF all claim to have preload or runtime assemblies by name Foo.dll or whatever, and that ModA's assembly will be used.
Or we can refuse to continue with the mod loading process.
The text was updated successfully, but these errors were encountered:
We need to ensure that no mods claim to contain assemblies that have the same name. During mod enumeration and metadata loading, similar to when dependency resolution happens, is the best time for this to happen. If two mods have the same name, we should take appropriate action, by warning the user that ModA and ModB and ModF all claim to have preload or runtime assemblies by name Foo.dll or whatever, and that ModA's assembly will be used.
Or we can refuse to continue with the mod loading process.
The text was updated successfully, but these errors were encountered: