Difference between revisions of "Topic Info Fragments"
Jump to navigation
Jump to search
imported>Fg109 m (→Notes: added note) |
imported>Jsquirrel (→Notes) |
||
| Line 20: | Line 20: | ||
*Do not have any properties or variables pointing at a topic info fragment script. For memory reasons, these do not stick around and may cause odd behavior if you try to hold onto them. | *Do not have any properties or variables pointing at a topic info fragment script. For memory reasons, these do not stick around and may cause odd behavior if you try to hold onto them. | ||
* When a topic info script is first created, it isn't possible to add properties to it. You must first close the Topic Info dialog window and then reopen it before adding properties to the script. | * When a topic info script is first created, it isn't possible to add properties to it. You must first close the Topic Info dialog window and then reopen it before adding properties to the script. | ||
* You can use GetOwningQuest() to access the current quest object. | |||
== See Also == | == See Also == | ||
*[[TopicInfo Script]] | *[[TopicInfo Script]] | ||
*[[GetDialogueTarget - Actor]] | *[[GetDialogueTarget - Actor]] | ||
Revision as of 16:50, 13 June 2012
Type
Topic Info fragment scripts extend TopicInfo.
Run Time
Topic Info fragments are run when the topic begins, and when the topic ends.
Special Variables
- akSpeaker: This is the Actor that is speaking the topic. (May be None if the speaker isn't an Actor - in which case, check akSpeakerRef)
- akSpeakerRef: This is the ObjectReference that is speaking the topic. Will be the same object as akSpeaker.
Notes
- To get the Target of a line of dialogue you can do this:
akSpeaker.GetDialogueTarget()- Do not have any properties or variables pointing at a topic info fragment script. For memory reasons, these do not stick around and may cause odd behavior if you try to hold onto them.
- When a topic info script is first created, it isn't possible to add properties to it. You must first close the Topic Info dialog window and then reopen it before adding properties to the script.
- You can use GetOwningQuest() to access the current quest object.