Normally, when I'm bashing or fighting in small groups, my CMUD system functions perfectly. However, when I get into big raid combat, it shuts down. I can't input text, fire macros or view any gauges or windows other than the main text window.

Anyone else have problems like this with CMUD? Any solutions?

It's the spam. cMud is notoriously slow, and it can't parse all the text in that time.

Well, that won't do. Is there a way get around it? Or do I need to switch to something else? I really don't want to do that, because i have a ton of time and effort invested in this system.

I'm sure other people use CMUD for raiding, right?

Hmm, think it could have something to do with using WRAPWIDTH 0?

I do that because it seems to make triggers much easier to catch, i don't have to worry about mutli-lines (and i use regex fairly heavily, which doesn't seem to support multiline triggers)

I know Zmud, and Cmud too probably lags when it has to wrap lines.

Test looking at a nexus (Ravenwood/Mother etc.) with wrapwidth 0 vs wrapwidth 80.

The wrapwidth 0 does make it slower, but even with wrapwidth 80 it can have issues executing a lot of code in a short time. This is the number one reason I switched to MUSHclient (after having invested several months into porting over everything I had from zMUD to work in CMUD). I haven't regretted the switch yet.

I also used to exclusively use cMUD, and put a pretty horrifying amount of time into building my system on it. As it became anything worth using, however, cMUD became incapable of executing the code at a useful rate. I switched to MUSHclient and am really not looking back.

(P.S., Treant is good for MUSHclient if you need a system before you start work on your own.)

I took a look at MUSHclient, and I have to admit I have real reservations regarding using it. The text doesn't seem to render cleanly, for one, and the default settings are ... ugly. I also don't really like the menu system, it feels cluttered.

But, I want to be a combatant, and cmud's horrible lagging issues basically put me out of any of the raids. So: I'll open up a new topic shortly asking for advice on new clients.

ugh... and I have about 150 hours of coding on utility scripts alone... (better printing of pipelist, defs and such)

MUSHclient has an antiquated interface, true. And, Nick keeps adding new features and then sticking them in some rather odd places. Most of us programmer types are not so good with proper UI development, so he did the best he knew how.

Not sure what you're referring to with the text not rendering cleanly. It looks much better for me in MUSHclient than it did in CMUD.

I've started working on a beginner's MUSHclient web page, if you need a few tips on getting started. I'm also available via e-mail for additional instruction.

does Cmud have speed issues, even if you enable and disable trigger classes?

I thought the whole point of Cmud was a faster version of Zmud....

That would be interesting to try, though the only time I've had issues is during raids... at which point I really do want my system on.

cMUD has a lot of speed issues IMHO, if you're making a combat system and want to be combat ready all the time. Enabling and disabling triggers doesn't help that much when you've got a full curing system in place. MUSHclient wins out.

I agree that it doesn't look as fresh as cMUD, and that it's hard to get to grips with straight away but it is WELL worth the change in the long run.

The idea behind it , is that the system itself handles which classes to have turned on or off.

Like all your triggers based on diagnose. Those can be turned off untill you type Diag.

Or all the triggers you have that are just meant to deal with mob afflictions, those can be turned off during raids.

The triggers you have to deal with spars and your own guild set, those can be turned off during raids. etc.

I actually miss TinyFugue... when I was running it on linux it was awesome.

Eh cmud started off really fast for me. After a particular patch though everything sort of went to hell. I have a dinosaur age computer and even with only my forging reflexes enabled there are occasional 1-2 sec hiccups, noticeable because 5 different clan says happen all at once.

I did a lot of that sort of thing in my combat system, and it made no notable difference. CMUD just ended up being slower than zMUD, despite all Zugg's (and my) efforts to make it faster.

It's my belief that Zugg did too much with threading in the script engine and it just ends up thrashing with too many context switches for the tiniest little script executions every few milliseconds. He built himself more overhead than anything.

Anyone able to search the zuggsoft forums to find out about the lag issue? I'm not having much luck.

I did quite a bit of searching on it, and wasn't able to come up with anything. I think it's an issue that mostly comes about with the IRE games, and in particular with Lusternia, because I don't think I've ever played another MUD that will present you with the massive wall of text that is raiding.

Huh. I've never had any speed issues with CMud OR ZMud, but then I'm running them on a quad-core 3GHz processor.

Edit: Gah, accidental necro. This is what I get for browsing while tired. Sorry!

Not to perpetuate the necro, but I think it's fair to say I was running cmud on a quad core (3 ghz) with 4 gigs of 1066 ram. It wasn't the computer slowing cmud down... i think it had more to do with my usage of events.