Hey guys, I decided to turn on logging to see what sort of things my game throws out. And it was showing me errors for scripts attached to my quests, saying the property cannot be initialised because the script no longer contains that property.

It's confused me because the quest hasn't even started when this error was recorded. And in the CK the properties are fine. It said this about 4 or so other properties in my other scripts.

Also a lot a vanilla skyrim quests had similar errors show.

Is this normal? Should I be worried?

Do the same errors occur when you use a newly-started game save?

Yep which confused me even more lol.

Not normal, and yes, you should be worried. This has happened to me a couple of times now too and it took some serious gymnastics to clear up. Starting with having had to wipe out properties on an entire script and then put them all back because something got lost somewhere that the game couldn't cope with.

I've no idea what the trigger conditions are, but it hasn't happened more than the couple times I've had to deal with it. Thankfully.

Thanks Arthmoor. Must be bad then, but worrying if vanilla quest errors were there to :/

I see now yea. The script that the error says it's attached to, doesn't actually have that property, but it may have done at some point. Although the property is removed completely, the ref the error is referring to, still shows as being part of that script/quest, when you use Use Info.

So for me, it's saying my global is still attached to a quest (when I view the Use Info), when it's not. It seems that clearing the properties down on the script in the error, exiting the quest, and going back in, setting the value for all the properties again, does fix it.

Thanks for your help mate

The error stems from the master file telling Papyrus to set a property to a value, but the script has had the property removed. Usually this happens when you delete a property that a script used to have. In-game, Papyrus is just going to ingore the extra masterfile data after spitting out that error.

The CK should fix it for you automatically if you open the offending script's property edit window, and hit OK on *both* the property window and the form, and then save the plugin. It's doing a silent cleanup when you open the window, but it won't save the changes unless you OK them. In the cases where the script no longer has any properties (and so the OK button is greyed out), just detach and re-attach the script.

That's what I found mate, after playing around, simply opening up the properties again, OK the props and the script/quest, then Save, the errors go away. Didn't have to reset every property in the end

The http://www.creationkit.com/Papyrus_Runtime_Errors page on the wiki documents those errors. I only recently started using console logging, anyone who writes scripts should being using it.