IsharaMeradin Posted August 4, 2021 Share Posted August 4, 2021 Not trying to disprove anything. Merely trying to help. But this is something not normally seen. And those "wild theories" I found, the person asking about it said they had merged plugins and got those errors. Not too far of a stretch for those responding there to follow in that frame of mind. I would say that if you were not merging mods but did do something to alter the plugin, that perhaps there is something in common that both processes failed at doing properly. What that is? I do not know. Then again, you said the mod was removed. Unless the author is one of those that recently opted to remove all their mods, perhaps this was an issue that they needed to work on. At any rate, good luck in finding a solution or at the very least a reason as to why it happened. Link to comment Share on other sites More sharing options...
primem0ver Posted August 8, 2021 Author Share Posted August 8, 2021 Sorry... I supposed people just make a lot of assumptions based on their experiences. That includes me. I have had a lot of experiences where people often offer advice or theories without really understanding the nature of the problem. I haven't done anything to change these mods. If I had, I would have started with the assumption that I caused the problem and wouldn't have brought it up. You are right. This problem is rare but in my testing of my new software, I have come across it more than once and the mods with this issue are exactly as I downloaded them from Nexus. When I posted the original problem, I wanted to make sure my software was correcting a real problem because I have programmed it to treat issue just as it appears that SSEEdit does... as an error that needs to be corrected. Link to comment Share on other sites More sharing options...
Recommended Posts