SolarianAlarm v1.6 by Lenja of Frostmourne EU
"Turns your whole screen deep blue when you get debuffed with Wrath of the Astromancer. It is IMPOSSIBLE to miss that!"
The text "SolarianAlarm loaded!" will appear in the chat window when you start the client and the addon is active. From then on, you will always be warned by turning the screen blue when you get Solarian's debuff. For testing purposes, use "/solarianalarm test on" and the screen will turn blue on ANY debuff and will remain so until the debuff is gone. You can easily test this by using a bandage on yourself. Turn test mode off again with "/solarianalarm test off" to go back to normal mode. You can also issue a version check with "/solarianalarm version check" to see what SA versions your raid members are using.
-The version check now uses broadcasts instead of whispers. It's a bit more overhead when doing a check (not that it really matters) but it'll fix the issues with people using obsolete ACE2 versions.
-Various optimization changes. Hopefully this'll fix the problems some people had when the screen turns blue.
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
Download the Curse Client
- +0
- Thumbs Down
- Thumbs Up
sp00n saidCould you (or somebody else) adapt this mod for the Eredar Twin's Conflagration?
I tried to do it myself, but the problem is that when the debuff actually appears on the player, it is already too late.
The screen should turn blue (or whatever) as soon as the boss emote is fired ("Alythess directs Conflagration at PlayerXYZ"), which I was unable to do so far.
- +0
- Thumbs Down
- Thumbs Up
Pwnzerfaust saidVR, lol? This is Solarian alarm tard boy.
- -1
- Thumbs Down
- Thumbs Up
bishope saidThis Mod is almost a must on VR any more.
Please update it for 2.4!
- +0
- Thumbs Down
- Thumbs Up
Lenja saidChanges in the new version:
-The version check now uses broadcasts instead of whispers. It's a bit more overhead when doing a check (not that it really matters) but it'll fix the issues with people using obsolete ACE2 versions.
-Various optimization changes. Hopefully this'll fix the problems some people had when the screen turns blue.
- +0
- Thumbs Down
- Thumbs Up
Lenja saidThis is getting better and better.... Guys, you can stop making suggestions now. I know all that already. I simply didn't have time to make an update yet. This is an extremely simple addon and there are very few places where problems can hide. I already knew all that last week when I made that post. You can stop trying to help me. ^^ I can see the obvious myself. ^^ All I need now is to get my lazy behind to update and upload the files.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidI'd suggest not showing or hiding frames on every update, but just when the state changes between show/hide. Here is how I hacked that for myself:
-- variable at top
local warnstate = false
-- inside SolarianAlarm_Update
if (a) then
if(not warnstate) then
SolarianAlarmMain:Show()
warnstate = true
end
else
if(warnstate) then
SolarianAlarmMain:Hide()
warnstate = false
end
end
Another thing that one could do is possibly put an
if(sec < 0.1) then
-- do nothing
else
-- all the rest
end
inside the SolarianAlarm_Update so it actually only does anything every 10th of a second.
- +0
- Thumbs Down
- Thumbs Up
yssaril saidmight want to consider making this event driven using one or multible of these events http://www.wowwiki.com/Events/Buff and not using the OnUpdate cause onupdate get triggered every single frame so you only want to use this if you really 100% have to use it the events will fire often during a raid but they will not fire every single frame thus reducing lag considerably
- +0
- Thumbs Down
- Thumbs Up
Agramon99 saidI think I found the problem, you check for debuffs on the OnUpdate event, this event is triggered EVERY frame. You need to check yourself when you last checked the debuffs, maybe every second or so. More info here: WowWikki Howto Use OnUpdate Correctly
- +0
- Thumbs Down
- Thumbs Up
Lenja saidA few other people seem to have trouble with fps, too. One of our members can't use it because her screen completely freezes up when she's the bomb. ^^ Maybe I can find a way to make it work better somehow. All it does is create a big transparent window.
- +0
- Thumbs Down
- Thumbs Up
Agramon99 saidVery usefull addon, but can you please check your mod, it turned the whole raid FPS way down. Mine went from 36 to 6 fps, during the solarian fight when enabled.
- +0
- Thumbs Down
- Thumbs Up
BBR saidhm. would it perhaps be possible to merge this into BigWigs?
And have it as an option there, i'm fairly sure it'd be a welcome improvement.
And everyone has and updates bigwigs in the guild :>
- +0
- Thumbs Down
- Thumbs Up
danalex saidsimple and effective
- +0
- Thumbs Down
- Thumbs Up
Lenja saidI've finally found out why some version checks do not succeed even though people have the addon installed. It's because they're using an old version of Ace2 (AceComm/ChatThrottleLib) from before patch 2.1. That old version improperly hooks the SendAddonMessage() function and may cause newer addons to fail. I've added a warning message to SA when that error occurs so that people know how to fix it.
- +0
- Thumbs Down
- Thumbs Up
Lenja saidHow come? Anything in particular you don't like? I'm always open for constructive criticism.
- -3
- Thumbs Down
- Thumbs Up
OrionShock saidgod.. what a bloated addon....
- +0
- Thumbs Down
- Thumbs Up
Lenja saidReloadUI only works if you do not add any new files. I always use it to test my stuff. Would be a pain in the arse otherwise. But you have to restart when adding a completely new file (like Localization.lua which hasn't been there before).
- +0
- Thumbs Down
- Thumbs Up
BBR saidSeems solarian alarm doesn't like /console reloadui to activate a newer version.
After a restart on wow.exe it works ok.
- +0
- Thumbs Down
- Thumbs Up
Lenja said@BBR: The global variables from Localization.lua are not loaded for some reason. That's why they're "nil" and don't contain the string value they should. Maybe you fubared something when you installed the new files. Try completely deleting the SolarianAlarm folder and download and install 1.4 again. Either the Localization.lua file is missing or it is not being included in the SolarianAlarm.xml file.
- +0
- Thumbs Down
- Thumbs Up
BBR saidErrors in 1.4 after upgrading from 1.3 :
2007/10/29 20:51:58-3437-x1]: SolarianAlarm\SolarianAlarm.lua:106: attempt to concatenate global 'SOLALARM_VER' (a nil value)
<string>:"*:OnEvent":3: in function <[string "*:OnEvent"]:1>
---
[2007/10/29 21:01:49-3437-x631]: SolarianAlarm\SolarianAlarm.lua:126: bad argument #2 to 'strfind' (string expected, got nil)
SolarianAlarm\SolarianAlarm.lua:126: in function `SolarianAlarm_Update'
<string>:"*:OnUpdate":1: in function <[string "*:OnUpdate"]:1>
---
- +0
- Thumbs Down
- Thumbs Up
Spoid saidsomehow it'd be really nice to make it work when thaladred's watching you, too. kinda the same thing for those unconcentrated people in your raid.