Difference between revisions of "Remote Activators"

181 bytes removed ,  23:53, 17 July 2007
m
minor elucidation - will update more later
imported>Sickleyield
m
imported>Guidobot
m (minor elucidation - will update more later)
Line 48: Line 48:


===Other===
===Other===
I've not mentioned a few other types of remote activators that I haven't found a use for yet (but perhaps you could). Activating doors (using their REF ID for those you didn't add) is an alternative way of teleporting to a location. Remote flora could be useful if you did some wierd stuff with ingredients. If you find any other uses for remote activators not mentioned here, please feel free to add to the comments below.
I've not mentioned a few other types of remote activators that I haven't found a use for yet but perhaps you could. If you find any other uses for remote activators not mentioned here, please feel free to add to the comments below.


----
----
Line 54: Line 54:
===Comments===
===Comments===


Important note: When using remote activators that bring up menu boxes, such as scrolls or containers, although the player cannot do anything until he clicks Close, your scripts will continue running. This means several such windows may open up at the same time if you are not careful. The situation is very similar to that when using the [[MessageBox]] command. I find setting flags between MenuMode and GameMode the easiest way to control this.
Important note: When using remote activators that bring up menu boxes, such as scrolls or containers, although the player cannot do anything until he clicks Close, your ''current'' script and MenuMode scripts will continue running. This means several such windows may open up at the same time if you are not careful, although only the last of a particular type will be displayed. The situation is very similar to that when using the [[MessageBox]] command.




[[Category: Useful Code]]
[[Category: Useful Code]]
Anonymous user