Purpose
I've used QuestGuru for a while, and really liked the feature to play some kind of sound when you complete a quest or a quest objective, but to have the addon installed, just for this feature, felt too much for me. The other addon I could find was Quest Progress Sounds, but couldn't get it working, so I decided to write this small addon.
Usage
QuestSounds has no GUI, and I'm not planning to add one either. All configuration options are available via chat commands. Type "/questsounds" or "/qs" for an ingame overview of the various options.
- /qs - Display ingame help
- /qs on - Enable QuestSound
- /qs off - Disable QuestSound
- /qs status - Display current settings.
- /qs double - Toggle double-ding*. Upon completing the last objective of a quest, if Double-Ding is enabled you'll hear both sounds. First the 'objective completed', and after that the 'quest completed' sound. If you disable it (it's disabled by default) you'll only hear the 'quest completed' sound.
- /qs chat - Toggle displaying quest progress in chat window (disabled by default).
- /qs qsound soundfile - Quest complete sound. Set to 'none' to disable.
- /qs psound soundfile - Objective progress sound. Set to 'none' to disable.
- /qs osound soundfile - Objective complete sound. Set to 'none' to disable.
'soundfile' can be either a built-in sound, or a sound from any mpq file in wow. For example to modify the "Quest Completed" sound, you could type:
/qs qsound "Sound\\Ambience\\WMOAmbience\\DungeonCrypt.wav"
Dependency
Users of v1.0 need to install 'LibQuixote-2.0'. As from v1.1, no other addons are needed.
Changelog
I don't actually keep a changelog. If you want simple "dings" while questing, without any other bells and whistles, stick to v1.1. if you'd like to configure the addon or like the chat info feature, use the most recent version.
Bugs
Don't expect too much from this :). I'm not a programmer. From v1.2 the addon became much more complex, so it's more than possible that there are still bugs in it. If you happen to find one, please send bugreports to [email protected], and I'll try to fix it asap. Thank you.
P.S.: Sorry for my bad English :)