Zugg Software :: Search

I would use a string list of the breaths you wish to compare to .. <$desiredBreaths = "Fire|Lightning|Sound|Force>"

then a Regex for .. ^>\s(\w)\s[#]\{,50}
#IF (%ismember(%1,$desiredBr ...

Would an alias for a #SW be enough?

<aliasname> (%1)

@numVar = %1
#SWITCH (@numVar)
(1-1) {@numbers = "one 1-1|two 2-2|three 3-3|four 4-4|five 5-5|s ...

<trigger priority="14850" regex="true">
<pattern>^(?:>\s|)(You tell \w+|\w+(?<!YOURPET) tells you|\w+ LTs $.+$|You LT \(.+\ ...

the #SW code would go in the body of the trigger that is capturing the attempts.

#TR {You nearly rip %* in two with (%*)!! ~(%d~)} {#SW {%1 = your deadly corrod ...

using () should expand the variable if i recall correctly... but why you want todo this escapes me.

copy an example of your gag'd line and in the trigger on the wizard tab you can paste it to test if the prompt matches... will help figure out what's going on. could be a un-counted whitespace.
...

Look into #SWITCH You should be able to have a generic 'capture' prompt and eval that capture to the #SW potential results to +1 your wand, and when no match is found do nothing.

#MATH is depreciated you can just use () to eval

try

$AABB = (100/50)

#SHOW $AABB

I recently had a same-ish issue but it was with mouse and not program. single clicks was reading as dbl or wouldn't hold so drag-n-drop was nearly impossible.

I'd look for something more like "Obvious exit(s): east, north, etc, etc"

it shouldn't 'break' but wouldn't fire off as no match would be found. Again without a few samples of in-game prompts it's hard to offer much. Hope the method helps find your solution :)

There are several way to go about this, but having some actual in-game descriptions from 'x corpse' or like outputs to refine the options.

personally, I would look at $relevantComponents = "compo ...

Start with each line and do a #SHOW so your first line $newarea=%gmcp.Room.info.area test with #SHOW %gmcp.Room.info.area if this does work then you can move to the next line. should help figu ...

Personally I would set a variable [ Blacklist = Multi_name_1|Multi_name_2|etc|etc ] specifically for the chars you want captured but not sent to the chat window. This will allow your capture trigger ...

#TR {An (%a) switches and hits * hard|very hard!} {grapple %1}
#TR {An (%a) pummels * hard|very hard!} {grapple %1}

assuming MULTI1 is a potential list of targets as well...

Look into #step #pause #resume I used to run a bot that would start and follow a speedwalk using those commands to nav through rooms, check for mobs, kill if present or move to next room if no mo ...

https://i.imgur.com/ectXFkQ.png

here's an example of how it looks for me... main mud window is on left, chat captures are upper right, and lower right is my tracked status variables.

Sorry it's ...

close your coloring with %reset()

#VAR shield %ansi(bold,cyan)ON%reset()

usually I just set my color in the status windows code and not embed in the variable, this could lead to issues with rea ...

out of curiousity, how long do you leave cmud running at any given time? Do you save and close the program periodically? I have noticed that dupe vars and mis-firing scripts will occur with variably ...

As Tarn said. Use "#LOCAL {tempVar}" then reference it with $tempVar

if you don't define it with #LOCAL it will dump the tempVar once the inital {script} is closed, so any further calls on it wil ...

Shalimar advised me on a floating script a few years back, and had said you pretty much have to always use #.00 for it to function.

in fact you had commented on that exact thread "I suck at math" ...

for on/off states I tend to use boolean (if that is the correct term) 1/0 so (@autosc = 1) {on} {off}

Sadly this is an issue with my settings to... I find it does it more frequently when I am enabling/disabling classes that store said variables.

My solution was to migrate to DBVars " charData.Var_ ...

#TR {Gigantic %n Force ~((%n)~) - %n ~[ ~]} {#PRINT %1}

should do the trick.