Difference between revisions of "Talk:Activate"
Jump to navigation
Jump to search
→Fake "Nesting": is deep nesting really necessary/useful?
imported>ShadowDancer m (→Can't activate whle on a horse: typo) |
imported>Quetzilla (→Fake "Nesting": is deep nesting really necessary/useful?) |
||
| Line 83: | Line 83: | ||
:::I've done it. A hint to the simplest way, not only to do it, but also to manage it: from a quest script or another object's script, use/set object variables that are triggering your stuff, exactly when you want it... ''set refObjectID.localVar to 1'', where a conditional block on localVar, within the refObjectID's GameMode block script, would trigger whatever stuff you wish for it to render. Like a "Master script" that is managing the cascading events from one single object's script that is NOT involved into that chain reaction (which object can be hidden in the player's cell, or that would have no other use than showing itself as well as doing this "orchestration" silently). --[[User:HawkFest|HawkFest]] 21:54, 16 April 2008 (EDT) | :::I've done it. A hint to the simplest way, not only to do it, but also to manage it: from a quest script or another object's script, use/set object variables that are triggering your stuff, exactly when you want it... ''set refObjectID.localVar to 1'', where a conditional block on localVar, within the refObjectID's GameMode block script, would trigger whatever stuff you wish for it to render. Like a "Master script" that is managing the cascading events from one single object's script that is NOT involved into that chain reaction (which object can be hidden in the player's cell, or that would have no other use than showing itself as well as doing this "orchestration" silently). --[[User:HawkFest|HawkFest]] 21:54, 16 April 2008 (EDT) | ||
True, this can be done, but it's not really nesting. Nesting means everything runs before the next line of code runs - this avoids a good chunk of timing issues ("orchestration") and would be much prefered.--[[User:Haama|Haama]] 05:28, 30 July 2008 (EDT) | True, this can be done, but it's not really nesting. Nesting means everything runs before the next line of code runs - this avoids a good chunk of timing issues ("orchestration") and would be much prefered.--[[User:Haama|Haama]] 05:28, 30 July 2008 (EDT) | ||
:I was thinking about this, and I was wondering what situations would really call for nesting 5-6 levels deep? I think generally better practice would be to have most activator scripts do something and then return, rather than call another activator mid-script. Most things that can be done via deep nesting can also be done relatively painlessly via simple nesting. So again, I'd be interested to see examples of where deep nesting would be used and for what. | |||
:--[[User:Quetzilla|quetzilla]] 06:13, 10 August 2008 (EDT) | |||
== RunOnActivateBlock Flag == | == RunOnActivateBlock Flag == | ||