I will take a look into this. Right now the only thing you can do is to disable the rares found beside the Underbelly (if they aren't treasures or events), or pick/kill them so it won't warn you again.
- Registered User
Member for 9 years, 3 months, and 25 days
Last active Sun, Sep, 25 2016 10:05:57
- 0 Followers
- 44 Total Posts
- 0 Thanks
Aug 15, 2016Link Removed
The function PlaySoundFile() receives 2 parameters: the audio to play and the audio channel to use. If you check the audio channel options, I'm using "Master", which plays the sound even with disabled sounds (ambience, music or other effects such as abilities). In theory once you disable the audio "CTRL + S" and the music "CTRL + M", you shouldn't hear anything else other than sounds played from the Master channel.
You can test it easily by disabling music and sounds effects and flying over Nagrand (looking for the elite rares in that place). You should be able to hear only Rarescanner alerts.
Aug 14, 2016Link Removed
It uses the general sound channel, which you can hear even if you disable the sounds/music of the game or minimize it (in window mode with Sound in background activated). So you can always disable the sounds in wow, and you will still hear an alert if you find a rare while you are doing something else.
Jul 27, 2016Link Removed
I've been researching about this issue and there's not much I can do.
In order to target and mark a NPC I need to use scripts because the API methods are protected, which means we cannot use them in an addon (only the game is able to), I forgot that's why I did it like this in the past :)
Perhaps with time Blizzard will whitelist inoffensive scripts like "/target" and you won't see the message again.
Anyway, if you see it, you can accept clicking "yes" and you won't see it again.
Jul 27, 2016Link Removed
I also noticed that warning, however I cliked "yes" and everything worked fine.
It's a new warning message added by Blizzard to inform about the use of scripts in addons, if you check the wow site forums you will find a lot of people asking about these warnings while using different addons and macros.
I will take a look into this, perhaps there is a new method to mark NPCs without using scripts.
Jul 22, 2016Link Removed
Bug fixed in 2.0.2. The new font I was using to display the names wasn't compatible with every client, sorry about that :(
It was affecting to ruRU, zhTW, zhCN and koKR.
Let me know if you have more problems.
The new version will be available as soon as curse approves it (it usually takes like 5 minutes).
- To post a comment, please login or register a new account.