13 is up. I'll update the site download later this evening (along with ubuntu ppa), but meanwhile mac and windows versions are here. (note: when using the mac update only, apparently you have to "delete mudlet.app in the application folder prior to installing the app only package").

Mac version should be usable now - text selection/copying has been fixed.

Having just downloaded OpenSuSe 11.1 64bit to play around with, I've encountered the same problem everyone else has with Treant and MUSHClient, trying to install Treant into MUSHClient crashes it for some godforsaken reason How difficult would it be to convert Treant (it being a lua system) from MUSHClient to Mudlet?

Would take me about a year, probably. (No, I'm not interested enough in Mudlet yet to convert 50,000 lines of code!)

I've been playing around with mudlet, and I'm finding that the documentation and API just aren't good enough yet to build a complex system. There seem to be a lot of features in the client that aren't properly documented, and it's hard to get the motivation to start converting stuff over when you know you'll find an awesome function a week later that nerfs your hour of work now.

Edit: that said; I'm glad that I took the time to build abstraction layers into my system. When/If I decide to switch over to mudlet, the system conversion should be pretty simple. It's the triggers that will take a while.

I still find the Mudlet UI to be rather unintuitive and klunky.

Pointers on that would be great, as I find it to be way less complex than MUSH's and am aiming it for it to be intuitive.

Certain interface improvements are queued for the next releases too.

When I see Mudlet's settings dialog, I'm expecting something a little more akin to CMUD's settings dialog.

• It makes little sense to me that I have the trigger patterns under the name and send plain text (why isn't this just one "send" box, whether it be script or sent to the MUD?).
• Selecting certain things in the left treeview is quirky. There should be a stock form displayed when you select something that isn't a trigger/alias/etc.
• It's also quirky when you're looking at one type of setting (clicked on Triggers) and then you hit something else on the add dropdown menu (Alias).
• The XML format isn't as friendly as CMUD or MUSHclient.
• The buttons for the color changes (global settings) have a very thin border of the color around a silver 3-D button (on XP).

I'm sure I could come up with more, but I haven't got the time or energy for any serious beta testing now...

I agree that the UI is a bit lacking at the moment. Mudlet uses wxWidgets, right? If that's the case, some of that issue probably stems from the fact that wx isn't the greatest way to create a friendly UI, in that you have to make it look good across all OS's widget kits.

I do like that you can have multiple patterns per trigger. I think that's a great idea, because often times I have multiple triggers that do exactly the same thing. Now I can group the trigger by affliction and drop all the main and secondary pattern lines into it.

Of course, in all fairness, MUSH's interface is about as antiquated as they come, and I've never liked that you can't group sets of triggers together in a tree menu. Both have their strengths and flaws in my opinion, at the moment.

I want MUSHclient's speed and power combined with CMUD's GUI and user-friendliness and Mudlet's cross-platform capability.

I thought they were using Qt, not wxWidgets.

This is how I see it:

speed: Mudlet > MUSH > CMUD
features: CMUD >> Mudlet > MUSH
ui: CMUD > Mudlet >> MUSH
community: CMUD > MUSH >> Mudlet
platforms: Mudlet >> MUSH > CMUD
documentation: CMUD > MUSH >>> Mudlet

I believe CMUDs interface is lacking, however Qt is quite hard to work with itself. There is room for improvement interface-wise, but don't expect a cmud clone - I'm going for intuition and that'll be easy to adjust to, and learn as new (I believe).

I believe CMUD's interface is pretty good. The rest of it is lacking.

You need a coding degree to obtain any measure of success... And you people (lusternians/people on the mudlet forums bashing IRE's client) wonder why I use the flash or nexus clients.

For people who didn't grow up in ye olde internet days, the two simplest things are Point and Click (and then type what it is you'd like it to do).

Meh, whatever. I have issues with clients in general, I guess.

Here's a tip for life:

All scripting languages are at least moderately easy. The worst of them (see: non-LUA MUSH) are bad because you're trying to get something not meant for scripting, or scripting in that situation, to do it anyways. You only need to know a few things: how to create the alias/trigger, how to send data, how to store data, how to display data, and how to manipulate stored data. This is something that can be taught in less than an hour for most respectable clients.

The problem is that most people aren't used to thinking in strictly logical, yes-or-no terms. That's something that can't be taught in one forum post. It also makes a strong case for making computer programming a required class in grade school, but that's neither here nor there.

Nice thought, but not the case. I learned how to code basic from reading "3-2-1 Contact" on a Tandy when I was 8-years old (yeah, that dates me). I understand the linear, flowchart logic alright. Yet the language is so so so far removed.

Many times the coding tutorials are written by people who are so immersed in coding, they forget what it's like to be at that step one... therefore these tutorials assume far too much prior knowledge and don't properly scaffold the basic skills before moving onto more advanced topics carefully enough. Not to mention print media doesn't provide the most clarity to disambiguate the confusing parts.

Although the Mudlet manual is confusing as hell for me (and I do read and reread it-- still have no idea about how to properly use wildcards and variables), Vadi went worlds above and beyond with the video tutorials he made. First, he explains how to teach the basics before moving onto trickier skills. Secondly, three minutes of a video-tutorial provides a much clearer model over text.

I'd love to see more, but can only imagine that it takes so much more time to produce a screencast than to write up a tutorial.

Mudlet is so new to the arena. Right now, it immediately addresses the needs of the Mac community who want something more than Nexus, but don't want to get drawn up in the technicalities of running Wine or Tinyfugue. Savitar and Mudwalker have no IRE-based communities, and are therefore limited.

Mudlet is the Mac user's best shot at a powerful client with some sense of community... A larger community and proper documentation is the only way a system (or at least bits of one) will ever be coded or adapted for public consumption.

Mudlet Beta 14 is available: http://www.mudlet.org/download/

This release solves some issues from the previous version. Nice product...

HEY, now how can we get IRE muds (namely Lusternia) to be a featured mud under Mudlet's connect ready made profiles?

I'll add IRE muds in there soon.

Mudlet's community is the best that I've worked with.

I've suggested fixes to Heiko and they've been done in HOURS. No other client has offered me that.

I sincerely hope that the stable version isn't full of bugs.