Loading...
» You are not logged in (log in)



You are here: Home » Shaman Mods » WFCDT

WFCDT

Virus/spyware scanned on upload
WARNING: Not been updated since the last patch
Compatible with WotLK ()
Author: shadar
Download size: 36.25 kB
Updated 29/12/2008 (407 days ago)
3,179 total downloads / downloads this week: 2,358 / downloads today: 274
Send PM to Shadar
 

Please log in to vote! Current rating: +5


------------------------------
WFCDT (Windfury Cooldown Timer)
------------------------------
this addon mesures the time between Windfury procs
and displays a bar depending on the shortest time you got between your procs.

i read some forum post today that the cooldown is less then 3seconds
so i decided to write this little addon to mesure the time between procs.

i have not tested it so if you encounter any problems let me know.

the timer starts on the first wf hit.
im not sure if it would be better to start the timer on the 2nd hit
and stop it on the next first hit.
the time between the 1st and 2nd hit is probably so short
that it doesent matter.

------------------------------
commands:
------------------------------
/wfcdt reset - reset values
/wfcdt lock - lock frame
/wfcdt info - show/hide details
/wfcdt center - reset frame position

Patch notes for WFCDT
------------------------------
changelog:
------------------------------
10009
* changed: combat log parsing to make it compatible with 3.0
* changed: combat log parsing for main- offhand seperation
* changed: graph and bar frame seperated
* changed: limited the graph bars to 5-40
* changed: color of the record text (we need blue for the frostbrand enchant)
* added: output for overall wf damage
* added: graph frame and bar creator
* added: new options (dmg/record, oh count/mh count)
* added: frames are now clamped to screen
* added: bar texture to make graph recoloring easier
* added: option to change max bars
* added: option to show/hide the graph
* added: the new options to the reset function
* added: textstrings will be colored
* fixed: added offhand wf spellid (was the reason for missing wf procs)
* fixed: problem when reducing the graph bars and there were more bars then the maximum
* fixed: problem when increasing the max graph bars after bars have been decreased
* removed: localization (this is not needed with the new combat log system)

10008
* added: unit name check to stop catching others wf procs (needs testing)

10007
* changed: toc version to 20400
* changed: combat log parsing updated to 2.4, thanks to Regaenei (Ysera EU)

10006
* added: console commands for all options
* added: console command to reset frame position
10005
* changed: font adjusted
* changed: bar offset adjusted
* fixed: output should be correctly updated if wf procs
* fixed: weapon speed will now update on new record and not on every proc

10004
* fixed: locking the frame will no longer reset the position on reload
* added: button to lock/unlock the frame

10003
* added: when a new wfcd record is made the weapon speed will be displayed
* added: button to show/hide detail informations
* added: reset button
* changed: if details are hidden the record and weapon speeds are displayed on the time bar

10002
* fixed: nil error
* fixed: parser

10001
* changed: update function
* added: time format
* added: bar for best time
WFCDT, archived on 27/01/08
WFCDT, archived on 02/02/08
WFCDT, archived on 18/02/08
WFCDT, archived on 21/02/08
WFCDT, archived on 22/02/08
WFCDT, archived on 05/04/08
WFCDT, archived on 12/04/08
WFCDT, archived on 19/09/08
WFCDT, archived on 29/12/08


Comments

