Advertisement

Recap (Hawksy)

  Download the Curse Client

Last Update: July 30, 2008 (1 month ago)
Category: Combat
Tags: ace2, combat, and raid
Project Manager: Hawksy
Current Version: Recap (Hawksy) v 4.10
(for World of Warcraft 2.4.3)
Downloads Today: 133
Downloads Total: 277,340
Favorites: 1,730
Comments: 478
  • About Recap (Hawksy)
  •  

Recap records damage, healing, and other combat-related events in the area around the player.

  • When installing Recap, please first remove any existing Recap folder from your "World of Warcraft/Interface/AddOns" folder.
  • If experiencing problems with Recap, sometimes it is a bug, and sometimes your saved variables file may be damaged. It is always worth seeing whether removing the saved variables file fixes the problem. To do that, exit the game and go into your "World of Warcraft/WTF/Account/<accountname>/SavedVariables" folder and remove the "Recap.lua" and "Recap.lua.bak" files.
  • If you believe that Recap is properly installed and enabled, but you can't see the Recap main panel, try typing "/recap". If that doesn't work try typing "/recap centre" (or "/recap center").

When reporting a bug, please mention the version number, and double-check it by looking at the bottom of the Recap Options panel.

Despite Curse's new instruction that: "Comments are not the right place to post defects or enhancement requests." I prefer to see your bug reports and requests for improvements right here on the comments page.


__ New in 4.10 __

  • Code to handle three new combat log event types with patch 2.4.3.
  • Bug fixes.
  • Five modules from Ace2 (r78794) included.

__ New in 4.09 __

  • Five healing spells that Blizzard credits to the person being healed are now assigned to the original healer. They are priest Prayer of Mending, druid Lifebloom, shaman Earth Shield, druid Improved Leader of the Pack, and paladin Judgement of Light. Recap makes a best attempt to assign these heals correctly, but can not guarantee to do so in all circumstances.
  • Quick fix for the five new combat log events with patch 2.4.3.
  • Bug fixes.
  • Five modules from Ace2 (r67789) included.

__ New in 4.08 __

  • Bug fixes.
  • Five modules from Ace2 (r67789) included.

