I'm another MacOSX user who is also finding that the libs directory has been added to the zip file incorrectly - instead of a directory structure like:
SpamSentry
+-- libs
+-- AceEvent-2.0
The directory structure is:
SpamSentry
+-- libs\AceEvent-2.0
Which doesn't work so well. This has only happened on the last couple of times I've updated SpamSentry - it was present in both the latest (72774) and the one I downloaded before that (72508).
Curiously, even though the AddOn appears in both the main Blizzard addon list and in the /ace2 list, its not actually in a working state in game.
Hi Simes, i did think about it at one stage, but there are much better addons which work very nicely with SR. The one i use is called CooldownTimers2, you should take a look, it does exactly what you're asking for (and more) :)
I've looked briefly at CooldownTimers2, but it would appear that its in a state of flux as the mod author has stopped developing it and the last comment on the CooldownTimers2 forum didn't fill me with confidence :(
Unfortunately the latest version of SpellReminder is now completely failing for me with the following message:
Date: 2008-03-05 23:16:09
ID: 53
Error occured in: Global
Count: 1
Message: ..\AddOns\SpellReminder\SpellReminder.lua line 721:
CandyBar-2.0: You need the PaintChips-2.0 library if you don't pass in RGB pairs as colors.
Debug:
...AddOns\Bartender3\libs\AceEvent-2.0\AceEvent-2.0.lua:365:
...AddOns\Bartender3\libs\AceEvent-2.0\AceEvent-2.0.lua:342
Trying earlier versions of SpellReminder (eg 61807.1) gave me the following error:
Hi Simes, not quite sure why the bar scales would have changed, it *could* be because there was a bug where the bar groups were being saved per-profile and not per char. But it shouldnt happen for future.
As for your shackle problems, you can set Shackle Undead to Persistant in the bar options to stop it from disapearing when you target a second mob of the same name. As far as shackles breaking, you can only tell if you have the shackle targetted when it breaks *or* if you mouseover the target. That said, if you turn on Persistant, then the bar will not dissapear even if you did that.
I'm rewriting the tracking system to use the new unitID introduced in 2.4 that should make things much more flexible.
The scale problem hasn't reappeared which is nice, I'm guessing that it could've been a one off.
The last time I encountered this I did have the bar set to persistent; I've just re-tested against mobs of the same name and it all worked as I'd expect - shackle one mob, target another of same name, nuke it down, etc.
I'll know for sure when I had back into Kara - its been on mobs in there in which I've encountered this.
Good to know that you're updating the AddOn for 2.4 - have to wonder how many AddOns are going to die when the combat log changes then.
One the most recent two builds I've downloaded (currently using r61807.2) the bar scale for normal was changed from 1 to 0.2 when the mod was updated.
Also, would it be possible to add an option to say that certain spells should always be visible - no matter if my target has changed. It'd make keeping shackles up a lot easier.
Talking of shackles, the addon doesn't seem to notice that a shackle has been broken, although I don't know if its possible to track that occuring.
0
The directory structure is:
Which doesn't work so well. This has only happened on the last couple of times I've updated SpamSentry - it was present in both the latest (72774) and the one I downloaded before that (72508).
Curiously, even though the AddOn appears in both the main Blizzard addon list and in the /ace2 list, its not actually in a working state in game.
0
I've looked briefly at CooldownTimers2, but it would appear that its in a state of flux as the mod author has stopped developing it and the last comment on the CooldownTimers2 forum didn't fill me with confidence :(
0
0
0
Trying earlier versions of SpellReminder (eg 61807.1) gave me the following error:
This can easily be re-created by using the "Test Bars" option.
0
0
The scale problem hasn't reappeared which is nice, I'm guessing that it could've been a one off.
The last time I encountered this I did have the bar set to persistent; I've just re-tested against mobs of the same name and it all worked as I'd expect - shackle one mob, target another of same name, nuke it down, etc.
I'll know for sure when I had back into Kara - its been on mobs in there in which I've encountered this.
Good to know that you're updating the AddOn for 2.4 - have to wonder how many AddOns are going to die when the combat log changes then.
0
Also, would it be possible to add an option to say that certain spells should always be visible - no matter if my target has changed. It'd make keeping shackles up a lot easier.
Talking of shackles, the addon doesn't seem to notice that a shackle has been broken, although I don't know if its possible to track that occuring.