Zugg Software :: Search

It might be a permissions issue, it might not have access to write to that folder.
Did you ever run CMUD as admin?

Are you using the same syntax? Cause with %concat it is treating the full path as a string, which is why the space gets preserved

i often find i have to use %char when dealing with single and double quote characters you want in a %concat string, which you will need to cobble together your %mapquery string with variables

Som ...

I can't replicate this locally to address it.

are you sure that package is infact included in your session to be loaded?
if you edit the session it should be on the list under the packages tab.

If it is there, then go to the advanced tab of y ...

CMUD Mobile would sweep the market...

Then my next guess is a corruption issue.
Under the file menu of the settings editor you can export your session settings to XML, prior to closing CMUD and deleting your session.pkg file.
And then ...

Does the little gun icon in the lower right (by the clock) have a red x through it?
That would explain it and clicking it would turn them back on.

It sounds like you might be on a new system.
Did you make sure to run CMUD as an Administrator at least once?
This will ensure the program has write permissions so you can save your personal setting ...

if the value for those increments is 0, they don't show
this is expected behavior

Stand-alone antivirus software is often more trouble than it's worth these days, so yes, it well could be.

I would just insert the carriage return client side instead.

Something like this should work:

<trigger priority="10" newline="false" prompt="true" id="10&qu ...

That adds no new information.
You are overcomplicating things.

There is no need for you to use both %ismember and %match here.
One or the other will get the results you seek.

also, remember to ...

or give it an ID and toggle it on and off as needed with
#T+ ID
#T- ID

ditch all the quote marks, you only need those when passing a string, you want these values to evaluate
also, you only need %ismember, %match essentially expects a trigger pattern, which you arent pr ...

Could just toss the pipes back in as literal characters, might need to escape them out ~|

Unless you have a table with a similar output, you might be able to simplify to a single trigger state

<trigger priority="544960" repeat="true" id="54496">
&l ...

The magnifying glass will send a #LOOK command, to reset the room description (if the map is in mapping mode).

The binoculars send the #FIND command, which will try to match the output of a 'look' ...

Try using %cr instead of <BR>?

Not crazy at all, you can even do it in-line:

#TR {(your special phrase)} {#SUB {<send 'default command|command2|command3' 'mouseOver|titles|are shorter'>%1</send>}}

I'm not sure how that is adding anything new to the problem?

Where the other variables get declared, doesn't matter, so long as the values are correct at runtime. (which you can test with #PRINT)
...

right click in the main window
window options
show command line

skxprd=(@skxprd+@gxprd)

Would be doing what you expect.

If you add two static values, the sum will stay the same every time.

Are the two values supposed to be changing?
You didnt give any triggers to show how.

Not enough information to go on.

Honestly, i think thats just a quirk of the ansi coloring system.

Have you tried migrating to MXP?

#SAY <color gray>This is gray</color> <color green> This is some green with a ...