Whats this supposed to mean?

Do you think a good client means making your users have to code in the things they want directly into the source? Do you think a good client means having a barely any real functionality? Learn some lessons from mush and cmud, then mudlet might be worth a few cents more than fireclient or kildclient.

No need to get so defensive. If you like MUSH, then it's for you. If you don't, Mudlet attempts to make you happy.

In regards to options - we provide the needed ones, not umpteen useless ones that confuse the user. Also stick to the "sensible defaults" philosophy, so "everything works out of the box" without configuration. Obviously, making the user dive into the code is the opposite of what we want.

You didn't even say what are you needing. We aren't looking to make a cross-platform MUSH clone, sorry.

Hmm, I was interested in mudlet, but my interest has dropped significantly without even having used it just from your responses, Vadi.

Making a new program is about listening to your users. If you have a user saying he thinks the configuability is sorely lacking, you ask him what features he'd like to see added, not tell him, "Sorry for you, take it or leave it". Even if you have no interest in adding the features, it's still a good idea to ask, unless the intent is to create a client only you will use.

No, my interest is in adding features - and as you see, the said person didn't even say what he wanted. They just bashed for lacking the options.

Sorry if I came off the wrong way; but unproductive bashing is, well unproductive and irritating. What am I supposed to get from "Mudlet needs about 100 more features for me to be interested."? Post what you'd like to see and that's important to you, and it'll be considered. But I'm not going to bend out of shape to please a high-stuck response.

Do read over it again to see that not a single request was made (if any are needed. All his post says is that the Settings window does not have enough options.) for me to think on

I've used MUSHclient for almost a year now, giving up on zMUD/CMUD for various reasons. I tried Mudlet beta 9-pre, and I found the interface screwy. I must say that the bugs I reported were resolved rather quickly, but it still seems that a lot more documentation and examples will be needed before I have a real sense of how to code anything useful for Mudlet.

Lots of potential there, if you guys can work out all the kinks through some solid unit testing. Just looks to me like another case (and I'm as guilty of it as anyone) of the developer not testing the program in ways it's not intended to be used. You have a set list of things you know you need to do and you stick to that, even though there may be four ways to get the same thing...

I agree with you this is being worked on, but concrete reports (if you have the time) are of course welcome to help narrow things down.

PS. Sorry for the above derailment - we're all very much open to constructive criticism. It's not good manners to bash something that people are making for you, for free, to enjoy gaming better. Gets you down!

Downloaded and installed the Mac OSX beta of Mudlet some while back. Between being over-busy at work, some display issues, and a general confusion about how to setup basic triggers, I shelved the project for a later date. Now that I'm starting my 10-week summer vacation, and updates on the Mac releases... I want to completely tackle Mudlet.

My initial experiences are good. No problems with installation and it runs quickly on my Mac. I already like this way better than Savitar and Mudwalker... Though, I still have some display issues. I am running a Mac 10.5.7 Intel Core Duo on a MacBook. Dunno what the screen width is, but certainly not up to the MacBook Pro widescreen.

Here are the related display issues: I have no icon for the application. The highlight background on highlighted text appears to hang too low... both on the top and bottom. The "system message" has a see-though background... that becomes muddled with my wallpaper. The font size for the commands is miniscule. Also, the popup gui for triggers / alias / etc. is way too wide, and doesn't fit on my laptop. Seems I can't shrink it down as well. I could take a screen shot to show all of this-- just let me know where I can send it.

Secondly, I am still having troubles setting up basic triggers. My only experience is Nexus, and I find Mudlet a little more challenging. Can anyone help me setup one basic trigger and alias to get me started? Thanks!

I'll get Mudlet on my Macbook today and see if I can't figure it out.

THANKS!

Would be glad to address all of this.



In settings -> main display, try raising the wrap width from the default 100. Is that better? If no, please provide a screenshot - and along with all of the other problems you've mentioned. If you can, please file a bug, one per issue, here: https://bugs.launchpad.net/mudlet/+filebug . Or you can just PM me if you're a bit lazy.

For the basic triggers, the user experience there needs polishing. Meanwhile, here's a short vid that describes it:

http://blip.tv/file/2272802/

The video quality is crap, so this link has the downloadable version: http://drop.io/2whbcqm

I'm also making one for making a trigger to send/echo stuffs, uploading right now.

Here's the second one: http://blip.tv/file/2272906/

Hope that clears things up - and further points / suggestions are welcome.

THANK YOU!
THANK YOU!
THANK YOU!

The videos were clear and concise; I had triggers with both send/echo running in about 5 minutes. Very helpful. Next I would like to know how to make an alias and a multi-line trigger/alias. Once I have that much info, I will be able to rewrite all of my Nexus commands to Mudlet.

PS- how do I import/install your sipper?

I just installed mudlet on my macbook & started to convert my system across. First impressions are pretty good!

It's great to see some other users here, I'll maybe make another thread with Mudlet specific Lusternia triggers etc. as I come across them.

I've been using Mudlet for abount... two maybe three weeks now. I love it so far, other than the fact that there's still no reconnect function. Otherwise, it's great!

YES PLEASE! I figure that I will have to code my own system... so anything you can do to help me get started would be a major help!

Added a video of aliases: http://drop.io/mudlet_videos

I need to work out a problem in the sipper where sometimes, after import, it's not always working. Then I'll make a video.

Does anyone else, on the windows version, have an issue where it reprints a line or lines to the screen?

Like, if I do "ql"

It will echo "ql" twice, as well as what I saw twice. But, they have the exact same timestamp (so I know the command isn't actually going through). It will also do this on other things, like if someone says something, or does an action, it will print twice. Not all the time, but sometimes.

I'm not sure if this is some local issue I'm having or a bug with the client.

I've noticed that today also, was wondering if it was just me.

Also, beta 10 pre 12 is now available. With an updated mac installer (but the issues reported by Janalon weren't addressed there yet). List of changes + download: http://www.mudlet.org/download/

@Janalon: how does one copy text on a Mac usually?

Apple-C, If I remember right. Also, "Edit-copy" from a menu in most anything. Usually the keyboard shortcut, though.

Mac is a one button "mouse" click so to speak. Highlight, release, ctrl+ spacebar would be the right button click equivalent. There is also ctrl+ C for the copy hot key. My issue is that I can't even highlight the text to copy.

Also I am having trouble with Mac Mudlet beta 10 pre 12. It seems that I dl and install and it did not overwrite pre 8. So, reinstalled Mudlet beta 10 pre 12 to make sure that I selected the right destination (there is only one destination BTW). Nope. Nothing. So I deleted pre 8 and installed pre 12. Nothing. Then I used the search feature to find it. Nothing. Is this package somehow invisible?

Anyway... I am having difficulty... should I bug this one?