Zugg Software :: View topic

Sorcerer Joined: 13 Jan 2006 Posts: 715

Ok, I'm still learning CMUD scripting and I've come across a case of wanting to use a local variable as part of a pattern to #WAITFOR... however it doesn't seem to work. I'm just trying to find out if that should work and I'm doing something wrong, or if it doesn't work.

Example:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Temporary variables only exist within the scope of the setting that literally spawned them. #WAITFOR creates a thread beyond this particular setting, and so the temporary variable doesn't exist there even though the #WAITFOR was described in that setting's code.

I believe you would have to use some variation of #EXECUTE.

Sorcerer Joined: 13 Jan 2006 Posts: 715

Or just change it to a global variable, that would work as well, correct?

I mean, that would be much simpler all in all.

Posted: Wed Jun 30, 2010 7:18 pm

could you enclose the $localVar in %eval() within the #waitfor to force it work?

Magician Joined: 02 Feb 2004 Posts: 364 Location: USA

Perhaps:

#WAITFOR %concat("You get ", $num_to_get, " rose petals from the bush.") 3000 {IF Success Commands} {Crud, I failed, so do something else!}

Sorcerer Joined: 13 Jan 2006 Posts: 715

I decided to go with the global variable, so I could use it in the output from the WAITFOR as well. But thanks for the answers,

Posted: Thu Jul 01, 2010 3:35 pm

Actually, #WAITFOR does not cause a "new" thread to spawn. When your script encounters the #WAITFOR command, the current thread goes into the background. But this means you can still use local variables just fine later in the script.

The issue is that #WAITFOR does not expand local variables within the pattern. However, the following script will work fine:

Sorcerer Joined: 13 Jan 2006 Posts: 715

ok, thanks Zugg, I'll change back to that then. That's much more efficient memory-wise I would guess.