Quest Data, Aliases and Packages

[JasmineMcCoy]

I have read the description (on creation kit wiki and other tutorials) of various options for Quest Data, Quest Reference Alias tabs and Package Templates, but there are some things still not very clear to me and I hope somebody could help me understand.

 

- What the "Run once" in the Quest Data tab acually does? When is it needed?

- And "Warn on alias fill failure"?

- Can I choose any value for the quest priority or should I keep it below some level?

- In the Reference Alias when do I need to tick "Option", "Reuse in quest" and "Allow Reserved" and when to leave them as is?

- What is "Force into alias when filled"?

- In a ForceGreet type package, what's the difference between "(forcegreet)" and "(hello)" topics?

- Do I need to set a quest owner for the package?

- In a ForceGreet type package, should I keep the radius below some value?

 

Thanks.

[Terra Nova]

I have read the description (on creation kit wiki and other tutorials) of various options for Quest Data, Quest Reference Alias tabs and Package Templates, but there are some things still not very clear to me and I hope somebody could help me understand.

 

- What the "Run once" in the Quest Data tab acually does? When is it needed?

- And "Warn on alias fill failure"?

- Can I choose any value for the quest priority or should I keep it below some level?

- In the Reference Alias when do I need to tick "Option", "Reuse in quest" and "Allow Reserved" and when to leave them as is?

- What is "Force into alias when filled"?

- In a ForceGreet type package, what's the difference between "(forcegreet)" and "(hello)" topics?

- Do I need to set a quest owner for the package?

- In a ForceGreet type package, should I keep the radius below some value?

 

Thanks.

• Calling Reset() will not work. When the quest is completed or stopped, you can't reset it.
• Mostly unused, one would think this does what it implies, but I personally don't know.
• I'm taking a guess here: When an NPC is attached to more than one quest, this number determines what order the starting dialogue options for the quest appears in. Higher priority = this is the quest to be initiated.
• I don't understand "Reuse in Quest", but Allowed Reserved makes it so there is no conflict with the alias that is already reserved in another quest, as otherwise the alias will not be filled due to the NPC or object being reserved in another quest, when Allowed Reserved is not check.
• Seems to be the same as ForceRefTo() although I am not sure, as I mostly use ForceRefTo() when trying to force something into an alias(if I need papyrus)
• Not really sure.
• Yes, or the quest will either not start, or the package on the alias will not run.
• Not really sure.

[JasmineMcCoy]

Thank you very much for the reply!

 

• I'm taking a guess here: When an NPC is attached to more than one quest, this number determines what order the starting dialogue options for the quest appears in. Higher priority = this is the quest to be initiated.

 

I know that if two quests load packages on the same npc, the one with higher priority wins. However I'm wondering if I shouldn't be setting the priority too high to avoid risking to overwrite something important.

 

• I don't understand "Reuse in Quest", but Allowed Reserved makes it so there is no conflict with the alias that is already reserved in another quest, as otherwise the alias will not be filled due to the NPC or object being reserved in another quest, when Allowed Reserved is not check.

 

What about the "Optional"?

 

Another question: I can't find many info on quest commands start() and stop(), would it be an issue giving the start() command to an already running quest and viceversa, sending stop() to a quest already stopped?

Edited September 19, 2014 by JasmineMcCoy

[Terra Nova]

Start() will do nothing on an already running quest. Stop() will also do nothing on a quest already stopped, however.. keep in mind, when a quest is completed(reached its completed stage), it can still be running, because stop was not called. It is wise to get in the habit of calling Stop() where necessary, so that all quest variables are released.

 

Optional allows any reference to fill it at run time, by using ForceRefTo(), and gives you access to the function Clear(), so that you can clear that alias when it's not needed anymore. Checking optional is the best way in troubleshooting aliases that aren't being filled because optional will allow a quest to run even if the aliases aren't being filled.

Edited September 20, 2014 by Terra Nova

[JasmineMcCoy]

I see, thank you very much.

[piotrmil]

 

I have read the description (on creation kit wiki and other tutorials) of various options for Quest Data, Quest Reference Alias tabs and Package Templates, but there are some things still not very clear to me and I hope somebody could help me understand.

 

- What the "Run once" in the Quest Data tab acually does? When is it needed?

- And "Warn on alias fill failure"?

- Can I choose any value for the quest priority or should I keep it below some level?

- In the Reference Alias when do I need to tick "Option", "Reuse in quest" and "Allow Reserved" and when to leave them as is?

- What is "Force into alias when filled"?

- In a ForceGreet type package, what's the difference between "(forcegreet)" and "(hello)" topics?

- Do I need to set a quest owner for the package?

- In a ForceGreet type package, should I keep the radius below some value?

 

Thanks.

• Calling Reset() will not work. When the quest is completed or stopped, you can't reset it.
• Mostly unused, one would think this does what it implies, but I personally don't know.
• I'm taking a guess here: When an NPC is attached to more than one quest, this number determines what order the starting dialogue options for the quest appears in. Higher priority = this is the quest to be initiated.
• I don't understand "Reuse in Quest", but Allowed Reserved makes it so there is no conflict with the alias that is already reserved in another quest, as otherwise the alias will not be filled due to the NPC or object being reserved in another quest, when Allowed Reserved is not check.
• Seems to be the same as ForceRefTo() although I am not sure, as I mostly use ForceRefTo() when trying to force something into an alias(if I need papyrus)
• Not really sure.
• Yes, or the quest will either not start, or the package on the alias will not run.
• Not really sure.

 

>warn on alias fill failure

>mostly unused

 

Are you kidding me, bethesda?! You add a debug tool that doesn't work?!