Zugg Software :: View topic

Posted: Fri Feb 02, 2007 10:56 pm

#ALIAS un {
#VAR target %-1
#VAR dostuff {%item( @un, %random( 1, %numitems( @un))) @target}
pounce @target
}

and i have a trigger that does:

#FORALL @dostuff {#EXEC %i}

Mainly the problem is in @dostuff

If done as is, it evaluates with the variable call, not to mention it strips out the space between the ending parenthasis of %item and @target, not what i want.

If i quote the contents to make it a string, or use FUNC instead of VAR, it goes into @dostuff the way i want, but now the FORALL does nothing with @dostuff, it doesnt even spit the string to the MUD.

Any ideas?

Posted: Fri Feb 02, 2007 11:57 pm

Did you try putting curly braces {} around it?

Posted: Sat Feb 03, 2007 12:35 am

Which 'it' do you mean?

Posted: Sat Feb 03, 2007 12:47 am

Posted: Sat Feb 03, 2007 1:02 am

its for the #forall statement, i want the #forall to process it and sent the results via the #EXEC

and your syntax is wrong there as well Zugg... the concat should come BEFORE the item if your doing it that way, but it does fix the missing space once that is cleared up

but im still having the trouble that it gets evaluated at #VAR definition... i want it to randomize the results each time the #FORALL hits it

Posted: Sat Feb 03, 2007 1:18 am

Sorry, I misunderstood where the %concat was needed.

Yes, #VAR is *always* going to evaluate the value being assigned. That's one of the differences in CMUD mentioned In the Help file Here

If you don't want it to be evaluated, then you must use the #FUNC command instead of #VAR.

Posted: Sat Feb 03, 2007 1:36 am

If you had read my entire first post, you would have seen that i have tried #FUNC already.... I apprechiate your attempt to help, but dont suggest something i've already tried.

Posted: Sat Feb 03, 2007 1:42 am

Yes, I saw that, but I didn't fully understand what didn't work. I was addressing the problem you mentioned with #VAR evaluating. And as I said, #VAR is *always* going to evaluate, so you *must* use #FUNC if you don't want it to do that.

So, that leaves the #FORALL statement. Have you done a simple #SHOW @dostuff to see if it is forming a correct string list? Maybe you need to use %eval(@dostuff) in the #FORALL statement to force it to run the function?

I'm trying to help as much as I can, but you haven't really given us a lot of specifics. Showing us what you think should be stored in @dostuff and compare it to what it stores. Show us the sample output you are trying to get.

The entire script looks very wierd and complicated, so my guess is that there is probably a much better way to do what you are trying to do, so if we had a clue exactly what you were trying to accomplish, it might help. Hopefully one of the other gurus can help you more over the weekend.

Posted: Sat Feb 03, 2007 2:01 am

Okay... i will try to explain better.

@dostuff is a place holder i have to work around RoundTime, or delays before i can perform another command, not all commands induce RT so sometimes i can spit out several before having to wait again

@dostuff is often (in other cases) an array, which is why i use the #FORALL, to loop through it and execute each memeber

I have tried

Posted: Sat Feb 03, 2007 6:20 am

As long as @dostuff is in a global or external module then the script can see it. Anything else and that's the problem. My question is what does @un contain? I'm not sure it matters though, since @target (which is simply %-1) will be delimited by spaces and not pipes. Same when you do your "%item() @target" thing - you'll end up with a list that's separated by spaces. This will totally naff up #FORALL since it'll recieve a list separated by spaces when it wants a list separated by pipes.

For example, you run "un" with the arguments "test1 test2 test3" and you'll end up with @dostuff containing "RandomUnItem Test1 Test2 Test3". When this gets passed to #forall that'll cause problems since it's expecting a string list in the format "RandomUnItem|Test1|Test2|Test3". Use %replace to switch the spaces to pipes when it's passed to #forall (or when it's created if nothing else uses it).

Posted: Sat Feb 03, 2007 8:18 am

un=kick|jab|punch|uppercut|knee|elbow|throw

its a list of unarmed commands...

most offen @target is just a single word as well though, so the worry of it having spaces in there

i think it might be a whole lot easier if i just make this an #alias and pass it @target
it won matter if it evaluates immediatly that way

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

This worked when I tested it. If you're trying to add multiple items to "dostuff," however, you'll need to use #ADDITEM instead of #VAR.

Posted: Sat Feb 03, 2007 3:18 pm

do you have @dostuff as well as the #FORALL call in another package to mimic my settings?

when i want mutliple items in @dostuff i just declare it as an array just like your definition of @un, no need to go into #ADDITEM if you know all the members before hand, its more useful for inline creation

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I did not put the variables in another package or module, but I think I can help with that, too. Make sure you have the package with the variables checked on the list of "Packages enabled for this package" in the package where your aliases are stored. Select the package in the tree view and you'll see the list of packages. You'll always want to make sure the package with the variables is published globally and not just locally.

Posted: Sat Feb 03, 2007 5:14 pm

Posted: Sat Feb 03, 2007 6:38 pm

Yes, both packages are checked as enabled for each other
@un and @ target are in the 'Combat' class of my main package
the other two are located in the 'FE Mimic' Package available in the package liabrary, which is set to be global.