Zugg Software :: View topic

Posted: Mon Feb 25, 2008 1:48 pm

Hi, I've been using this script (Meleecolours) for many years, but now it suddenly won't work on ZMUD 7.21. The colour changes that would normally occur are not output by the client any more. I've looked over it many times but cannot see what is goign wrong.

Can anyone help me out by trying to spot what the problem is?

Many thanks in advance :)

#VAR Attacks {tickles|hacks|slashes|scythes|strikes|smites|pounds|stabs|pierces|cleaves|blasts|hits|lances|crushes|shoots|whips|stings|slices}
#VAR Attack2 {tickle|hack|slash|scythe|strike|smite|pound|stab|pierce|cleave|blast|hit|lance|crush|shoot|whip|sting|slice}
#VAR bodypart {head|body|left arm|right arm|left leg|right leg|left foot|right foot}

#TRIGGER {{@Attacks} your {@bodypart} into bloody fragments} {#cw red}
#TRIGGER {{@Attacks} your {@bodypart} extremely hard } {#cw red}
#TRIGGER {{@Attacks} your {@bodypart} very hard } {#cw red}
#TRIGGER {{@Attacks} your {@bodypart} hard } {#cw red}
#TRIGGER {{@Attacks} your {@bodypart} } {#cw red}
#TRIGGER {barely tickles your {@bodypart} with * {@Attacks}} {#cw red}
#TRIGGER {tickles your {@bodypart} with * {@Attacks}} {#cw red}
#TRIGGER {barely {@Attacks} your {@bodypart}} {#cw red}

#TRIGGER {You {@Attack2} * {@bodypart} into bloody fragments} {#cw green}
#TRIGGER {You {@Attack2} * {@bodypart} extremely hard} {#cw green}
#TRIGGER {You {@Attack2} * {@bodypart} very hard} {#cw green}
#TRIGGER {You {@Attack2} * {@bodypart} hard} {#cw green}
#TRIGGER {You {@Attack2} * {@bodypart}} {#cw green}
#TRIGGER {You barely {@Attack2} * {@bodypart}} {#cw green}
#TRIGGER {You tickle * {@bodypart} with your {@Attack2}} {#cw green}
#TRIGGER {You barely tickle * {@bodypart} with your {@Attack2}} {#cw green}

#TRIGGER {Your bash at * sends * sprawling} {#cw green}
#TRIGGER {Your boots need polishing again -- blood all over...} {#cw green}
#TRIGGER {Your kick hits * in the solar plexus} {#cw green}

#TRIGGER {sends you sprawling with a powerful bash} {#cw red}
#TRIGGER {You're hit in solar plexus, wow, this is breathtaking} {#cw red}
#TRIGGER {wipes * boots in your face} {#cw red}

#TRIGGER {You gasp in pain as streaks of fire from * burn your body} {#cw white}
#TRIGGER {Your body is pierced by razor sharp ice spikes sent by } {#cw white}
#TRIGGER {The air around your eyes seems to catch fire, blinding you} {#cw white}
#TRIGGER {Arrrgggh!!! Your body is on FIRE! You have precious few moments to save your sorry life} {#cw white}
#TRIGGER {calls lightning from the sky to strike you, sizzling your insides} {#cw white}

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I have 7.21 and sometimes my settings creates #CW triggers for the color names themselves. I had assumed it was that I had made a set of #CW triggers that fire without defining %1 properly, but could not find the alias or trigger that was making the wierd #CW triggers. I still think it is me, but if your code stopped working midstream that is very uncomputerly. I would think it was something outside the script. You might try a new session, or look for duplicates? Could it be a new script you added that seems unrelated? Maybe it is a quirky #CW afterall. Having triggers on color names can be eerie when they return black color data. After hearing this, the next time it happens I will better focus on the problem with my code to see if it is me or not. Thanks.

(I could not find any script that made CW triggers at all at one point, but that only made me think I was not searching well)

Posted: Tue Feb 26, 2008 11:15 am

I think I was unclear. This script used to work until I upgraded/installed 7.21, but now it has ceased to execute properly.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I'm not seeing a problem. Could you try these out in a blank session and see if they still fail?

To get a blank session hit the escape key at the sessions menu.

Mind that I had to get rid of some of the new lines when I entered the triggers. But on a quick run through I didn't have any triggers fail. [I did not try them all.]

Leitia almost appears to be drunk when posting of late but the advice to look for new triggers that could be causing the problem is usually sound as well.

So what version did you upgrade from? Perhaps that could give someone a clue where to look next provided that it works for you in the blank session.

Posted: Tue Feb 26, 2008 8:24 pm

This is weird.

Tried it in a blank session and it worked, so tried it again in the session and it now works apart from 3 triggers (which work if input seperately)

#TRIGGER {Your bash at * sends * sprawling} {#cw green}

#TRIGGER {sends you sprawling with a powerful bash} {#cw red}

#TRIGGER {You gasp in pain as streaks of fire from * burn your body} {#cw white}

appears when i input that entire list, but then if input seperately they work.

Ah well, it works now so thanks. Guess something got reset along the way :)

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

The weird trigger on color phenomenon appeared in a session I am using for offline work.

TRIGGER {pink} {#cw show}

I did not make any #CW triggers but may have inadvertently told the puter to do that using random letter sequences for testing. This was the only thing similar I found:

TRIGGER {pink} {#cw show}

#sh xxx show %i
#co pink

%i can look like this literally <%i> and subbing that with anything to make the trigger, no clue how that is possible.

These are kind of funny, this trigger will blot out any mention of pink in descriptions and messages. Looking at that moniker I thought oh, that 'xxx show' could have connotations; though any Freudian definition or implication should be considered against my constant use of x y and zs for flow charting.

meep

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

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

I wasn't trying to make a trigger, it happens sometimes these ones on color names, but I could not find a trigger that makes a trigger, nor do I make any trigger in an alias, or have I used #CW in this session. I wouldn't want that trigger if it was correct, but it's an annoyance.

I suppose when %i came down somehow it executed a function, or under some null set of circumstances a new unwanted function is created. Or simply I don't see the thing, but I have looked a lot

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

#CW has a certain syntax that automatically creates a trigger with the #CW in it. It can be easily done via the command-line. I forget the order, but it's in the helpfiles. Basically, you just specify the pattern as well as the color:

#CW show pink

If you have the parameters in the wrong order, the trigger still gets created but now the color word is the pattern and the pattern is now the color. Because it's an invalid color, it defaults to black.