Differences

This shows you the differences between two versions of the page.

--- lua:scriptenvironments [2015/10/17 21:26] – [getpc() and getroom()] aethyn
+++ lua:scriptenvironments [2016/02/08 04:45] (current) – [Script Environments] vodur
@@ Line 1: / Line 1: @@
 ====== Script Environments ======
-With the exception of the [[:lua:sharedtable|shared table]] all Lua scripts run in the environment they're first called upon and by default have no access to variables or methods in other environments. These environments are the OBJ, CH/MOB, ROOM, AREA spaces, along with a few others. There are several ways to "break out" of an environment and affect external environments.
+All prog scripts run in the scripting environment that is attached to the game object to which the trigger is attached. For instance, mprogs run in the environment of the mob that is running the script. Each individual environment represents the "global" scope for the script, and thusly a "global" variable or function in one environment cannot be accessed from a script running in a different environment.
+There are a few ways to share values between different script environments, the most simple to use being [[:lua:sharedtable|shared table]].
 ===== Simple interactions =====
@@ Line 120: / Line 122: @@
 In the function the "players" table, which only contains the strings of a PC's name (and not the CH object) is looped through and checked against getpc() to make sure players haven't logged off.
+getroom() is even more straightforward. Since ROOMs of a certain vnum always exist, using getroom() will always allow you to access that ROOMs properties and methods. For instance, we can turn a "dormant" EXIT visible upon a mob's death:
+<code lua>
+-- DEATH. Make the exit up from 22000 visible.
+getroom(22000).up:setflag("dormant", false)
+</code>
+Again, there's no need for any checks, because if the room exists it always exists.