Zugg Software :: Search

ok really stupid question. is their a code that can take a variable, record its value so so permenantly stored somehow but still allow the variable to change? kinda like if the varaible is a countin ...

Very cool. Regreatably the remove buddies doesn't seem to work. it also does the show buddies even if it isn't a buddy that logs on.

Ok Basicly what I'm trying to is create a buddy list built right into zmud.

What I need is a way that the user to can add a person to a list of other people.

EX add player3 to buddy list
This w ...

I'm having some trouble with my attempt to making shoping easier. This seems to be bugged. Quickshop looks like a very easy code but yet sometimes it doesn't seem to work at all.

^quickshop ( ...

that keeps the alarm from moving to a different folder but the xptimer data record is still making a copy of itself in a different folder.
**EDIT**
correction. the data record starts copying itself ...

I've imported it several times and always get the same results. On the randomness it saves to one of 3 subfolders but they have absolutely nothing to do with the script. Cost is a mud command for di ...

Seeings there was no nibbles to assit useing that I figured I'd display the full script to see if that would be helpful. This is what i imported in.
#CLASS {xptimer}
#ALIAS showxp {s ...

First off I take no credit for this script to monitor xp made on merentha. It was given to me by a friend who said he had no problem with me playing with it in an attempt to improve it.

My problem ...

the sytnax is give bag # to yourself. the problem is if bag 1 and bag 2 is full i need it to give me bag 3

I've been kicking around the idea of createing a code that will swap bags of holding until i have an empty one.
when you look at a full bag you get this message

bag of holding is about 90% full.
...

alright cool. thanks for the info. I'll try to fix that up and see if it doesn't help.

Why does zmud save newly created variables into random class folders? Is there a setting I'm not aware of that I can change and if so where is it? On occassion I've noticed that if i move the variab ...

nm found the problem elsewhere.

Well no real complaints about the code but there seems to be a minor problem. The trigger never stops applying salve. any takers?
#Class automatedhealing
#TRIGGER "The salve seeps into your s ...

#TRIGGER "ms_salve" {^The salve seeps into your skin and slowly heals you. } {#NOOP do nothing}
#COND {^The salve seeps into your skin and slowly heals you.} ...

#TRIGGER
{The salve seeps into your skin and slowly heals you.$The salve seeps into your skin and slowly heals you.} {dostuff} "" {within|param=2}

Throws me into a giant loop which displays just ...

You should enter this script into the command line (where you type mud commands) and hit enter.

The #IF outside of a trigger will only work the first time it is sent.

#TRIGGER "ms_salve" {^The s ...

Fair enough
under the Position/Size tab uncheck the box for Auto Size. Any time you change a gauge that has the Auto Size check boxed checked, every other gauge that has it checked will resize as we ...

Nexela's should work. And, is that a typo in the #COND command or were you really trying to put an #IF command outside of the code block for the #COND (obviously, a trigger wouldn't work in that case ...

Neither one of those seems to work... Crying or Very sad

So something like this?
Useing The salve seeps into your skin and slowly heals you as the pattern?

#TRIGGER "ms_salve" {^The salve seeps into your skin and slowly heals you. } {#NOOP do nothing} ...

Is it possible to only make a trigger fire of if two lines are recieved from the mud. The lines are identical.

The salve seeps into your skin and slowly heals you.
The salve seeps into your skin ...

Best suggestion I can give is very similar to Matt's. Use your prompt trigger to apply your salve and set a variable to indicate that you must wait to apply again. Then use an alamr to clear that va ...

Wow while effective it causes other problems. Useing the Alarm off the prompt will cause the trigger to fire even when I'm in combat which is something I want to avoid. Useing when the mob dies fire ...

hmm. No luck. it still just spams apply salve a bunch of times. any other ideas? It's like it doesn't use the wait or calculate how many times to loop it properly.