• posted a message on RareScanner

    lol, sure! I will change that :), perhaps a horn or something else less dramatic.

    Next week I will upload a new version with the database updated, so this change will be included.

    Thanks for your comment!

    Link Removed
  • posted a message on RareScanner
    Quote from Raphael_M >>

    Woah, never heard of the "Master" channel - thanks alot for the explanation!

     You are welcome! :)
    Link Removed
  • posted a message on RareScanner

    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. 

    Link Removed
  • posted a message on RareScanner

    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.

    Link Removed
  • posted a message on RareScanner

    K4tz I've uploaded a new version 2.0.5 changing the target script. I think it might stop popping up the warning. Please, let me know if it works.

    Link Removed
  • posted a message on RareScanner

    That's new, it only asked me once, and now everytime I click on the button it doesn't show up. I just tried again with a couple of characters and it didn't pop up. I will keep looking into this anyway.

    Link Removed
  • posted a message on RareScanner

    Hello again.

     

    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.

    Link Removed
  • posted a message on RareScanner

    Hey K4tz.

     

    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.

     

    Thanks!

    Link Removed
  • posted a message on RareScanner

    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).

    Link Removed
  • posted a message on RareScanner

    Hey gaspy10.

     

    Thanks for the report, I will take care of it right away. Probably the file has changed the encoding.

    Link Removed
  • To post a comment, please or register a new account.