Basically what I want to accomplish is to trigger a custom made quest that requires completion of a vanilla skyrim quest.

the easiest way to do this is to fire the quest directly from within the skyrim quest, but i don't want to touch anything that edits vanilla data. so what i'm wondering is, what is the best way to "fish" for a trigger?


i've been reading up on RegisterForUpdate to set the quest in a polling state until the condition is met (required vanilla quest completed) but i don't know how efficient that would be. it doesn't sound like a good idea to have a function constantly updating until the condition is finally met.


is there any kind of event function that i could use that would trigger for specific quest related stages/objectives? kind of like how the "fetch me this ingredient" quests always update in real time when you find said ingredient?

As long as you have a sufficiently long interval between updates (which you should for this purpose) you shouldn't have any problems performance wise. Especially since you'll just be using a few lines of code to check for quest status.

Can't you just do an "if getstage quest " or 'isCompleted()" on the vanilla quest from your custom script?

that would only check the condition once. that's why i was wondering if using a polling state would be ok, because in order to fish for that condition constantly should the first attempt return false, it would have to be fed into itself on a controlled loop.


it would be nicer if i could find a direct way to trigger the quest that doesnt make any edits.



the vanilla quest in question is DB10 - death incarnate. i have a quest that requires the completion of this one (kill astrid).

i tried creating a reference alias of astrid (burnt version) on my quest and attaching an OnDeath event trigger script attached to the alias, but it doesnt trigger anything when i kill her.




EDIT - holy crap it worked. I set the alias to external reference and pointed it to DB10's astrid alias. attaching a new script to the alias of the alias doesnt edit the original data, but it works just the same. i got the debug message on screen after i killed her.

Interesting. I've been looking into how I can use alias's to trigger new quests without actually altering the vanilla ones. Haven't gotten anything working in my experiments though, but I seem to be surprisingly warm.

using an explicit alias reference screwed everything up, but when i set it to use External Reference (pointing to the already existing alias on the vanilla quest), it worked. and nothing is altered in the vanilla data