__ New in 4.07 __

  • Replaced four option settings (Only Friendly Combatants, Only Party Combatants, Only Player Combatant, and Store Only Friends / Party / Player) with three settings (Hide Group, Hide Other Combatants, and Store Only Displayed Combatants). Hide Group and Hide Other Combatants are both off by default. The group members are shown in green on the main fight panel and include party members, raid members, their pets and controlled mobs, and former members. Most references to 'Friendly' combatants have been modified to refer to 'Group' combatants.
  • Recap now omits intra-group damage (such as Shatter in Gruul's Lair) from the 'Out' column on the main fights panel, and from the Outgoing Details tab. This removes this kind of damage, which is not representative of what the combatant can do, from their DPS. The damage is still tracked in the 'In' column, and on the Incoming, Source, and Target Details tabs.
  • Recap now tracks dispels (which includes the deliberate and accidental breaking of crowd control) with the Recent Events. If you hold down the control key while either double-clicking the combatant row on the main fights panel, or while clicking on a combatant's Recent button, the Recent Events popup panel will be filtered to show only the dispels (Outgoing or Incoming) for that combatant.
  • Double-clicking on the totals row on the main fights panel will now bring up the Recent Events popup panel with ALL recent events. This may be slow on older machines if you have the recent events slider set to a high value. Holding down the control key while double-clicking on the totals row will bring up the Recent Events popup panel with ALL recent dispels. This should be fast.
  • Bug fixes.
  • Five modules from Ace2 (r67789) included.

__ New in 4.06 __

  • In the popup Details panel the information for same-name pets is amalgamated (with Merge Pets on). This amalgamation will save time and memory. Details created by earlier versions of Recap are not amalgamated.
  • All multi-line posts to chat are now limited by the "Report in Multiple Rows" slider (on the Options / Reports tab, default 10 lines, maximum 100 lines). The option to concatenate multiple lines into one long line has been removed.
  • The code for generating live DPS and HPS numbers has been rewritten and should be more accurate. There is still at least one unresolved issue.
  • Bug fixes.
  • Five modules from Ace2 (r67789) included.
  • NOTES:
  • Most mage, warlock, and hunter pet ownership issues have been resolved, but there can still be orphan elementals, pets, or totems.
  • There is currently only one multiple rows slider. If you want to auto-post 5 DPS lines at the end of each fight, and then want to post 50 recent events manually, you will have to move that slider to 50 then back to 5.

__ New in 4.05 __

  • The All Fights panel no longer updates live while synchronization data is being received. There is a new timer that will update the panel a while after the last synchronization data has been exchanged. The timer is also used to auto-post data when synchronization is active.
  • Bug fixes.
  • Five modules from Ace2 (r66043) included.


For descriptions of what was new for versions 3.50 through 3.77, and for versions 4.00 through 4.04, see the file readme.txt.

Version 3.50 was initially uploaded by Hawksy on 2006-December-20

Recap up to version 3.32 was developed by Gello.

  • Downloads (7)
  •  
Advertisement

You need to login or register to post comments.

Benefits of Registration

  • Interact with hundreds of thousands of other gamers on an open social network.
  • Post your stories, news, images, videos, and other content to share.
  • Create a network with your fellow gamers or join an existing one.
  • Gain reputation for everything you do.
 
  • Aug. 10, 2008, 07:42AM (4 weeks, 1 day ago)

    I'm looking for a detailed explanation about the different data between the dps meter addons. I KNOW it was talked about it many times and I vaguely remember that recap were better than dps meter because it was registering aoe damage over dps meter. Other than that I'm not sure... And now that recount is around as well and my guildies using it I would love to explain why I stick to recap (since it's the most trustworthy dps meter out there for sure). Could anyone point me to a nicely detailed explanation please?

    Cheers, and cheers for the addon again and again! :) (I do love the graphical details of recount, maybe some ideas could be implemented from there? ;)

  • Aug. 11, 2008, 12:43AM (4 weeks ago)

    H0PE:

    Here is a partial reply. I welcome other opinions, and I welcome corrections and disagreements with what I'm about to say.

    Each combat meter has its features and its disadvantages. What suits one person may not suit another person.

    For an example of differences: Recount has cool graphs; Recap has a powerful Recent Events tracker; and Violation is the smallest and fastest with fewest features. Last time I checked (several months ago), if you turn on all of Recount's features, and all of Recap's features, Recap uses less memory and less CPU time than Recount.

    Total damage done numbers and total actual healing done numbers should be identical or very similar among all combat meters (though WWS will have trouble properly calculating "actual healing").

    The most visible difference between the combat meters is in their DPS numbers, which is in turn a result of the differences in the measurement of "time in combat" for each combatant.

    For a combatant without pets, Recap takes time in combat from the first damage done by the combatant to the last damage done by the combatant. If the combatant takes time out to polymorph or decurse or banish or click a cube or get a beer or watch internet porn, Recap keeps the timer going. Recount, on the other hand, will turn off the timer temporarily in the middle of the fight if the combatant hasn't done any damage for a while. Recount will also turn off the timer as soon as a combatant dies (even if they have DoTs still up).

    As a result the Recap DPS number is a measure of the combatant's average DPS contribution to the fight. The Recount DPS number, which is usually higher, is a guess at the combatant's peak DPS while they are 'active' in the fight. I happen to think that the Recap way is fairer and easier to understand, but I can see how the Recount way would seem better to other folks. The Recount way is certainly closer to the combatant's peak DPS, which is good for the ego.

    One disadvantage of the Recount way is that if someone burns all their cooldowns and mana, then does nothing for 30 seconds while they are waiting for their mana and cooldowns to come back, they will get an unrealistically high DPS number. Recap will automatically factor in that mana shortage and downrate their DPS accordingly. Which is more realistic? Which is more useful? Your mileage may vary.

    Both types of DPS number have to be treated with some caution. You need to look at total damage done, and you need to consider whether the combatant was doing some essential non-damage stuff in the middle of the fight, or conversely was afk for some of the fight.

    It gets a bit more complicated if the combatant has a pet. I happen to think that the Recap treatment of DPS for a combatant with a pet is significantly fairer than Recount's treatment. Recap treats the combatant+pet as if they were a single entity, adding their damage, and taking their combined time in combat from the first damage done by either until the last damage done by either. The resulting DPS number for the combatant+pet reflects their combined average contribution to the fight.

    Recap keeps independent timers for each combatant for healing done, and for damage received, so that the "HPS" and "DPS In" numbers are independent of the DPS numbers.

    Hawksy

  • July 31, 2008, 02:54PM (1 month, 1 week ago)

    [2008/07/31 14:44:37-3843-x1]: AceComm-2.0-78794 (Recap):2241: attempt to call method 'UnregisterAllComms' (a nil value)
    AceComm-2.0-78794 (Recap):2339: in main chunk

    I had to use the older acecomm-2.0 lib from recap4.9 to avoid that error.

  • July 31, 2008, 04:57PM (1 month, 1 week ago)

    coani:

    Hmm. Those errors are from inside AceComm, where there is code for the UnregisterAllComms function.

    Any hints as to what I might try to see if I can re-create these errors for myself?

    There is also an even newer version of Ace2 available on files.wowace.com. I've not tested it yet.

    Hawksy

  • Aug. 4, 2008, 05:55AM (1 month ago)

    AceComm and AceOO (and maybe other Ace libs) have been screwed up for a lot of addons over the last couple weeks. Some broken versioning out there is loading them in the wrong order. Players have to find the mod with the broken libraries and then rename their "libs" subfolders (or just rename the broken ones).

    For me, it's LD50_abar and BugSack.

  • July 31, 2008, 09:22PM (1 month, 1 week ago)

    hawksy: I got that from the 4.10 you uploaded here, some version conflicts there (which I've seen happen before with comm & oo libraries)

  • July 30, 2008, 09:19PM (1 month, 1 week ago)

    Version 4.10 is now available.

    This version should correct for the erroneous Blizzard code that has been giving errors with the Sunblade Protectors, and possibly also be a fix for the robots in Magister's Terrace though I've not been able to check those.

    The three new combat log events from 2.4.3 dealing with breaking CC should now be handled, rather than simply ignored as they were in 4.09.

    Hawksy

  • July 29, 2008, 04:24AM (1 month, 1 week ago)

    Can Recap be set (either hardcoded or by the user) to ignore certain effects? Like, the main tank is credited with zillions of healing on Illidan because of Drawn Soul, damage done to players by ghosts during Gorefiend seems to be credited to the player, etc. Sometimes that data can be useful, but most of the time it isn't.

    Recap appears to ignore args to the /recap command, or at least I haven't found any subcommands that might let me do this.

  • July 29, 2008, 05:42PM (1 month, 1 week ago)

    Farmbuyer:

    Recap is not currently able to ignore or remove specific effects. It is on my list of changes to investigate. It is trickier than it looks.

    There are a few args recognized by the /recap command, but the only one that is for general use is the emergency "/recap centre" (or "/recap center") for when the main Recap window has gone missing and "/recap" doesn't bring it back.

    The slash commands are not localized, so if you are running (say) a German client you would still have to type the English slash command.

    Hawksy

  • July 28, 2008, 07:28PM (1 month, 1 week ago)

    the Ace2 libs are in the recap folder als always....

    could there be a problem with some ace2 addons using NEWER ace2 libs than those in the recap package?

    because like i said, i did a wowaceupdate some days ago which updated my other addons (all but recap because its on my ignore to avoid problems).

  • July 29, 2008, 05:59PM (1 month, 1 week ago)

    LostHero:

    I don't know the answer to your question, because I don't understand myself how different versions of Ace might interact. I'm using the latest revision of Ace2 without problems.

    Hawksy

  • July 28, 2008, 01:34AM (1 month, 1 week ago)

    i get strange errors since 2 days now (didnt change anything but updated my ace2 addons via wowaceupdater. with recap on its IGNORE list, so i DONT have the recap version from wowace!).

    this is the error i get every time i login on my chars (resulting in recap not working at all)

    http://www.losthero-online.de/images/wow/error.jpg

    in addtion:
    sometimes this error DOES NOT appear, but than recap loads with ALL settings back to default which sucks ^^.

    hope this helps you.

  • July 28, 2008, 08:32AM (1 month, 1 week ago)

    LostHero:

    That first error means that Recap can't find the Ace2 library AceComm. Check that Recap and Ace2 are installed properly.

    I can't figure out why you would sometimes get the RegisterComm error, and sometimes not.

    If all Recap settings revert to the defaults, that means that at some point the Recap data file in SavedVariables may have been damaged or deleted.

    Hawksy

  • July 26, 2008, 08:22AM (1 month, 2 weeks ago)

    I get the same error as the sunwell error when I am in magister's terrace fighting the sentry robot. It happens every time the robot does its chain lightning attack.

  • July 25, 2008, 07:02PM (1 month, 2 weeks ago)

    I am getting the following error when in Sunwell:
    Recap [4.09]:Interface\AddOns\Recap\RecapCombat.lua:1408: attempt to concatenate local 'myElement' (a nil value)

    Just after the patch I got lots of errors so disabled it and grabbed the 4.09 version.
    I am pretty sure I have been in other raids with it working but back in Sunwell it gave me errors again so I disabled it, I could be mistaken but I group a lot and only needed to disable it after the next Sunwell raid.

    Thanks for keeping this mod going.

  • July 25, 2008, 09:00PM (1 month, 2 weeks ago)

    no_idea:

    Thanks for the report. It sounds like the one reported by painstorm.

    I'm investigating.

    Update July 29: I've managed to get into Sunwell. In the combat log events the Fel Lightning cast by the Sunblade Protectors has an unexpected school of 40. It used to be 4 (Fire), so I expect that it is a Blizzard typographical error.

    Hawksy

  • July 26, 2008, 10:27AM (1 month, 1 week ago)

    Yup, I got the same error as lutra123 and no_idea are reporting :)

  • July 21, 2008, 06:28AM (1 month, 2 weeks ago)

    Since updating to 4.09 I get table errors constantly when grouped. An example would be:

    Interface\Addons\Recap\RecapCombat.lua: 4374: table index is nil

    Interestingly, if I enable sync (even if no one else is running recap) the errors do not get displayed. I also have the LUA Errors display disabled in the Help window. Yet these still show up.

  • July 22, 2008, 04:33AM (1 month, 2 weeks ago)

    Same error as MhicAoidh... Doesn't seem to happen solo, but happens constantly in a raid.

  • July 22, 2008, 02:56AM (1 month, 2 weeks ago)

    MhicAoidh:

    Interesting, thank you very much for spotting that. It looks like I might have overlooked something when writing the new code for Judgement of Light.

    Are you running with "Store Only Displayed Combatants" checked? My guess is that you are.

    If so, what is happening is that casting Judgement on a target that is not stored (because of that option) gives an error. I'll have to fix that.

    Hawksy

 
  • Similar Addons
  •  
  1. 2,055 DamageMeters Combat
  2. 1,840 Recount ... Combat
  3. 1,579 Natur EnemyCastBar PvP, Buffs & Debuffs, Raids & ...
  4. 1,391 Decursive Buffs & Debuffs and Combat
  5. 1,308 BigWigs Bossmods Raids & Encounters, Other, ...
Advertisement