I've started to modularize my system, and part of this is creating one trigger for each common event (prompt, balance regains and such) then raising an event that other modules can simply declare.

Does anyone happen to know if the event system has any hangs or slowdowns? I imagine it has to be faster than running several redundant triggers.

Your mileage may vary, but I abandoned my CMUD system because it was so slow it was unusable, and I implemented a fair number of events across several packages to make it as modular as possible.

You use MUSHclient now, right? I've never had problems with CMUD being slow, to any degree. But I have a bleeding edge machine I built myself for speed, which probably makes a difference.

Slow software can potentially run slow on any machine.

But Forren built his system on CMUD, and he did great with it, so I have to assume there are ways around the speed issues.

Object oriented design is great, but I have never taken that path with a MUD combat system, mainly because I'm afraid it will cause speed issues.

Yes, I use MUSHclient now. The main difference, for me, between MUSHclient and either zMUD or CMUD is that there is much less of a need (in MUSHclient) to optimize your own code for speed. I had to work around quirks in Zugg's clients and was always looking for a way to do things quickly but still in a way that could be easily adapted and maintained. I just didn't strike that balance with CMUD and I wasn't willing to invest another month or two reimagining my design to eek out enough performance.

Fair enough. I know a lot of people are very partial to their clients. I actually really liked tinyfugue for a while, but now that I'm on vista (rather than linux) most of the time, I've come to like the way cmud works.