I have the following script attached to an Alias of mine:

Scriptname CitizenScript extends ReferenceAlias  ConditionalInt Property IsHome Auto ConditionalCell Property HomeCell Auto Hidden

The same alias has an AI Package attached to it, and I want to add a condition to that AI package, namely that the conditional property "IsHome" in the script shown above equals 1. So I make sure the AI Package has the quest owning the Alias as Owning Quest, I add a new condition to the AI package, pick GetVMScriptVariable from the list, I enable the parameter (Use Aliases) and click on the button under it to select a target. The Alias shows up in the first list just fine, but after I select it the second list of variables only has NONE available. For some reason it doesn't find/recognize the conditional IsHome property variable that is attached to the Alias.

Has anyone any idea how to fix this? The script has compiled properly, and I also set the IsHome default value to 0. The script has been properly attached to the Alias in question, and I also closed all windows and saved the plugin, even restarted the CK. Still nothing in the list where the IsHome conditional should show up.


Edit: The conditional IsHome does show up if I attach the script to a specific actor instead of an Alias and pick that actor as a target instead of the Alias. So, the conditional variable system doesn't work on Aliases with scripts it seems. Such a dynamic system in all other regards, and then this is left out...

i think it might be self-defense against a "catch 22" issue.

my guess is because the Alias doesn't technically exist until runtime, and script variables/properties must also be initialized at runtime. the condition in the AI package queries the script property in the alias. that property doesnt initialize until the alias is filled, but the alias contains the AI package itself, its essentially a catch 22.

I can predefine the starting values of Property variables in scripts attached to an Alias, so I doubt that that is the problem?