a way to import sound packs

Hello, I would like to recommend a feature to import sound packs that have been made for MUDs. This way, rather then having many different MUSHClient installs for each and every pack, you can just use one MUSHClient instance and when you load a world with a pack-BAM, the sound pack works.

There's nothing special about a "sound pack". It's just a collection of sound files and a plugin that determines when to play each sound. MUSHclient already has a generic plugin interface, so I don't understand what this is asking for.

I thought there was something more since every single pack includes it's own MUSHClient rather then just letting you import it into an existing install.

Do you have any examples? There are many reasons why doing it that way makes more sense, but it's hard to say what the specific circumstances might be without knowing which sources you're talking about.

The reason I do it for Aardwolf is because the Aardwolf MUSHclient Package does way more than just sounds, and I very regularly depend on new features or bug fixes that are not yet available in released versions of MUSHclient. You may not like the idea of having a different copy of MUSHclient sitting around, but it's actually much easier for both users and plugin developers when the process is for you to go to your "Aardwolf folder" when you want to play Aardwolf and to your "Alter Aeon folder" when you want to play Alter Aeon, and so on. That way I can do whatever I want for Aardwolf and not have to worry about maintaining compatibility with other MUDs.

I honestly never thought of it like that. Was referring to ones like UOSS, Cleft of Dimensions, Star Conquest (when it had one) etc. I was just thinking that since other MUD client devs are discussing making some sort of centralized system for sounds that it might be a good idea to have something similar for MUSHClient. That way if the player wants to use MUSHClient (for instance due to MUSHReader) they can just import the sound pack.

Sounds are played from anywhere on disk, logically though they would be in a subdirectory of MUSHclient. However you could easily get people to download a .zip file with lots of sounds in it, and make a suitable plugin that plays sounds from whatever folder you extract them into.

Fiendish is right, having a "package" of MUSHclient and other files (eg. world configuration, a mapper, appropriate plugins) helps make a client that runs "out of the box" for a particular MUD.

Since I try hard to make things backwards compatible you can always load the "pre-release .exe file" on top of the MUSHclient.exe that comes with a particular package.

See http://www.gammon.com.au/forum/?id=13903 for how to do that.