EIA485
EIA485
i have [a mod](https://github.com/EIA485/NeosExposePatchedMethods) that use's stemvr configs. dont think we should axe it.
maybe config options for enabling/disabling hotloading for anymod/not explicitly supported mods
if the mod implements onlateload then its hotloadable?
i dont really see an issue with just using OnEngineInit for mods that dont support hot loading.
maybe there should be a field in the mod class that a mod can set that overrides nml's config for if it should attempt to late load OnEngineInit
my reasoning for wanting the loader to know if a mod explicitly does not support late loading is we can have it log that it wont load x mod due...
there should probably be a method or delegate for other mods to know when a mod has been late loaded. this would be useful for mods like the config mod...
thats a good point, if a mod explicitly not supporting late loading was an assembly attribute we could check that before loading any assemblies
Afak the [mod manager](https://github.com/XDelta/NeosModManager) @XDelta has been working on has or will have an installer.
really interesting pr. im somewhat unclear on why this needs to be part of the mod loader as opposed to being a standalone mod that interacts with the mod loader's...