Edit :

My main issue seems to be resolved, but I still have another issue :

ReferenceAliases in Vanilla Skyrim autofill via the Properties tab, but mine don't... I'm not sure why, and would be grateful if anyone knew?

The Defines/Aliases are set up using the same name, the same as with Vanilla Quests Alias Defines, so, like normal properties, I'd expect them to autofill?

They only autofill if the script is part of the quest with the alias. Alias names aren't exclusive, so if your alias is called "Player" there's no way for the script to know which quest the "Player" alias belongs to. But if your script is attached to your quest, it assumes that's it and auto fills to the "Player" alias on your quest. However if your script is on anything else, a trigger, object, actor, etc. it doesn't know so it can't assume anything.

Then, I'm pretty sure it should be auto-filling, if I understand you right...

1. My Script is attaced to a quest.

2. My Alisases are set on the Quest Aliases Tab of that Quest.

3. My script defines the aliases:

ReferenceAlias Property ZCDMSOMapMarker01 Auto

4. The properties show the Quest Defined alias, and the Alias Tab has the same name ("ZCDMSOMapMarker01")

So, it should Auto fill like a normal alias, right?

Actually scratch that, the only example I can find is scripts attached to aliases, that therefor have an owning quest?

I have a script on a Player alias in my brawling quest, and it was an alias property for 'Opponent' which auto fills properly. I guess scripts attached to quests don't, just ones on aliases themselves? (Though not exclusively the alias that you need to auto fill)

- Double scratch that!

Try making the property line this instead:

ReferenceAlias Property Alias_ZCDMSOMapMarker01 Auto

And see if it auto fills.

It didn't, until I went back after totally closing everything down, so at least progress!

Unfortunately, they still don't seem to work...

I've assigned another few Aliases to items which should be disabled (right now they should be constantly disabled, since it's a perma-run onUpdate() for testing purposes), and even though the Properties and Aliases are defined, they're not disabling...

Im running this on one of them, for example :

Alias_ZCDMSOQuest01Reference02.GetRef().Disable()

The Alias is defined, and the Property points to the right Quest Alias, which is defined as a specific Reference in the world, but that reference does not take the command. The rest of the Script works fine, and this is immediately at the top of the OnUpdate() block, so I do not see how anything lower-down would interupt it, and there's nothing else re-enabling the reference

Do you know your update block is running? Make sure you have debug.notification("Your message") in there so you can see that it's actually running okay.

In addition, make sure these aliases don't have any enable parents. That completely disables your independent control over disabling them. If something has an enable parent, the only way to disable it is through that parent.