Difference between revisions of "Talk:SetStage"

2,406 bytes added ,  14:42, 2 April 2009
no edit summary
imported>Scruggs
(clarify...)
imported>Dr.Phil
 
(13 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[User:DragoonWraith|<font face="Oblivion,Daedric Runes" size=3>D</font>ragoon <font face="Oblivion,Daedric" size=3>W</font>raith]] [[User_talk:DragoonWraith|<font face="Oblivion,Daedric" size=2>TALK</font>]] 13:05, 31 July 2006 (EDT): Does SetStage accept variables as an argument?
[[User:DragoonWraith|<font face="Oblivion,Daedric Runes" size=3>D</font>ragoon <font face="Oblivion,Daedric" size=3>W</font>raith]] [[User_talk:DragoonWraith|<font face="Oblivion,Daedric" size=2>TALK</font>]] 13:05, 31 July 2006 (EDT): Does SetStage accept variables as an argument?
: Yes, just like (nearly?) every OB function, it will take a variable for any numerical parameter. What's more interesting is that a script that stores a questID in a ref variable and then calls '''setStage refVar stageVar''' compiles fine. I haven't tested to see if it actually works, though. [[User:Scruggs|Scruggs]] 19:46, 31 July 2006 (EDT)
: Yes, just like (nearly?) every OB function, it will take a variable for any numerical parameter. What's more interesting is that a script that stores a questID in a ref variable and then calls '''setStage refVar stageVar''' works perfectly in the game. Seems reference variables can store pointers to base objects as well. Cool! [[User:Scruggs|Scruggs]] 19:46, 31 July 2006 (EDT)
 
== Install usage ==
 
You can use any other script type to tell if something has been installed, so the note has been removed.--[[User:Haama|Haama]] 11:00, 9 February 2008 (EST)
 
== Using variables or not? ==
 
I've not been able to use a variable to set the Quest stage.
Is there anyway to bypass this problem, or is the only way to use a very long list of elseif's?
Anything in OBSE?
--[[User:Dr.Phil|DrPhil]] 08:19, 1 April 2009 (EDT)
:I've used variables and seen others use variables without a problem. There might be an issue with remote variables (Ref.Var), but I know local variables work. Are you sure the variable is a short/long/int and set to a valid quest stage?
:--[[User:Haama|Haama]] 18:24, 1 April 2009 (EDT)
Well. If you have made it without a problem it maybe was me who did something wrong.
I'll do a new try today and hope it'll work better. I don't know if it affects anything, but I did the variable and the math in a result script on a topic. Maybe worth to mention at least. But, a new try later today!
--[[User:Dr.Phil|DrPhil]] 02:05, 2 April 2009 (EDT)
 
:Well, result scripts ''can't'' have local variables, so it is probably impossible to use <tt>SetStage var</tt> within one. If you modified the ''quest's'' variable (using <tt>set Quest.var to blah</tt>, then the Quest could should certainly able to do <tt>SetStage var</tt>. But the Result Script would have to use <tt>SetStage Quest.var</tt>, and I don't think that would work (though perhaps worth trying).
:[[User:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">D</span>ragoon <span style="font-family: Oblivion, Daedric Runes; size=2;">W</span>raith]] [[User_talk:DragoonWraith|<span style="font-family: Oblivion, Daedric Runes; size=2;">TALK</span>]] 05:27, 2 April 2009 (EDT)
 
::Stupid Bethseda.. why can't they make things that actually works? Then I'll have to do some stupid work-around here too.. Maybe use an activator would be the easiest? Any thoughts or ideas?
::--[[User:Dr.Phil|DrPhil]] 10:15, 2 April 2009 (EDT)
 
:::You've already got a quest, so you can attach a quest script with the necessary variables. Then refer to the variables from the result script (QuestName.Var).
:::--[[User:Haama|Haama]] 11:03, 2 April 2009 (EDT)
 
::::Thankyou both! Sometimes I need to hear things twice.. ^^
::::--[[User:Dr.Phil|DrPhil]] 14:42, 2 April 2009 (EDT)
Anonymous user