Difference between revisions of "EvaluatePackage - Actor"

From the CreationKit Wiki
Jump to navigation Jump to search
imported>Perdev
m
imported>Terra Nova2
m
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Latent Functions]]
[[Category:Scripting]]
[[Category:Scripting]]
[[Category:Papyrus]]
[[Category:Papyrus]]
Line 22: Line 21:
Bob.EvaluatePackage()
Bob.EvaluatePackage()
</source>
</source>
== Notes ==
* This function can bring about undesired results with travel packages.
** For example, if you have a travel package with them going to whiterun, the package will run as expected.
** If however you call EvaluatePackage for when conditions for a different package is met to travel to say, Windhelm, the previous package will continue to run for a random amount of time.
** Should the previous package run to the point where it reaches its destination, thus ending the package, '''after''' EvaluatePackage() was called, '''the next package will not process.'''
** More testing as this may be an issue when used with [[SetPlayerAIDriven - Game|SetPlayerAIDriven]].


== See Also ==
== See Also ==
*[[Actor Script]]
*[[Actor Script]]
*[[GetCurrentPackage - Actor]]
*[[GetCurrentPackage - Actor]]

Latest revision as of 08:22, 27 September 2014

Member of: Actor Script

Forces this actor's AI to re-evaluate its package stack.

Syntax[edit | edit source]

Function EvaluatePackage() native

Parameters[edit | edit source]

None.

Return Value[edit | edit source]

None.

Examples[edit | edit source]

; Tell Bob to re-evaluate his package stack
Bob.EvaluatePackage()

Notes[edit | edit source]

  • This function can bring about undesired results with travel packages.
    • For example, if you have a travel package with them going to whiterun, the package will run as expected.
    • If however you call EvaluatePackage for when conditions for a different package is met to travel to say, Windhelm, the previous package will continue to run for a random amount of time.
    • Should the previous package run to the point where it reaches its destination, thus ending the package, after EvaluatePackage() was called, the next package will not process.
    • More testing as this may be an issue when used with SetPlayerAIDriven.


See Also[edit | edit source]