The last revision of FuBar_CombatTimeFu (r35439) was in May...2007. Due to the WoW 2.4 combat log changes, its now quite unreliable for timing fights. Usually detects the start of a fight OK, but very often the timer keeps running when the fight is over. Which is problematic on bosses (among other times).
I'm aware of the new, working StatBlocks_TimeInFight, but am still using FuBar here. DeadlyBossMods has a combat timer too, but the guild here is using BigWigs. In my (and other users) quite limited screen space, adding another StatsBlock block on the screen to replace a partially dead FuBar plugin isn't the most preferable option ;).
The author Saroz is still around; any interest in an update? Or disinterest?
The mod is unusable here (and likely for others); it only retains and shows you your "longest" fight time in the session.
This issue makes TimeInFight useless for keeping track of any combat event where you want to see the last time taken. Such as boss fights during a raid/instance. If one boss takes a shorter time than another, you won't get the time. One group pull compared to another. Soloing. And so on.
Funky responded in the thread about contacting the author and I PMed the author, but no response so far (3 weeks). Funky fixed it bugging out (reported above). But since posting about the issue, there has been a further commit by the author (for "display issues"), but no design changes to show last fight time taken.
This design is unlike FuBar_CombatTimeFu, which retains and shows your last fight time. At least when it stops running after a fight, which doesn't always happen due to the 2.4 combat log changes. Note that I have yet to see an occasion where it improperly kept running after a boss fight (it still always provides the correct time). It only keeps running sometimes during trash & soloing.
So until the design of StatBlocks_TimeInFight is changed, there is still a place for FuBar_CombatTimeFu. Hopefully it can be updated with the 2.4 combat log changes so that it works properly 100% of the time and doesn't keep running occasionally after a fight is over.
The latest updates to FuBar_CombatTimeFu today by Saroz have fixed the issue with the timer continuing to run after combat occasionally/often. r77606 reliably stops running after every combat tested so far. Thought the problem had something to do with the combat log as it only started happening after 2.4 hit. Nice work.
And...Funky's changes to latest StatBlocks_TimeInFight (r77618) allow showing the last combat time in addition to the longest fight time of the session. So its a lot more useful, to the guild here at least (and hopefully others). Also nice work :).
So fanboys of each bar mod now have less reason to switch to the other (that is if there was anyone besides me who preferred CombatTimeFu's design) :D.