Hm yeah I can see how that would be a problemChain_Reaction post_id=76512 time=1598401491 user_id=2 wrote: It will cause me headaches if another user starts using our DLL names or namespaces
In that case, I'll have my mod check on world load to see if Chemistry actually is installed and add the string to sAssemblies if it isn't, and also tell my version of CalculateAttraction not to run if Chemistry is there. Should handle both compatibility with Woohooer now and compatibility (at least in this one regard) with Chemistry later. Thanks for the help!
[EDIT: I'm actually having a little trouble accessing sAssemblies, presumably because it's a private field. This line always gives me a null:
Code: Select all
FieldInfo assembliesField = nestedType.GetField("sAssemblies", BindingFlags.NonPublic)