Basically there is a difference between what properties the esp thinks a script has and what properties the script it is calling actually has. You get stuff like this
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A00441B) cannot be initialized because the script no longer contains that property warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A000D63) cannot be initialized because the script no longer contains that property warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A004415) cannot be initialized because the script no longer contains that property warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A0012F9) cannot be initialized because the script no longer contains that property warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A001DD7) cannot be initialized because the script no longer contains that property Error: Property CityShadowmarkControl on script TGRQuestBasedShadowmarkScript attached to (4A0049A6) cannot be bound because <NULL form> (00055C08) is not the right type
in your papyrus log. The esp thinks AttachedTo is a property of TGRPlayerHouseShadowmarkScript but it doesn't exist in the psc/pex file so it throws a warning. I removed the property in the esp (IE found where the scripts were called, loaded them, saved them and with CK magic they went away) CityShadowmarkControl on TGRQuestBasedShadowmarkScript was set to a different cell than the object was located which gives an error message. I changed the cell and object and fixed the error.
I didn't touch the logic, everything (should) work the way it did before but there will be 10ish fewer lines in the papyrus logs. For a normal human does it matter? Probably not, it's been like that for three years.However there is a new version of STEP coming out and I'm doing what I can to eliminate 'harmless' errors.
Give Feedback
4 comments
Basically there is a difference between what properties the esp thinks a script has and what properties the script it is calling actually has.
You get stuff like this
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A00441B) cannot be initialized because the script no longer contains that property
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A000D63) cannot be initialized because the script no longer contains that property
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A004415) cannot be initialized because the script no longer contains that property
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A0012F9) cannot be initialized because the script no longer contains that property
warning: Property AttachedTo on script TGRPlayerHouseShadowmarkScript attached to (4A001DD7) cannot be initialized because the script no longer contains that property
Error: Property CityShadowmarkControl on script TGRQuestBasedShadowmarkScript attached to (4A0049A6) cannot be bound because <NULL form> (00055C08) is not the right type
in your papyrus log.
The esp thinks AttachedTo is a property of TGRPlayerHouseShadowmarkScript but it doesn't exist in the psc/pex file so it throws a warning. I removed the property in the esp (IE found where the scripts were called, loaded them, saved them and with CK magic they went away)
CityShadowmarkControl on TGRQuestBasedShadowmarkScript was set to a different cell than the object was located which gives an error message. I changed the cell and object and fixed the error.
I didn't touch the logic, everything (should) work the way it did before but there will be 10ish fewer lines in the papyrus logs.
For a normal human does it matter? Probably not, it's been like that for three years.However there is a new version of STEP coming out and I'm doing what I can to eliminate 'harmless' errors.