boris
491 days ago
Yeah i think you might be right, i used to use an older vertion before i updated so it was probley the old Saved Var making conflicts, silly me never thought about that... /slap self ill give it a try now Edit: working fine
shadar
502 days ago
thanks for the report, i will try to replicate that error. did you use any older version of this addon? if so please delete the wfcdt.lua in your WTF folder (the game should be closed when doing this) and see if you still get this problem.
boris
503 days ago
Just got an error on login, im using a few addson but the addon was working fine until today... [2008/09/24 17:21:48-353-x1]: WFCDT\WFCDT.lua:462: Usage: WFCDTGraph:SetPoint("point" [, region or nil] [, "relativePoint"] [, offsetX, offsetY]) WFCDT\WFCDT.lua:462: in function `WFCDTPosition' WFCDT\WFCDT.lua:112: in function `WFCDTCheckOnEvent' <string>:"*:OnEvent":2: in function <[string "*:OnEvent"]:1> Edit: This bug can freeze/crash my client of WoW from what i can make out also but not 100% with that
shadar
509 days ago
v10009: this version does not require any spell localization anymore and should catch every proc you get. i also added a graph display, at the moment it displays how much dmg each proc made. i will add some more graph settings later, this one is to compare mainhand vs offhand proc/dmg. i also planing on adding frostbrand and flamethongue to the check but since i cant say if its main or offhand with this spells i have to test some things before i release that part. hope it works and you like it:D hf
shadar
668 days ago
hm maybe there is something wrong with the localization. can you post the exact combat log msg here for wf procs?
Marius
668 days ago
Should it still work with the german client? Doesnt work for me. All the data is empty, even the "Speed" for both hands are set to 0.0 and nothing works at all.
shadar
676 days ago
i got an update from a user today, it worked for me so i uploaded the latest version with the changes for 2.4.0:D thanks to Regaenei (Ysera EU) EDIT: there is a problem in this version, all the wf procs from other players are captured. i will upload a fix next weekend.
mrdummy
682 days ago
With 2.4 patch mod doesn't work anymore. You need change the code to work it again. It doesn't detect my WF's.
shadar
720 days ago
v10004: new button to lock/unlock the frame and locking the frame should no longer reset the position.
shadar
720 days ago
no i have not fixed that bug, but i will fix that now.
mrdummy
720 days ago
Have you fixed problem with saving window location? When i lock the window, after game restart, the window is suddenly in the middle, not on the place where it must be. But if i don't lock the window (thus still moveable) and came back after game restart, the window is still on same place, and not in the middle of GUI. That means there is bug with lock function. Is it fixed or not?
shadar
722 days ago
v10003: if you meka a new cooldown record the weapon speed will be displayed so you can see beter if you had a lot of haste rating(flurry, bloodlust, etc). i also added 2 buttons, one to hide the detail frame and the other to reset your data.
shadar
730 days ago
@mrdummy: where can i download that?^^ to be honest i dont plan to implement much more because i have other addons that need my attention and the purpose of mesuring the time between procs was my goal for this addon. if you want to take it over from here you are welcome to do so.
mrdummy
730 days ago
Perhaps extra stats: - average reacts-per-sec (you can see if it's going better with another weapon or not) - store for example 100 last timings and show it in graph to see the reaction. (also useful to check the effect which weapon is good). This is only storage, building graph is with /wfcdt stats or /wfcdt graph. This is for own analyzing WF in better overview. And add detect too which powers are used if possible. The best measured time is visible as red line in the graph.
shadar
735 days ago
i also got times under 3s (record 2.71s) but i dont see how the addon could cause the times to be lower. all it does it mesure the time between the procs.i already planed some modification options and am aware of the reset when locking the frame.
bozothecrayon
735 days ago
okee, first i seem to have an issue that will cause me to not use the mod. this isn't a huge issue mind you but meh. :p seems everytime i log after placing and locking the mod to the lower left corner it resets to it's default position in the middle of the screen upon logging back in. again this isn't a huge issue but one that my OCDs can't stand. second is i just had a raid and now my best shows as 2.73secs from the observed 2.84secs. i did not equip my haste ring or anything nor had i used heroism before noticing this new time. my guess is that it is a server/client issue. thanks for the mod btw. i like small footprint mods and hope you at some point add ways to customize it. atm i have no need of the timer bar...
Bhim
735 days ago
As for the error, it is gone with the new version. :-)
bozothecrayon
735 days ago
same here on the "less then 3sec WF proc". gave your mod another go after i saw your update and headed to blasted lands. kept healing stream down and water shield up. proceeded to attack and SS every cooldown till WF enchant faded. so after 30mins i had a best WFCD of 2.84secs. since i have very little knowledge of how to make a mod or the workings thereof i can't help in figuring out if it's a mistake with the mod or if indeed the 3sec cooldown isn't set in stone or perhaps affected by haste. at the time of this test i had a passive 100 haste rating. i can add another 31 rating as a test to see if it drops the registered WFCD any further but no time as of writing this to try.
shadar
736 days ago
hm i acctually dont know, the only reason i can think of is that you used a version which did not work. i made a mistake in the parser so it could not catch the wf proc. i also played some hours with the addon active and i got under 3s (2.91s) so im wondering if the cooldown is affected by haste rating or is it because of the server/client delay?
mrdummy
736 days ago
I'm now played with shaman, and can test the addon. Update: When i played first with addon, it don't react with first many WF reactions. The counter is still 0,00s. But much later, perhaps after next level up, it shows finally something in x.xx s. But why now recording and not earlier? (records cooldown now around 4s)
shadar
738 days ago
ok it seems that i had a wrong event in the parser so it acctually did not work. strange that nobody reported that. @Bhim: could you write here if it works now? i have no shaman at the moment to test it.
shadar
739 days ago
thanks for the infos, im not sure if i need a different combat log parser for the german version because its so different from the english one o_O i fixed the error you posted and will upload a version when i checked the parser.
Bhim
739 days ago
The spell name ist "Waffe des Windzorns", the buff on the weapon says "Windfuror RANK (Like: Windfuror 5) and the combatlog gives the following message on hit: "Angriff des Windzorns von Euch trifft TARGETNAME für DAMAGEAMOUNT Schaden." (e.g. Angriff des Windzorns von Euch trifft Abyssischer Flammenbringer ür 114 Schaden.). :-) The fucked up "für" here has to be "f\195\188r" in a LUA file. ;-)
shadar
739 days ago
hmm not sure what causes this error, can you post here the exact words from your combat log when you get a Windfury proc? and whats the german name of windfury? windfuror?
Bhim
743 days ago
I recive the following error message on login (deDE WoW Client [german]): "Interface/AddOns/WFCDT/WFCDT.lua: 167: attempt to compare number with nil" Clicking on "OK" doesn't do anything, but after a few seconds WoW pops up a message saying that my addons are causing a lot off errors and asking if I want to deactivate them.
assailant
745 days ago
nice