Authors CurseForge

Can someone commit this without Priest's Prayer of Mending?

It doesn't work and just wastes space and time.

you can remove it yourself quite easily, just check chronometer/data/priest.lua

Would it make sense to combine the combatlog-parsing with a check for the debufftable of a target?

Iirc the debufftable of a unit works with an FIFO-principle.

So if the table changes, one would first have to check if a debuff has faded or one is gained and then there would have to be some logic applied to check which was gained/faded.

I don't know if it is possible to exactly pinpoint your own debuffs with this method. I think lag could make it a bit complicated. But if it works, it should be possible to keep a closer watch to your own debuffs.

Quote from jjacko »

Quote from Letum »

same problem here

we currently are 2 shadow priests raiding in 25man instances, et we see our vamp touch or pain bars disappear while the dots are still up
I didn t remember such a thing when I was the only one

Well i have similar problems, even when i play solo...

Most of the time i open on mob with :
Vampiric Touch (applying shadow weave debuff)
Then, almost simultaneously : Shadow word pain (applying shadow weave debuff)

Chronometer should show (if no resist):
Vampiric touch (applying shadow weave
Shadow word pain
Shadow weave debuff

*BUT*, most of the time, one of these isnt showing (shadow word pain usually).

Weird thing is after initial problem, if i recast these spells later on mob, chronometer seems to handle them the right way...

Maybe there is a problem when these spells are cast simultaneously ?

Am i only one with this problem ? :(

I made more tests btw :

I removed the Shadow weave debuff and i still have the problem so it is not it causing the problem.
It seems the root of problem comes from casting simultaneously (or so) Vampiric touch and Shadow word pain.
If i wait "some time" between casting the two, Chronomoter creates both timers without trouble.
If i cast them simultaneously :
- either shadow word pain timer isnt created
- either *BOTH* shadow word pain and vampiric touch timers arent created
- *VERY* rarely all is ok

Anyone can help me finding a solution ?


Update :

After more tests, it seems the problem comes from /Stopcasting command i use in my macros casting SWPain and VTouch...

How to change the alpha of a bar not its background?
SetCandyBarColor(name, color, alpha)
It's possible to do some cosmetics changes to do something like : A screenshot of TTSpellTimer.

Hi,

I just wanted to let you know that with the french client the first time I use 'Shadow Word: Pain" with my priest, chronometer displays an error, then it works fine ( I use error Impromment).

Am I the only one with the problem

Can someone explain to me the function of these numbers ?
self:AddTimer(self.SPELL, BS["Battle Shout"], 120, 0,1,0, { d={tn=BS["Booming Voice"], tp=true, tb=10} })
And where can i find more commands like d={tn=BS["Booming Voice"], tp=true, tb=10} } ?

the 3 numbers after the duration relate to the color of the bar.

that second thing you bolded is adjusting the duration based on wether or not the talent booming voice is had.

An issue i noticed last night while using chronometer on my warlock. I enslaved a demon and I got the timer bar just fine. The enslavement broke after a couple of minutes. I re-enslaved the same demon and did not have a timer for it. Any ideas?

Quote from chuckg »

Quote from Jakobud »

I'm not sure if this has been mentioned yet:

Warlock's "Howl of Terror" rank 2 spell, chronometer has the duration at 14 seconds. This is incorrect it would be 8 seconds.

Also, the Howl of Terror rank 1, I haven't tested it with chronometer but it is a 6 second duration. Might want to check this as well.

Here's the fix:

self:AddTimer(self.SPELL, BS["Howl of Terror"],    	 6, 0,0,0, { d={rs=2}, dr=1 })

Ya I know I can fix it myself but FYI, this error is still in the code, might want to update it for the next release or Chrono. Probably like 100 other warlocks out there who use the addon but dont know of this fix.

Is it possible to get timer bars to show up for actions that you or your pet performs on 'focus' targets? For example, when I set a target to be my focus, and I (warlock) tell my succubus to cast Seduction on my focus target. I currently don't get a Seduction bar in Chrono, but it would be hella nice if I did. Any thoughts?

Is there a fix yet for Fire Vunerability? Right now only the first 5 Scorchs are recognized.

Quote from mymycracra »

Hi,

I just wanted to let you know that with the french client the first time I use 'Shadow Word: Pain" with my priest, chronometer displays an error, then it works fine ( I use error Impromment).

Am I the only one with the problem

Same probleme here.
Another probleme : chronometer do not detect the talent "Improved Shadow word : Pain" which increased the duration of the SW:P spell by 3/6sec. THe bar lasts only 18sec whereas my spell lasts 24sec.

EDIT : I use a french version of WoW.
If a translation is necessary, i can provide the name of all spells in french but i cant make the localisation my self, too weak in .lua :x

Quote from bofra »

Is there a fix yet for Fire Vunerability? Right now only the first 5 Scorchs are recognized.

Jep, this REALLY sucks. Anyone got a fix for this problem?

Okay, as far as all of the complaints about Fire and Shadow Vulnerability - I know about this, it has been a bug since this was AceTimer, and the fix for it doesn't fit well into the AceTimer architecture that Chronometer still uses (and even if I do implement it, it still wont' be perfect).

