Authors CurseForge

Yeah much much nicer, thanks! No more 5 lines of spam, and easy to read.

Is there any way to track the number of bosses killed? For instance, in hc OK you can skip 3 bosses (Elder Nadrox, Amanitar and Jedoga Shadowseeker), most groups skip just 2, some just 1 and some groups do them all. The run time of course depends on how many bosses you kill. Just wanted to hear if you had any thoughts about this? :)

I found a bug in the output options.

If you have anything checked under General Options > Announce Char Runtimes, even if you have "Announce Overall Runtimes" unchecked it'll still display anything you have checked in Announce Char Runtimes.

Found another bug. If you do a run with a 00 seconds in it it'll skip the seconds portion on the output

[09:55] [PL] [80:Kguku]: DSR: Azjol-Nerub (Heroic) Current Runtime: 11:03 Avg: 10:15 Total Runs: 3 Best: 08

I believe that run was 8 minute flats, but as you can see it's not doing the :00 afterwards. Might want to take a look at that.

Feature idea/request: could you have it show the time
you have been waiting in the queue for the dungeon to start and keep an average of that?

DSR v0.7-beta-5-g1fb2dd5

Bug:
17:08] DungeonSpeedRunner: End Of Instance: Utgarde Keep (Heroic)
[17:08] DungeonSpeedRunner: Started at: 01/28/10 16:55:05
[17:08] DungeonSpeedRunner: Ended at: 01/28/10 17:08:33
[17:08] DungeonSpeedRunner: Duration: 13 Min 28 Sec
[17:08] [PL] [80:Kguku]: DSR: Utgarde Keep (Heroic) Current Runtime: 13:28 Avg: 14:31 Total Runs: 9 Best: 11:37

As you can see it's outputting data twice, one of which is super spammy. I have it set to output via Channel:Party, so it should only be doing that. I can't find anywhere to turn off the spammy portion.

Well if the user has it set to output to a chat already I'm not quite sure why you would want it to do it a second time. Hence why I would consider it spammy, as you're already seeing it once via the method you chose to output it as.

Can you have the timers and run totals align to column?

v0.7-beta-8-g1359ca1 (updated from older version), USEnglish client/server. Head into Interface, Options, DungeonSpeedRunner, click the General Options tab. Verbose Output is unchecked, I check it.

Change to Announce Runtimes tab, click one of the (old) entries there, error is thrown up:

["message"] = "AceLocale-3.0: DungeonSpeedRunner: Missing entry for 'Verbose Output':\nDungeonSpeedRunner-v0.7-beta-8-g1359ca1\\DungeonSpeedRunner.lua:543: in function <...ace\\AddOns\\DungeonSpeedRunner\\DungeonSpeedRunner.lua:532>\nAceConfigRegistry-3.0-11:306: in function `app'\nAceConfigDialog-3.0-44:1755: in function `Open'\nDungeonSpeedRunner-v0.7-beta-8-g1359ca1\\DungeonSpeedRunner.lua:436: in function `OnClick'\nStatBlockCore-2.65\\StatBlockCore.lua:598: in function <Interface\\AddOns\\StatBlockCore\\StatBlockCore.lua:596>\n\n  ---",
            ["type"] = "error",
            ["time"] = "2010/02/09 00:58:12",
            ["session"] = 811,
            ["counter"] = 1,
        }, -- [302]

This consistently fails to recognize final boss kills in both heroic Forge of Souls & Pit of Saron (haven't tried it yet in Halls of Reflection).

Consequently, the timer keeps on running after the instances are over. You have to remember to stop it manually if you want the run to be recorded at all. There are no problems with "old" heroics.

Using v0.7-beta-11-ge4a26d0, USEnglish client/server, WoW 3.3.3a live.

I used the LFD tool for assembling the groups. 4 times for Pit of Saron, once for Forge of Souls. But they were selected as "Specific Dungeons" in the LFD tool.

The timers started properly at the beginning of each of those dungeons. But they did not stop properly.

Latest Pit of Saron run, the timer kept on running after the boss was killed. But after leaving the group (and getting ported back to where I was before the group was assembled), the timer stopped counting automatically...and the run was not recorded. Was not able to stop the timer manually.

If the mod is unable to properly handle anything other than random LFD groups (due to it looking only for the LFG_COMPLETION_REWARD event), it really should not start a timer on other group types (like the aforementioned Specific Dungeon LFD group). Especially if its going to automatically discard the timer after leaving the dungeon as it does now. That is, if there is any event to look for at the start of a dungeon that is specific for that group type.

Of course, would be nice if it recorded any dungeon run types someone cares to do. Barring that, provide a selectable option to have it not automatically discard timers when you leave a dungeon and its still running. Instead when that happens, the person can choose to manually stop it.