This is an issue with the CK where a property that WAS set correctly BUT for some reason sets itself to NONE!

AND you cannot see this until you open it (to examine the property) because it still has the symbol next to it that shows the property is SET to "something". I have seen this for some time now but this is the first time I remembered to document it.

See here:

spooky i have never seen that before and I've set up hundreds of properties.

Are you absolutely sure you saved the script properties, and didn't just close the properties window? And saved the object window, not just close the window?

um dude... how would that set it to NONE ?

I guess I will test that now and see what happens...

I have never seen that before either.

And the pencil simply means that you have clicked 'Set Value', even if you don't input a new value. Clicking 'clear value' get's rid of the pencil, setting it to the arrow, inheriting the parent object's script's properties.

Like Alex said, if you click Edit Value, it defines a value, and then you choose the value you want. None is a valid value, and the first option in the drop down menu.

What I meant was that it looks the same as all the others so it is well hidden.

Also: I just tested B1gBadDaddy's theory and it did not set it to "none".

edit: I have to intentionally set it to NONE, closing and saving will not do it. I was wrong, actually it will for some types of properties.

So what happens when you select an empty property, click the Edit Value button, then click the OK button without picking an object?

I take that back, it depends on the type of Property, in some case it will set to none. My first test was with an INT. But trying it with a keyword was different.

But I know I did not make a property, set it to none "accidentally" as then the script would not work, so I know it WAS set right at first.

I mean if the script did not work after I just made it I would have found this right away.

Instead I am finding them later down the road after some strange thing starts to happen in my testing.

Could this be because I define the property in the script itself (not in the property window)?

I just prefer doing it that way, but this may be why I am only getting this (or causing this to happen)?

Using NotePad++ would not do that right? I have used NotePad+ for many years in Oblivion and for all my scripts in Skyrim and never had this until about the last few months.

Oh, and there was another person (who posted here in this forum a few months ago) that had this issues as well.

It has to be something outside, because if scripts can just randomly lose their properties in the CK, what would that mean for us lot?

I think it has something to do with how I create the property in the script manually. I will avoid doing that for a while and see if I still get this issue.

Could just be a random oddity that would hopefully never happen again... I always manually create my properties in notepad++ and I never ran into a problem like that :/