Question on Priority of quests and the effect on aliases

[PJMail]

Can someone confirm or refute my assumptions on how Quest priority effects packages applied via aliases?

 

Specifically if 2 quests have aliases that target the same NPC, and each of those quest aliases applies an override package, which package wins (as an NPC can only have one 'current' package)?

 

My assumption is the quest with the highest priority wins, and the highest possible priority is 100.

What happens if both quests are the same priority?

[SKKmods]

My findings by extensive (over 30 sample runs) testing AI packages and dialog is that the higher the quest priority value the higher the priority in the stack.

 

When two colliding quests have exactly the same priority I have observed (limited less than 10 sample runs) that if one is already active it stays active, and if neither are active its random.

 

If you are messing about then force Actor.EvaluatePackage() and Debug.Trace() Actor.GetCurrentPackage() to see what happens and let us know.

[lee3310]

Can someone confirm or refute my assumptions on how Quest priority effects packages applied via aliases?

 

Specifically if 2 quests have aliases that target the same NPC, and each of those quest aliases applies an override package, which package wins (as an NPC can only have one 'current' package)?

 

My assumption is the quest with the highest priority wins, and the highest possible priority is 100.

What happens if both quests are the same priority?

I can confirm the first assumption; higher priority will always win.

If same priority, then like SKK said: FIRST COME, FIRST SERVED (if you don't re-evaluate packages at least).

What i didn't try is having NPC in two different aliases with same quest priority then "EvaluatePackage()" (i think it will be random too)

Edited March 7, 2023 by lee3310