Zugg Software :: Search

How are you setting the @NextQuest variable?

Edit: Waaaiiiit... it's a variable of type integer but you're assigning a string value ("Test") to it? That doesn't seem like it will work.

Yes, you need to enclose the events to occur after the #WAITFOR in {brackets}. First set of brackets is commands to perform when the condition is met, the second set is for when the condition isn't m ...

Okay, from my own experiences with #SHOW, it displays text as though it was sent from the mud, so it's vulnerable to #GAG commands. I never really played with #SAY.

My own experiences with #GAGgin ...

Wow, I'll take a look at this after I have some coffee. Long night last night. ;)

You shouldn't have a problem if you paste in the code I posted above... it works just fine.

edit: Never mind, I guess you can't #CALL two functions inline... I added two more #CALL commands to per ...

Oh, you may have to go into the button options tab to tell it which toolbar to display on.

Create a new button, then click the XML tab at the bottom and copy the XML above into the text editor and save it.

Be sure to get the most recent copy that I posted, I made a couple minor changes.

Heh, you could combine both of these for the dynamic button coloring as well as on-screen messaging.

edit: change my code posting to add on-screen messaging.

<button name="ThumpButton" transparent="false" color="navy" textcolor="white" priority="1510" id="151">
<caption>Thump!</c ...

Okay, the new code works though I'm baffled that my deaths window works with a similar format. Thanks!

The @ThoughtSender variable is created directly in the trigger pattern - "You hear the {faint|quiet} thoughts of &ThoughtSender echo in your mind:"

I *just* started converting my package to CMU ...

I'm having an issue with a script I converted from zMud to CMUD... the scripts intent is to catch a two-line output, gag it, load variables, and send a one-line output to another window.

<trigge ...

New release, moved topic: http://forums.zuggsoft.com/forums/viewtopic.php?p=137727#137727

I've released a new codebase for my ZMud client, now renamed to Citrus. This release addresses a lot of bugfixes and requested enhancements. This setup requires no central server (like PsiNet) as da ...

I am having trouble with your RT count down, unless i am typing alot to get alot of mud imput, its gauge just doesnt move.

I use the following to work around it:

#ALA -1 {#IF (@roundtime) {#ADD ...

I'm having the same exact issue. Would have been nice if he posted his configuration. :)

Thanks! I'll update this for testing in zMud.

That's strange. Is it ZMud or CMud? I've noted that on CMud the gauges don't update until there is an update to the game window. I've never had an issue in ZMud, however.

If you have the exact text from the act of purchasing influence, you can make a trigger to call this alias, too.

If you want to check for EITHER stat being less than 80% of full value, use the following:

#IF (@hits<@maxhit*.8 OR @mana<@maxmana*.8) {lay hands}

Swap out OR for AND if you want them BOT ...

Show us your existing code, please?

I took this and cleaned it up slightly, and changed the trigger a bit for GSIV.

#TRIGGER {^In the (*) you see (*).} {
TempContainer={%1}
TempContents= ...

Coincidentally, this should work too, with only one trigger needed:

#TRIG {cexkdb~-%1~-~-} {#SUB {cexkdb~- %eval(%len(%1)*20)~-}}

Maybe a #TRIGGER and #SUB for each variation, only using the end of the line...

#TRIG {cexkdb~-~+~-~-} {#SUB {cexkdb~- 20~-}}
#TRIG {cexkdb~-~+~+~-~-} {#SUB {cexkdb~- 40~-}}
#TRIG {cexkdb~-~+~+~+ ...

Thanks, ralgith. You inadvertently helped me format a 2-line "tell" situation into a neat one-line deal with a timestamp.