First, I'd like to compliment Nick for having an excellent client to start with, it was great when I first started using it a few years ago, and it just keeps on improving. Whenever I want to do something, Nick has already made it possible a few versions ago, and if he hasn't he probably will soon. Thanks Nick!
Now, on to what I'd like to see. I store all my worlds, sounds, scripts and so on within the MUSHclient-directory, and whenever I upgrade MUSHclient, I just move over the sound-directory and all the worlds and scripts I still actively use to the new MUSHclient-directory. I don't overwrite the old install with a new one, which I guess most do, so I end up with a little problem, I have to update every path in every world after an upgrade, and as this includes finding all triggers with sounds and painstakingly changing each one, this quickly becomes a real pain.
I realize that this probably isnt't a big thing in the big scheme of things, and it's probably more work than it's worth to implement, but I'm going to throw it out anyway and let Nick decide: Wouldn't it be better if MUSHclient stored the paths as relatives, if the path pointed to somewhere beneath MUSHclient's working directory?
Heh, I almost feel a little ashamed for posting this, now that I read it. I'm just being really akward about how I upgrade MUSHclient, ain't I? I'm just going to start installing over the old installs from now on, I think. Still, I'll leave this post here anyway, it's a sound idea, even if not really worth implementing. |