Hi,

This error is popping up:

If a script no longer contains this property, why is the game trying to initialize it?

The mod runs with no problem at I can see at the moment, because the script doesn't use property at all. However, will this cause problems in the long run?

How do I stop it from trying to initialize that property?

I'd open up the quest/item/thing the script is attached to (maybe 1D00ADF2) to check the property isn't assigned a value, save and retry.

What chuck said.

This seems to happen if a script had a property which was set to a value, but that property has since been removed from the script without opening and closing the Properties window for the script.

Also script information sticks to the save, so you have to be extra special careful about things like this.

Thanks! I'll open the Properties window to get it cleared.

@Arthmoor: Really? So there's no way to stop those save files from initializing the property, and logging those errors?

Try removing the script, then reattaching it/filling properties. Properties will actually get wiped when the script is pulled as that's all stored in the record(s) the script is attached to... If you remove a property, then add it back, note that it'll automatically point to wherever it was previously pointing at whereas, if the script is removed and added, the slate is wiped clean.

Yep, really. I have stuff like this still lurking on my saves from changes that were done eons ago, even with removing and reattaching the script.