BloodSurge
Owner request.
If you have any questions please contact our support team https://support.curseforge.com.
Overview
Minimalistic AddOn for instant Wild Strike! notification. This was spurred by the AddOn Bloodthirst and is meant to be a direct replacement. Bloodthirst had a large memory leak so I decided to just write a new AddOn that accomplishes the same thing and is Ace3'ed.
Changes
Ability to add custom spell ID's and names to BloodSurge has been removed. This was done to return BloodSurge back to its roots as a lightweight addon. If you like the addon as it was developing then please install Proczors as it picks up where BloodSurge left off.
BloodSurge Description
- A Warrior Only AddOn
- BloodSurge is a simple and small monitor for a warriors instant Wild Strike! PROC.
- Configurable in Blizz Panel
- Full Screen Flash (Color Configurable)
- Playing of Sound (Taken from Bloodthirst)
- Alternate sound options via AceGUI-3.0-SharedMediaWidgets
- Print Warning in UIErrorFrame
- Flashing Bloodsurge! Spell Icon
- Icon Size
- Icon X
- Icon Y
Configuration
/bs or /bloodsurge
Supported Translations
Please help localize this project HERE
This isn't working for me. I've tried the Alternative combat log filtering, no luck. The Test button works just fine. Not sure how to use the Debugging. I'll have to spend some time trying to see if it's another mod interfering.
I haven't used this in a few months, so just now upgraded it to the latest version.
@420Bunny
Ok try v1.3.7, there was a typo in v1.3.6.
2 errors:
BloodSurge-v1.3.6\BloodSurge.lua:317: unexpected symbol near 'if'
and
BloodSurge-v1.3.6\BloodSurgeOptions.lua:6: Usage: GetAddon(name): 'name' - Cannot find an AceAddon 'BloodSurge'. AceAddon-3.0-10 (Ace3):176: in function `GetAddon' BloodSurge-v1.3.6\BloodSurgeOptions.lua:6: in main chunk
@420Bunny
Try v1.3.6, it should take care of the CLEU changes in 4.1
I am having the same problems as frankz, works in the config/test button, but not in actual combat...any suggestions?
The Sound alert works via the Test button in configuration, but doesn't work for me in actual combat.
With ur link it fail. Any news? Btw the sound alert works when wow sounds are turn off? Waiting for ur tips. Thanks.
Im tryin' to get sound alone with some guildies, but thanks! And i will try with ur link.
Crimzlol: just download 1.0.39-release which is, as it states in the name, release quality.... and the sound works! not sure why your not getting sound with the latest alpha, will have to look at that this weekend.
Hi, im french user and im really bored atm. I was a fan of bloodthirst, since 3.3 ofc it fail. So i dl the latest file : r42. I just want the fucking sound, but everything works except that, icons, flash msg works, but sound not... Pls i need some tips, since 3.3 release this is so crapz to play without slam sound alerts... Thanks a lot.
Hey networkerror thanks a ton! Your workaround is working just fine for me. It's pretty annoying missing slam procs so thankfully you were able to work around the issue. Thanks a bunch again you've saved my day.
try r38, this should workaround the bug. Thanks for the link jtbalogh and Mik for his fix.
Missing buffs was reported to blizz. Bloodsurge was one of em. Using an event instead of a combat log event is a temporary fix : /. http://forums.worldofwarcraft.com/thread.html?topicId=21726253070&sid=1
The slam buff icons appears but combat log has no reference it started or stopped. All other buffs appear ok in the combat log. Monitoring the addons, function BS:BloodSurge() has the same results.
Doesnt work at all for me.
I actually didn't make any changes recently, those changes appear to be from WoWAce so the TOC never really got its interface version bumped. I will take a look into the combat log filtering asap.
I have two issues here networkerror. The update you posted is not fully updated. WoW is still showing it as an outdated mod. I made sure to delete the previous version from the interface directory and I cleared the physical cache from the WTF folder to be sure. Also your mod is being affected by the combat log bug where as the mod isn't working at all when slam procs. Nothing short of watching the floating combat text is working right now. It may just be a bug or something new Blizzard implemented into the combat log system.