Void Reaver Alarm
What’s Different? Top
I posted a new version of the addon to fix various bugs and features of the original addon written by Lenja of Frostmourne-EU. To see the original addon, click here.
2.4.2: Blizzard has implemented a new way that Void Reaver functions. I have updated the addon to accommodate these changes. Once 2.4.2 goes live, the newest version should work.
2.3.0: Unfortunately 2.3 had issues with the addon forcing one of the functions that get the direction you are facing to be invalid, and therefore broken. If a bomb was placed, you could see it, but not know which direction it really was. This leads to people running into other bombs, and the deaths we have had recently. I used a piece of code offered in a comment to fix this.
At the request of a few members, I toned down the blue screen that is to warn you by half its brightness. I also created an option to remove the blue screen entirely, but maintain the bomb icons and distance meter (/vra blue off to disable, /vra blue on to enable). I also removed the ping warning outside of TK. It was highly annoying to receive the notice that X pinged the minimap every 3 seconds in AV. Now it only notifies you while in The Eye.
My modifications are only usable in the english language settings… I didn’t translate the additions and add to the localization file. I only modified the main LUA and XML files (only one number in the XML file). This was to provide a simple use of my addon’s code to fix Lenja’s when s/he can do so.
Downloads Top
- WoW 2.4.2 version: Void Reaver Alarm v.1.4
Instructions for Windows Users Top
- First, click the above link and save the file to somewhere very easy to find. I suggest the desktop.
- Right click the file (Windows) and select “Explore,” if you do not have an option to “Extract” or “Unzip.” If you have something like extract or unzip, use that and skip to step 4.
- Click “File” in the new window that opened, and hit “Extract All…”
- You should either have the Windows Extraction Wizard open, or your personal unzipping software’s window open. If you used a one-step extraction like in Winrar, skip to step 6.
- Click “Next” until you reach a text box to tell it where to extract to. Make sure you know where it will go. The default for windows extraction is into a folder named the same as the zip file, but not the contents of the folder. Click “Next” and “Finish” until it completes. If you can’t find the folder it was supposed to extract to, try it again, and pay attention to where it extracts to.
- Find the innermost folder named “VoidReaverAlarm.” If you open this file, you should see several files including “VoidReaverAlarm.toc.” Select that folder (not the files, but the closest folder with those files), and move it or Cut and Paste it into the World of Warcraft addon folder. This is typically “C:\Program Files\World of Warcraft\Interface\Addons\.”
- Now make sure you have a folder named “VoidReaverAlarm” along with the other addon folders (some include folders starting with “Blizzard_”) and if you open the “VoidReaverAlarm” folder, all you see are the files I mentioned before and no other folders inside. If you did exactly as I said, you should see them in the right place.
- Now you need to exit completely from WoW, and restart the program and login to the character screen.
- Click the Addons button in the bottom left of the character select screen and verify there is an addon named “Void Reaver Alarm” (or something close). If it is in red, check the box to enable out of date addons (the TOC file hasn’t been updated at all). If there isn’t an addon listed similar to “Void Reaver Alarm,” go back to your WoW addons folder and go to step 7.
- Hit OK, and log in on a character.
- After you load, type “/vra” and hit enter. There should be some text explaining the slash commands in your chat box, if not, log out, and go to step 9 again.
- If everything works up to now, try it out inside an instance (preferably alone) by typing “/vra test bomb.” Try moving around to see the numbers change, turn to see the icon indicating direction, and learn how to understand the symbols and numbers. When you are 21 yards/meters from the bomb’s center, the blue screen goes away, and when you are over 30 yards/meters away, the icon doesn’t show at all. Become an expert with this addon BEFORE we go in The Eye and work our way to Void Reaver.
May 21st, 2008 at 7:37 am
I’ve had someone say on curse.com that the addon you have posted here does not work as intended. I understand that you developed this as a beta test and would like to ask if you have had confirmation or not as for it’s functional.
Assuming that the Orbs target someone and that fact that I do not know the cast event for the log event, I offer my variation of the combat log trigger that should work in any case provided a point of origin has been established (pinging the minimap) for the fight.
–localization.lua–
VRALARM_SPELLNAME = “Arcane Orb”
–VoidReaverAlarm.lua–
–function VoidReaverAlarm_Event() case–
if (event==”COMBAT_LOG_EVENT_UNFILTERED” and arg4==VRALARM_BOSSNAME and arg7==UnitName(”Player”) and arg10==VRALARM_SPELLNAME and arg2~=”SPELL_DAMAGE”) then
PlaceBomb()
end
May 21st, 2008 at 7:43 am
I’ve tested that structure on specifically named persons and spells such as Icelance and Searing Pain and found that some spells like Icelance and Death Coil have a target when cast while others do not (tested casting time spell: Searing Pain), but trigger a targeted event on hit/miss or proc in the case of dots.
May 22nd, 2008 at 2:57 am
NVM, according to DBM creators, blizz lied on the patch notes and there is still no combat log entry for arcane orbs.
June 3rd, 2008 at 1:50 pm
There is, I saw it in my log file, it’s just not what you expect.
What I could see was “Target is affected by arcane orb” Not too sure, will update when we try voidreaver again