Trying to figure out what client is easy to use. I've messed around with mudlet and mushclient, the the logging still eludes me. Any suggestions on a client that is easy to use ie triggers, aliases, and logging? Or what is the best client?

NT

Wintin++ on Windows or just tintin++ is free and pretty solid with a lot of tutorials and scripts out there. It's simple and easy. Zmud or the newer cmud are windows clients you pay for but have a lot of features and work well with graphical UI. I've used both as well as mudmaster and ended up just sticking with wintin++ because it's so easy but powerful.

I'm terrible at any kind of code. Was hoping for a something more simple, but thanks for the info.

NT

nt

Both clients are easy to install and use and require no coding. You will, however, always need to make use of the clients basic scripting to make use of it for anything other than pure telnet. All of them are extremely simple and not really comparable to coding in complexity. For example my most basic script I have for my first characters is at the bottom after links. I removed anything more advanced but it should show how simple it can be. Here are some links to popular Mud clients.

Zmud/CMud This is the most popular MUD client there is and possibly most feature full. It is not free though.
http://www.zuggsoft.com/index.php?p=cmud

wintin++/tintin++ Simple, free, powerful, cross-platform, purely text base so no GUI, but it's for playing a text game so I don't really need a GUI slowing it down. I currently use this.
http://tintin.sourceforge.net/index.php

I used to use this back in the day so I don't know how well it works anymore, but it's a graphical interface like Zmud/Cmud. If I recall, that actual scripting system is taken from tintin++.
http://mm2k6.sourceforge.net/mm2k6/

Other popular ones I don't know too much about.
MUSH Client
http://www.gammon.com.au/mushclient/mushclient.htm
JMUD
https://sourceforge.net/projects/jmud/
GGMUD
https://sourceforge.net/projects/ggmud/

My most basic scripts for wintin++ if you are interested. All of these can literally just be typed into wintin++ as you see them. You would just follow the steps below.

1. Copy each line below into wintin++ by right-clicking on the window and clicking paste.
2. Type #var character Dudeman or whatever your characters name is.
3. type #write CF when you are done to save it as CF.
4. Any time you open wintin++ you simply type #read CF and the type connect. That's it.

You can also set this to PLAIN instead of HTML if you want but if using plain I would suggest using notepad++ for reading, which also has a powerful search in files option for finding keywords in your docs. Just edit the directory for logging to wherever you want to log to, just note that each \ or . requires another \ in front of them as shown. E.g. #log append {C:\\CF\\Logs\\$character$date\.html}. More simply you could just do #log append $character and skip the date but you could end up with a maybe 50MB or larger single file as all of your logs would be in one file. The way I have it set is each day gets a new date on the end of the file name so one file per day. Everything below here can be copied and pasted into wintin++ in one go.

#CONFIG LOG HTML

#VARIABLE character Dudeman
#VARIABLE container knapsack
#VARIABLE date -2015-11-01
#VARIABLE food bread
#VARIABLE water canteen

#ALIAS water {get $water $container; drink $water; put $water $container}

#ALIAS fillw {get $water $container; fill $water;put $water $container}

#ALIAS food {get $food $container; eat $food}

#ALIAS connect {#session CF carrionfields.net 4449; #split; #format date -%Y-%M-%D; #log append {C:\\Users\\Admin\\Desktop\\Logs\\$character$date\.html}}

Thanks for all the help. I actually have logging working now in mudlet, but it does not log my input commands. Was hoping to have those as well for figuring out directions and such.

Anyone have experience with mudlet? Seems like a great program, but I feel I'm in over my head with it. Advices much appreciated.

I see people complaining about it from 2009 and the response being that the next update, being 2.2 or later, would fix it. Mind that 2.1 is still the current version. There seems to be a 3.0.0 preview version that is available now though since November but it may be buggy and I haven't tried Mudlet at all so can't help much...