So after finally starting work on my contribution to ModTown, I hit a massive wall... my plugin is now completely unloadable in the CS. But the weird thing is that it loads fine in-game? (There's one minor script error not finding a referenced object, but apart from that it loads fine).

The plugin isn't finished, so I need to find a way to exorcise it!

I am freaked out for two reasons: 1) If I can't get this plugin working, I've lost a huge chunk of my progress (I do have previous copies of the plugin which load, but they're from yesterday, and I really don't want to repeat hours of exactly the same stuff); and 2) what if this weird unknown thing happens to me while I'm working on my big project?!

Here is what I know/have tried:

• Restarting computer makes no difference


• Using a different MW directory makes no difference


• Cleaning the plugin using TES3CMD makes no difference (TES3CMD didn't modify the plugin)


• There is one minor script error in the plugin where I forgot to tick "references persist" for a referred to object (but I've done this plenty of times before and it's never been an issue)


• Loading the plugin in-game causes no issues; I can even go to the new area added by the plugin w/ no problems


• The newest version of the plugin is the first where I made it dependent on the ModTown .esm and added to the ModTown landmass (but I also added other stuff, so big deal?)


• Does the CS just hate me???

Important update -- using Wrye Mash to remove dependency on ModTown esm allows the plugin to load in CS

This sort of thing is the bane of my existence... I feel your pain.

Two things I can think of off the top of my head to try out:

Remove dependency on ModTown 2015.esm and see if it will load properly

This may sound weird, but are you using any custom models in your claim? If so, try loading the esp in another directory like you did but don't bring the files with you. Sometimes corrupted meshes can cause CTDs as well.

I don't have any other ideas at the present. Going to bed in a few minutes. But I will help as much as I can...

Removing the dependency fixed the problem completely (i.e. it loads now)! But I'm still not sure why (or how to make it dependent safely). I moved some trees on the landmass around to better fit my claim -- could that have caused the problem?

As for the meshes, my blender skills are pretty dodgy, but I did all the exporting/loading in previous versions of the plugin which load fine. Could that still be a problem?

Sorry if I'm keeping you up with my incompetence! Feel free to go and sleep, and seeing if I'm still a mess tomorrow!

Edit: quoted you twice by accident

So I tested opening up the ok plugin as active, loading ModTown esm as well, making no changes in the editor at all and saving so the plugin becomes dependent but without any editing/adding, and even this is enough to render the plugin unloadable. I don't know what this means!

EDIT:

I tested the exact same thing as above with the earlier ModTown esm (Dec 2015) and it loaded fine post-dependency. Could it be an issue with the latest esm?