7 months later still suffering from situational depression that hits me at odd times.

Drunk dialling Lusternians.

My roommates, despite weighing 30 kilos less at the least than me, none of whom who visit the gym more than once a fortnight, have instructions that they are to restrain me when I decide to be a hero and down a bottle of scotch when I haven't had a drink for sixth months.

This = FUN

MUSHClient. Good grief. Despite two people helping me earlier for a couple hours I still am not at the point where I can find in the documentation how to make an IF/THEN ...thing.

I tried coding in MUSH for ten minutes.

When I discovered that their if statements went something like:




I closed the program and ran back to zMUD.

Wow. You guys must've had bad tutors.

MUSHclient lets you use whatever language you want, pretty much. Lua is the easiest to learn and the best integrated (also, the most portable).

Why would you run back to zMUD just because the if statement syntax is more clear?

I don't have a tutor, I'm just trying to search through the help files...and the forums...they don't even seem to have anything clearly about conditionals or if in there. All I want is for something to tell if a variable = something I set it to, and if it is, do something. THAT'S ALL I WANT.

WHAT ING SYNTAX ERROR NEAR ELSE. YOU DIDN'T ING TELL ME HOW TO WRITE ELSE IN THE FIRST PLACE. OR IF OR THEN FOR THAT MATTER.

I enjoyed that part about writing Verilog in Xilinx. It would generate random errors every time you compiled, and it would only tell you "error near this", and usually, if you just kept clicking the compile button, it would eventually work. Also aggravates me when things aren't documented right. Zmud documentation is great. README's and help files should explain things like you're talking to a 2 year old, because honestly when you learn something new that's how you start out.

I get really aggravated trying to install new software that gives vague directions and just assumes you know what you're doing. It seems the more complex or high level that a piece of software is, the less they seem to think they need to tell you.

Like installing a compiler and hooking it up to an IDE. Took me forever to figure out how to do that the first time, because there weren't good instructions for it.



Well that was my rant.

And that's how this damn programme is making me feel. It should not be taking me 2 hours to set up a trigger that I can do in nexus in 20 seconds.

I have to agree: the MUSHclient help is awful. There's a huge gulf in between "how to log into a MUX and type stuff" and "the syntax and data types of COM objects" which makes it very easy to get started on connecting, and very, very hard to move past that.

One thing I found that helps is this tutorial. But it's still a big strike against MUSHclient that this kind of insight isn't in the help file, and spread around a little.

Actually doing stuff in it is pretty good if you get past that. But I bet MUSHclient loses most of the people who would be best positioned to thrive in it because of that. A rewrite of the help file adding stuff on "how to do very basic scripting" would go a long way. Maybe one of you users/scripters who love MUSHclient could write it and offer it to Nick.

They never do.

They always seem to think that you have some sort of clue when they write those, so, of course, when you don't (and I really don't! ), you're out of luck. That's why I paid Ethelon for his system. It's all user friendly and when I see him, he lets me bug him with questions without making me feel even stupider than I am.

Yes, MUSHclient has a more challenging learning curve. However, not only is it far more powerful than any other client I've used (especially on Windows), it's got a far more helpful developer behind it. Nick answers a lot of questions and he does so in a very clear and helpful manner.

You can find examples on how to write things in Lua in the (*gasp*) Lua sub-forum over on the MUSHclient web site. It's a great place to start, and if no one has asked something like what you're looking for now, you just ask your question in your own way. Heck, you can even just e-mail me and ask!

Well then, Zarquan. I have the same questions as Shiri.

How does MUSHclient variables and if/then statements work?

Could you maybe post a mini-tutorial to the basics of MUSH in the mechanic's corner of the forums? I'd be one hell of a happy person if you did, since I already know MUSH runs at the speed of light.

ZScript has ridiculously documented functions and examples. Of course it seems easier to people... MUSHClient resembles real code, which strikes fear into even the most stalwart of hearts.

#IF @monkeyballs {#ECHO Your monkey has balls} {#ECHO Your monkey doesn't have balls}

Created with ZMud/CMud help file examples. Very easy. The same statement in MUSHClient looks like function code. Most people learned to limp in ZScript because they don't know how to code.

I'll think about it... just for the confused and/or lazy people.

(I had tried to get into MUSHclient at least a half dozen separate times, and I kept going back to zMUD because I just didn't like how things were interconnected in MUSHclient and I love my graphical maps and buttons.)

Thanks for that link, Gwylifar, it at least got about 40-50% of the way to solving my problem which is more than I'd been managing on my own.

I started working on a MUSHclient tutorial today, after reading comments here, but I've never been the greatest at explaining things to others, especially others with little or no knowledge of the subject matter. It's a basic start so far, and I have plans to add more as I have time, but please give it a look-see.

http://larkin.dischai.googlepages.com/mush

Cheers for Zarquan. MUSH seems a bit easier to understand with a tutorial, even if it's one that's just started.

Oh right. A rant.

Being bored.

Ok, so I bought a car (which is AWESOME!!!!!!111!!) when I went to visit my cousin in Mississippi (she happens to work at a car dealership! Got an awesome car for like two grand under retail! ). Apparently, the rule in Mississippi is: You don't get your title until you register and get your tags. But, here in Arkansas, where I live, you can't get your tags until you have your title.

The dealership there didn't give me the title because of Mississippi's rules, the revenue place here won't give me the tags because of Arkansas rules.

My car is in limbo!

I've talked to my cousin and they're gonna be sending me the title in the mail as soon as possible, but it'll be a lil bit.

I knew it was all going too smoothly!