Currently MelonLoader just adds multiple custom Assembly Resolve events.
This can have conflict issues in certain use-cases.
The Fix would most likely be changing it to a single custom event or to a central Manager that will handle resolving and redirection.

Some examples of these conflicts are:
• Assembly being resolved to the wrong Assembly.
• Assembly being resolved to the wrong Version.
• Compatibility Layer System overriding File Loads when its not supposed to.
• Compatibility Layer System not overriding File Loads when its supposed to.