Now, about spells not being recognized, especially when cast in quick succession or in macros. This is hopefully fixed, since I have moved to SpellEventsLib for spellcast detection. However, I never really encountered this issue myself so I'll rely on those who have had this problem to verify that this fixes it.

After the latest update tonight I got the following error.
[2007/04/16 21:31:05-317-x1]: Chronometer-0.10\Core\Chronometer.lua:726: bad argument #1 to 'gmatch' (string expected, got nil)
<in C code>: ?
AceEvent-2.0-32527 (BigWigs):322: in function `TriggerEvent'
AceEvent-2.0-32527 (BigWigs):1009: in function <...ce\AddOns\BigWigs\Libs\AceEvent-2.0\AceEvent-2.0.lua:1002>

Quote from Snarfle »

After the latest update tonight I got the following error.
[2007/04/16 21:31:05-317-x1]: Chronometer-0.10\Core\Chronometer.lua:726: bad argument #1 to 'gmatch' (string expected, got nil)
<in C code>: ?
AceEvent-2.0-32527 (BigWigs):322: in function `TriggerEvent'
AceEvent-2.0-32527 (BigWigs):1009: in function <...ce\AddOns\BigWigs\Libs\AceEvent-2.0\AceEvent-2.0.lua:1002>

Okay, I think I fixed it, but I don't know how to duplicate what you were doing to test it. If it still happens, please let me know what exactly you're doing to cause it (spell you're using, etc.)

I'll give it a try. It occurred when I first started moving after logging in.

It happened again when I was mounting my epic mount (flying)

[2007/04/16 22:11:26-318-x1]: Chronometer-0.10\Core\Chronometer.lua:726: bad argument #1 to 'gmatch' (string expected, got nil)
<in C code>: ?
AceEvent-2.0-32527 (BigWigs):322: in function `TriggerEvent'
AceEvent-2.0-32527 (BigWigs):1009: in function <...ce\AddOns\BigWigs\Libs\AceEvent-2.0\AceEvent-2.0.lua:1002>

--------------------------------

Quote from Bhattu »

Quote from Snarfle »

After the latest update tonight I got the following error.
[2007/04/16 21:31:05-317-x1]: Chronometer-0.10\Core\Chronometer.lua:726: bad argument #1 to 'gmatch' (string expected, got nil)
<in C code>: ?
AceEvent-2.0-32527 (BigWigs):322: in function `TriggerEvent'
AceEvent-2.0-32527 (BigWigs):1009: in function <...ce\AddOns\BigWigs\Libs\AceEvent-2.0\AceEvent-2.0.lua:1002>

Okay, I think I fixed it, but I don't know how to duplicate what you were doing to test it. If it still happens, please let me know what exactly you're doing to cause it (spell you're using, etc.)