Unexplainable and incorrectable line in papyrus log

[schatten]

Hi.

 

Can someone explain to me how and why this line exist in my log?

 

[03/01/2014 - 08:02:23PM] warning: Property EvangelineCombatAICombattargetScene on script EvangelineCombatAIQuestScr attached to EvangelineCombatAI (2E0442C8) cannot be initialized because the script no longer contains that property
 

The property does not exist in my source and compiled source. Yet it won't go away when starting a new game. It's just there... like a ghost haunting me.

 

 

Another one is this:

[03/01/2014 - 08:02:23PM] Error: Property SolitudeAvenues on script EVA_QF__0203FC67 attached to EvangelineMarriageWedding (2E03FC67) cannot be bound because <NULL form> (00037EEA) is not the right type

 

What does this one want from me? I have a Cell Property properly filled, yet I get this entry?

 

 

 

Oh and what should I do here?

    [ (00000014)].Actor.IsInLocation() - "ObjectReference.psc" Line 604
    [Evangelineradiantfetchsidequest01 (2E081D42)].Evangelineradiantkillsqscr.OnUpdate() - "Evangelineradiantkillsqscr.psc" Line 10
[03/01/2014 - 08:04:30PM] Error: Cannot call IsChild() on a None object, aborting function call
stack:

 

The quest isn't even running... but it complains about this line:

        if Game.GetPlayer().IsInLocation(Alias_Location.GetLocation()) == False

 

Of course it complains as the alias is not filled... because the quest isn't running.

[WillieSea]

Old scripts are STILL in your save game, its called saved game corruption. If you ever in the past had a variable, it is now part of your save game. Some script changes will also be part of your save game.

 

You should ALWAYS use a clean save game when testing your scripts. That is a save game that has NEVER had your mod 'activated' when you made the save game.

[schatten]

If it would be that easy.

The bethsoft CK forum revealed the solution:

The first one is a CK bug.

 

The second one I have no clue. It is a Cell, the property is a properly filled cell... but returns null form.

 

The third one means I had to add unequal null checks. Quite frustrating.