Describe your problem

First off, I'm on a Fedora Linux distro which doesn't have the best support in general. I ended up trying a ton of things to get any unity game modded, including: Bepin & Melon, running native & wine/proton, IL2CPP & mono, and a few different unity games. I'm pretty tech savy and am decent at following directions and diagnosing problems - I am also a developer.

Even with all logging options enabled, this was all I would see from Bepin for hours of trying things:

[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 0 plugins to load
[Message:   BepInEx] Chainloader startup complete

Which left me wondering, is this a .net problem? Is it a wine problem? File access problem? An unlogged exception from elsewhere??

As a programmer, it's my opinion that the level of logging Bepin does when trying to do its core feature (Load mods) is far from ideal, for both mod developers and end-users.

Proposed solution

Add verbose logging for the Chainloader (possibly as a BepInEx.cfg option) which logs problems loading plugins and other assemblies:

• Warning: Plugin X is not compatible with this BepInEx version and will be skipped.
  (Probably others!)

Alternatives

No response