No this mod only has a Casting Bar and Mirror, if you want enemy Casting bar check out Antagonist.
That's too bad. I read this entire thread and I all I saw were a bunch of responses of--why would you want that? As-if the people asking were silly for wanting 1 casting bar addon for all the casting bars they want to see.
Question: "why are people so obsessed with getting an enemy cast bar into a casting bar mod? seriously?"
Answer: Because I play two classes (warrior and rogue) that are both responsible for INTERRUPTING spell casting when the mob/player is casting something nasty. I use eCasting Bar to put a nice big casting bar in the middle of my screen to alert me to the spell casting and make it easy to tell what it is they are casting.
I might only have 3 seconds to decide whether to INTERRUPT a spell and I need to make sure I am interrupting the heal or polymorph and not something less important.
Besides interrupting, this is also incredibly helpful for melee classes when a mob has an AOE effect that will go off (triggered by health at a certain % or something) and I need to run.
Can I use the one I can attach to the Target frame? Sure. I actually use aguf to put those on party members and my focus frame. But I that's just a nice to have feature.
Also along these lines-- Why it unreasonable to expect a casting bar mod to work for all of the available unit IDs? Blizzard made it pretty simple to access the info in 2.0, so why is that such a huge ask?
An addon like Antagonist pre-2.0 had to do a lot of playing around with different events to get the information and that's not the case anymore. Personally, I'm trying to Ace2 my whole UI and with a few exceptions, I am almost there. Unfortunately, eCasting Bar is one of the addons that I haven't been able to replace yet.
Perfect !
it is what I wanted to say, but I am not enough good to speak in English.
I think CBR (and oCB, for that matter) don't feature an enemy CB simply because the addon never meant to do so. They exist, as I understand, because the default castingbar is ugly and IIRC featureless, as in not moveable and textless. And thats what this mods are good at, they provide a pretty way of showing your actual cast as a bar.
I remember someone saying that enemycasts should stick to the unitframe and with that, with the UF-mod of your choice. Since Blizzard itself stuck the enemy CB feature to the unitframe I find that reasonable.
A simple mod, showing your current target's castbar in a way CBR shows yours would be pretty awesome, but I guess this goes beyond the scope of what the author of CBR (or again, oCB) intended for the addon. IMHO, a second addon (ie. Antagonist) will do the job pretty good, even though it may be a bit heavy and not as pretty as CBR.
Pre-2.0 oCB never intended to contain a enemy castbar, mostly because of the actually cost and code annoyance doing this. It wasn't a simple process which shared events and code in general with the default castingbar, which it is now.
If you wonder, the next release of oCB will contain the ability to spawn a castbar for other valid units (player, target, pet, partyX, raidY). It's written to handle it, with almost only the cost of the frame, and the updating off it. Personally I don't want more then the enemy castbar on my rogue, I can go without having one for my own character.
oCB won't go further then using the in-game API for handling the casts.
(I have a feeling I'll end up reading on these forums as habit again :)
If you wonder, the next release of oCB will contain the ability to spawn a castbar for other valid units (player, target, pet, partyX, raidY). It's written to handle it, with almost only the cost of the frame, and the updating off it.
With that in mind my post above seems ridiculous. If it actually doesn't take more than to spawn a new frame and hooking it to another unit ID it would totally make sense that one CB-addon should handle all CB. Why use redundant code in an UF-addon if it actually already is in the CB-addon?
Sorry about that, my knowledge of LUA and LUA in WoW is really non at all, so next time I better just shut up. :)
On a side note, nice to know your kinda back here, Haste.
Is there any option in CBRipoff to show the bars while you customize them, returning them to a locked/hidden state when you are done? I saw a post by Haste on his site that this functionality was dropped from oCB when it was converted to Ace2, though it would be returning at some point.
First time after loading the game(or reload) I get the timer for the fishing 'channeling' bar.
At the second cast the fishing channeling bar doesn't have a time.
I'm having an issue with counter-spells and interrupts. When I get a cast interrupted the casting bar keeps going like it wasn't. I've had this issue a lot in the past too, and caused me to switch to a different casting addon for awhile. I decided to give cbripoff/ocb another shot but I'm surprised that it still does it.
CBRipoff, and even OCB, does have a big latency. At firts I guessed this was unavoidable, but then I saw that the casting bar from agUf is much more precise !
Is there any way to change the updating speed in CBR or OCB ?
The interrupt bug is because oCB never used the UNIT_SPELLCAST_STOP event. The reason it didn't use the event was because it made the whole 'detect' successful casts and failed/interrupted more accurate. The problem however, is that certain spell interrupts don't fire UNIT_SPELLCAST_INTERRUPTED, but UNIT_SPELLCAST_DELAYED followed by UNIT_SPELLCAST_STOP. It's inconsistency in other words (at least in my opinion). The whole interrupt issue can in other words be fixed by forcing the add-on to use UNIT_SPELLCAST_STOP.
The whole bar chopping while updating is because of the way it uses the StatusBar frame. The add-on sets the min value to whatever the start time was, and the max value to whatever the end time is suppose to be. In 2.0 however, this made the bar jump while moving (ie. seem choppy). You might have noticed that Blizzard's casting bar also has this issue.
It's easy to fix the problem with the jumping, just make it use a min value of 0, and a max value of 1, instead of the start time and end time.
I've explained how to fix this before, and I know at least vhaarr knows about it, but I'll post it here in-case someone else wants to fix it.
I've explained how to fix this before, and I know at least vhaarr knows about it, but I'll post it here in-case someone else wants to fix it.
I do not experience these problems myself, so I don't want to spend time fixing them when I can't debug stuff at the same time. People should just use your castbar addon.
If anyone wants to fix CBRipoff, that would be nice.
Is there any way to hide the casting bar? I prefer using the one in my unitframe, but my unitframes (pitbull) don't support breath/fatigue bars.
You could try oMirrorBars. It's written to only replace those bars, and not include any other 'fluff'. It currently has a very limited set of options, but should work fine, mostly at least :).
I've explained how to fix this before, and I know at least vhaarr knows about it, but I'll post it here in-case someone else wants to fix it.
I do not experience these problems myself, so I don't want to spend time fixing them when I can't debug stuff at the same time. People should just use your castbar addon.
If anyone wants to fix CBRipoff, that would be nice.
Latest version from Haste's site is: 20064 | otravi | 2006-12-1? I couldn't find page for oCB on wowinterface either with a quick search. Is it still under development or abandoned? Is there a newer version somewhere else?
Hmm there's also OminousCastingBar in the svn also... Guess I'm just going to have to try all 3 and see which is working best atm
2007/05/01 14:30:11-662-x1]: DeuceCommander-1.1\DeuceCommander.lua:74: Dewdrop-2.0: [Height] Handler "nil" not available
Ace2\AceLibrary\AceLibrary.lua:96: in function `error'
Dewdrop-2.0-34179 (DewdropLib):1365: in function `FeedAceOptionsTable'
DeuceCommander-1.1\DeuceCommander.lua:74: in function `OnMenuRequest'
FuBarPlugin-2.0-33127:1054: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:1031>
Dewdrop-2.0-34179 (DewdropLib):1802: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1751>
Dewdrop-2.0-34179 (DewdropLib):2630: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:2589>
Dewdrop-2.0-34179 (DewdropLib):429: in function `OnEnter'
Skinner-2.1\SkinMe\Dewdrop.lua:53: in function <Interface\AddOns\Skinner\SkinMe\Dewdrop.lua:50>
(tail call): ?:
Getting that when I try to set the cast bar settings with DeuceCommander, I suspect it has something to do with the recent change to the height and width handler changes to Dewdrop (the mouse scroll input box thing), other mods that use it like Chronometer are fine just CBR is borked afaik. If you can fix it that would be sweet, if not I'll live. Theres always slash commands.
Perfect !
it is what I wanted to say, but I am not enough good to speak in English.
I remember someone saying that enemycasts should stick to the unitframe and with that, with the UF-mod of your choice. Since Blizzard itself stuck the enemy CB feature to the unitframe I find that reasonable.
A simple mod, showing your current target's castbar in a way CBR shows yours would be pretty awesome, but I guess this goes beyond the scope of what the author of CBR (or again, oCB) intended for the addon. IMHO, a second addon (ie. Antagonist) will do the job pretty good, even though it may be a bit heavy and not as pretty as CBR.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumPre-2.0 oCB never intended to contain a enemy castbar, mostly because of the actually cost and code annoyance doing this. It wasn't a simple process which shared events and code in general with the default castingbar, which it is now.
If you wonder, the next release of oCB will contain the ability to spawn a castbar for other valid units (player, target, pet, partyX, raidY). It's written to handle it, with almost only the cost of the frame, and the updating off it. Personally I don't want more then the enemy castbar on my rogue, I can go without having one for my own character.
oCB won't go further then using the in-game API for handling the casts.
(I have a feeling I'll end up reading on these forums as habit again :)
With that in mind my post above seems ridiculous. If it actually doesn't take more than to spawn a new frame and hooking it to another unit ID it would totally make sense that one CB-addon should handle all CB. Why use redundant code in an UF-addon if it actually already is in the CB-addon?
Sorry about that, my knowledge of LUA and LUA in WoW is really non at all, so next time I better just shut up. :)
On a side note, nice to know your kinda back here, Haste.
That's all I would ever want to ask from my casting bar addon. Thanks Haste! I love your addons, BTW.
At the second cast the fishing channeling bar doesn't have a time.
I only get the timer on the very first cast.
This doesn't happen with Sariash' modifed ocb version:
http://www.sariash.de/sunrise/smf/index.php?action=dlattach;topic=8307.0;attach=1078
edit: found rapidcast... investigating =P
http://www-en.curse-gaming.com/downloads/details/6643/ecastingbar-latency-mod/
thanks
Can anyone tell me what the issue is?
CBRipoff, and even OCB, does have a big latency. At firts I guessed this was unavoidable, but then I saw that the casting bar from agUf is much more precise !
Is there any way to change the updating speed in CBR or OCB ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe whole bar chopping while updating is because of the way it uses the StatusBar frame. The add-on sets the min value to whatever the start time was, and the max value to whatever the end time is suppose to be. In 2.0 however, this made the bar jump while moving (ie. seem choppy). You might have noticed that Blizzard's casting bar also has this issue.
It's easy to fix the problem with the jumping, just make it use a min value of 0, and a max value of 1, instead of the start time and end time.
I've explained how to fix this before, and I know at least vhaarr knows about it, but I'll post it here in-case someone else wants to fix it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI do not experience these problems myself, so I don't want to spend time fixing them when I can't debug stuff at the same time. People should just use your castbar addon.
If anyone wants to fix CBRipoff, that would be nice.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou could try oMirrorBars. It's written to only replace those bars, and not include any other 'fluff'. It currently has a very limited set of options, but should work fine, mostly at least :).
Latest version from Haste's site is: 20064 | otravi | 2006-12-1? I couldn't find page for oCB on wowinterface either with a quick search. Is it still under development or abandoned? Is there a newer version somewhere else?
Hmm there's also OminousCastingBar in the svn also... Guess I'm just going to have to try all 3 and see which is working best atm
Ace2\AceLibrary\AceLibrary.lua:96: in function `error'
Dewdrop-2.0-34179 (DewdropLib):1365: in function `FeedAceOptionsTable'
DeuceCommander-1.1\DeuceCommander.lua:74: in function `OnMenuRequest'
FuBarPlugin-2.0-33127:1054: in function <...\FuBarPlugin-2.0\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:1031>
Dewdrop-2.0-34179 (DewdropLib):1802: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1751>
Dewdrop-2.0-34179 (DewdropLib):2630: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:2589>
Dewdrop-2.0-34179 (DewdropLib):429: in function `OnEnter'
Skinner-2.1\SkinMe\Dewdrop.lua:53: in function <Interface\AddOns\Skinner\SkinMe\Dewdrop.lua:50>
(tail call): ?:
Getting that when I try to set the cast bar settings with DeuceCommander, I suspect it has something to do with the recent change to the height and width handler changes to Dewdrop (the mouse scroll input box thing), other mods that use it like Chronometer are fine just CBR is borked afaik. If you can fix it that would be sweet, if not I'll live. Theres always slash commands.
Thanks ^_^
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI know I can code around it, but not sure it's worth the trouble, the slash commands work fine.
I'll see what happens.