"Crashed!", but no crash?

[FurryEskimo]

Does anyone know exactly why a mod might appear with "Crashed!" next to it on the mod menu?

Context: I updated some code, it crashed.  I updated it more, it worked.  I updated it again, it crashed and displayed "Crashed!" next to it, so I undid the changes and it appears to work again, but it still displays "Crashed!" in the mod menu, even after the game has been restarted twice.

[Mr.CrazyPotato]

Its client, DST don't care about code changes. If it can see that your mod the problem it will show it as it is. But if you launch the mod and it'll work the crash mark should remove.

[FurryEskimo]

2 hours ago, Mr.CrazyPotato said:

Its client, DST don't care about code changes. If it can see that your mod the problem it will show it as it is. But if you launch the mod and it'll work the crash mark should remove.

Thanks.  That didn't fix the issue, but it did help me to discover the issue.  When th game is loaded it references a mod's modclientmain and the modmain.  My code ran as expected.  When launching a server though, the modclientmain is not run, and I had a file that references an array created in the modclientmain.  Since that array didn't exist, it crashed.  Fixing this removed "Crashed!" from the mod in the menu, so thank you.  I was not aware that the game checked the functionaity of the mods this way, but it's helpful to know now.