Zugg Software :: Search

From the lack of responses, it seems likely that noone knows. Let us know if you find something that works, it might help the next person.

Why play with the colors at all when you don't want to change them.
Vijilante wasn't suggesting you should turn off the colors, he was suggesting that since the colors you want are the colors which ...

If the %colorname colors don't mix with the standard colors, then don't mix them. Decide which you want to use and do all your triggers one way or the other. It might require a lot of work now to conv ...

Apparently ; isn't being processed correctly. Just replace all of them with new lines.
#TR {^You have (%d) to spend on stats} {
#MATH XPincrease {%1 - @XPtotal}
#VA ...

What Matt is saying is that you need to put some kind of delimiter, such as double-quotes, around %1 in the #IF conditions. Otherwise, if %1 is longer than one word (contains spaces) then your #IF con ...

#ALA *600 {xprate}
#TR {^You have (%d) to spend on stats} {
#MATH XPincrease {%1 - @XPtotal};#VAR XPtotal %1;#SAY {You have made @XPincrease xp in the ...

Actually, you could use a simpler pattern. Both * and %1 match anything, so they aren't needed at the beginning or end of a trigger Pattern unless the portion of the line they match will be used in th ...

The #STATUS line may or may not work. I tested it in offline mode and it wouldn't update the status bar.
The status bar doesn't update when system variables change. It only updates when user variable ...

I think the 'atconnect' alias is what you want.
#AL atconnect {Connect %char %pass}

The #CW trigger which comes last will set the color you see. To revise the order quickly, just delete the @1 trigger then remake it.
#UNTR {@1}
#TR {@1} {#CW 12}

Just put double-quotes around the extra spaces.
%ansi( white)Armor : %ansi( yellow)@armor
%ansi( white)Shield: %ansi( yellow)@shield
%ansi( white)R ...

It appears you had an "unattached" command line. The probable fix would be to right click the window and then select Attached Command Line from the Window Options submenu. It can also be controlled fr ...

This is similar to many other 'errors' the syntax editor reports. There's nothing wrong with the syntax but it's not what the editor expects. If you rely on the syntax editor to do your syntax checkin ...

#VAR lv 0
#LOOPVIEW {#ADD lv 1;#IF (@lv > 2) {#VAR lv 0;#SHOW &Name} {#SHOWP &Name}}
You'll need to set @lv to 0 either before or after the loop, so ...

Yes, results of functions are usually sent to the MUD and they usually don't change a variable's contents directly. Functions just return the altered value, if you actually want the variable changed t ...

Make sure you have at least one item in each variable. If one of the variables is empty, anything with the same ending will match.

Very nice!

Is there anything different in the Preferences of those two characters? It is quite odd and I'm grasping at straws hoping to find a solution for you.

Yes, I did test it just not as exhaustively as you did. I used the precise line you complained about in your original post:
goss let's try it again with & and % and " and such
What it sends:
&a ...

It's probably controlled from the Files tab of the character's properties.

%quote doesn't apply to either single-quotes or double-quotes.

Instead of trying all these tricks with user functions (scripts inside variables), just put the color-selection into the alias.
#AL g ...

No, you won't be able to do this with #SETPROMPT. You'll have to make a trigger using #TRIGGER. You can still use #SETPROMPT if you want, the only command the trigger has to have is
#T- Cap
That com ...

Functions use parentheses (), not braces {}, around their parameters, and they don't have a space between the function name, %pos, and its parameters.
#IF %pos("long ", %1) {look}
NOT
#IF %pos {"l ...

#var timeqc %eval( %eval( 60 * %eval( %time( nn)-@QSMinute)) + %eval( %time( ss)-@QSSecond))

First, you need to replace the #VARIABLE command with the #FUNCTION command in the above statement. Othe ...

Yes, it's always better to give the real problem. I believe this will do the trick.

#TR {Teleporting...} {#CO WHITE;#VAR RoomName ""}
#COND {(*)} {#VAR RoomName {%1}} {LoopLines|Param=1}
#COND { ...