Just looking through the system now, seems easy enough to set up. As a system builder i can say this is pretty user friendly, good on ya cat for offering it free. I'm gonna try it out for a little and see where it needs improving/customise it to the standard I like.

Hrm, regarding my other post, I now tried connect to lusty directly (bypassing mudbot), doing atcpon, and trying to get the sipper working that way... As with atcpoff and normalhp enabled, the health/mana/ego values are updating in the Current** variables... and the atcp folder is enabled with normalhp disabled... everything looks right except for it actually sipping. So I'm at a total loss as to what my problem is.

Has anyone else experienced this or might have a clue as to why it wouldn't sip when current hp/mp/ego drops below desired hp/mp/ego?

I've had sipping problems, but i havn't worked out why yet.
Often in zmud this problem would be caused by it not recognizing your prompt or the like.

I was thinking the same thing, but the thing that throws me through a loop is the fact that it does update the current hp/mp/ego values off the prompt, which says to me that it is ok with the prompt. I'm still looking about, but I'm damn horrible at running around in CMUD still.

I'm not healing at all now actually... if anyone has any ideas pleas let me know.

ok new question.

Which triggers should I be looking at wich initiate the "do you need to be cured or healed?" events.


My system is adding afflictions and changing health variables, but never doing the actual curing.

edit:

also, when I change marry mode, are my parrys supposed to switch, or only after I get hit?

From what I can tell, in the Health Sipper folder, under NormalHP (if you use mudbot and have atcp off), the trigger prompt is ^&%d{CurrentHealth}h, &%d{CurrentMana}m, &%d{CurrentEgo}e, &%d{CurrentPower}*-$ It calls setHealthLevels, which does the health maths, and if hp/mp/ego is lower than desired, it sets off MasterHealthAlarm. There is a MasterHealth function there, it's a conditional in which the first one is (@CurrentHealth < @MinimumHealth && @SipHealth()) {healthsip} ... and indeed there is a healthsip alias that sips health and sets lastelixir and hptry variables...

So, I think that answers your question... however, none of it is working for me, either. Everything logically looks right, but it doesn't work. Dunno.

I don't have mudbot, should atcp be on or off?

Thanks I'll play around and see if I notice anything.

If you don't have mudbot, atcp on is fine according to the instructions.

I have noticed that the @blackout and @lastpercent variables are red... which normally means they don't exist.

That may be the problem?

allright, I've isolated the problem to the fact that masterHealthAlarm never gets called or activate.

Any suggestions?

Here is the trigger in xml format:




when I rightclick on the trigger and choose "execute script" it works wonderfully.

Edit: while reading up on alarms, I saw this.


What does that mean, and does this affect this system at all? Thanks

Still not sure what masterhealthalarm isn't going off... as far as the threads thing, it just means that CMUD runs alarms concurrently, one on each thread, meaning that one being active doesn't hold up anything else.

The infamous zMUD thing was that zMUD was written to run on a single thread. If you put a #WAIT 5000000 or something, it would prevent other triggers and such from firing until that wait was done. In CMUD, you can have things running on different threads, so nothing is held up. So really... this should help the script, not hurt it, though I know that once you start going into multi thread realm, coding gets a lot more complicated.

I haven't figured it out.

The first time I got it working (I think, the prompt defs were colored red). It was working while I had CMUD running.

After I closed the program and opened it later, it wouldn't work anymore.
I deleted the session and package associated with it and remade both, but now I can't get the triggers to work anymore.

Anyone have a similar kind of trouble?

I had the same problem actually. For some reason after the first time, took me a while to narrow this down, I went through everything to check it, so much wasted. Not sure how to fix this, but until now I thought it was just me who had the problem. It looks like the AddAffliction event and the others I think, dont properly activate the alarms, so they don't fire, and thus don't actually work. Or it could be something completely different.

While I haven't tried Catarin's free system (just looked at it), I can say that I have problems with CMUD myself. The client has become more stable than previous versions, definitely, but it's still got a few underlying issues that can lead to serious problems, such as settings being disabled inadvertently or things just not compiling/parsing/firing properly. It's very annoying, and it's the biggest reason why my new system still is not finished and ready to use.

Yeah, it's kinda annoying. I know zMUD is a bit archaic in how it handled things, but I'll be damned if when I put some code in, I knew exactly how zMUD would react. I don't have that confidence with CMUD, and it's a shame, since there are some pretty neat sounding features I'd love to exploit, but can't afford to waste my time on if I won't get a return on it. If it's a script problem, I don't know what it is, but it could be a CMUD problem, in which case I'm the wrong person to be solving it... well, actually, I'm probably the wrong person in either case.

Any suggestions on how to formulate the question within the CMUD forums so it gets an educated response?

Thanks.

Me mashed the buttons and none worked. Why for?

Probably not, eh?

Actually, I remember that I think I broke CMUD when I did a trigger. It's been such a long time since I've used zMud/CMUD (Mushclient all the way), and I tried doing a trigger that echos my target.

Apparently I got a crazy loop thing that busted CMUD, so I un-installed and re-installed, and now it works fine.

it is definitly an instalation problem, and not a system problem because my packages work on other peopele's computers.