One of the issues I tend to clash with a lot of programmers on is the issue of tossing in options/toggles/etc on programs I work on, be they scripts, MUF, engines, servers, etc. When I maintained code on MUCKs in the past, and someone came to me with a problem they had with how a program worked for them, or how it didn't work like they were used to
(
Read more... )
Comments 7
Reply
hardassed about this. When it comes down to it, I think...a MUCK is a
MUCK. A MUSH is a MUSH. If you want a MUSH, use a MUSH. Don't use a MUCK.
I totally agree. x_X Turning a MUCK into a MUSH via wacky commands is just a recipe for confusion.
Reply
Reply
Reply
-Akari
Reply
Reply
But yeah, you made colors acceptable, since it was easy to implement self-setting colors, in conjunction with good default color schemes for almost everything. You can look at it everything you guys coded and 99% of it didn't blind you.
I agree with everything said about switches. As well as hiding the 'MUCK.' One thing which struck me as weird is how relatively unaltered watchfor was, though. I figured it would totally be +watch/add-ed and such but wasn't.
Reply
Leave a comment