Difference between revisions of "Category:Latent Functions"

Category:Latent Functions (edit)

428 bytes added , 19:09, 8 October 2012

See http://forums.bethsoft.com/topic/1373784-papyrus-threading-alternative-techniques/page__view__findpost__p__21629276

Anonymous user

@@ Line 1: / Line 1: @@
-This lists latent functions in Papyrus. If you call one of these functions, you unlock your script so that other waiting calls can now execute (and therefore possibly cause your variable values to change). For more information on threading, see [[Threading Notes (Papyrus)]].
+The idea for latent functions is that these functions take not-insignificant real-world time to execute. (There are some that are latent for other reasons, but this is the main one) For example, Wait is latent because it will not return until X real-world seconds have passed and SetCurrentStageID is latent because it waits for the quest stage fragment to finish running before returning. Note that if latent functions do not actually take any time (like a wait with a 0 time, setting a stage with no fragment, or an error that is detected early like calling it on None) they won't unlock your self long enough to actually let any other thread in.
+Below is the list of all latent functions in Papyrus.
 [[Category:Papyrus]]