So last night I tested and updated my most recent and most simple mod in Unity 2019.4.2f1, with the DFU v0.10.25 and it worked out fine. I did find out some things from this though, this first one might be obvious to some, but not to others. If you update a mod for v0.10.25, that built mod WILL NOT work in earlier version of DFU, and by not working, it won't show up in the mod list at all, so just keep that in mind, I had a question about that on my mod-page.
Besides that probably obvious thing, that particular mod was working fine when updated and running in the DFU v0.10.25 environment. When I started testing the mod I released just before that, which is more complex, I got some problems off the bat, somewhat hard to pin-point problems.
So it's having a similar issue that Ralzar has been having with updating some of his mods, it will work in a "virtual" form when used inside the Unity environment, but when built into a .dfmod package, it will not work, not in the Unity editor, nor in the DFU v0.10.25 compiled build, coming up with this error when the mods try to do their initialization after hitting "start."
Here is the error in my case:
- Capture.JPG (76.48 KiB) Viewed 1647 times
Now I could be completely wrong here, but I think the reason it's more difficult to debug in this case is because the issues are only happening in "built" versions of the mods, so the only place that can be pointed to when something goes wrong is the mod frame-work, since the mods are currently in a compiled package and are just binary files. But I have no clue if that is true on how it works, just guessing there, but i'm currently trying to figure out how to fix this mod's specific issue.
But since I'm only good at writing quests, that's wholly irrelevant.
You can still add to Hub during install with the Download Assistant. It's the same process as grabbing 2018.2.21f1 up until now.
