Ever wish you could remember the details around that epic crit you delivered in Alterac Valley last week - was that the highest damage I’ve ever delivered, the hardest hit? Who did I hit, was it melee or a spell? How about the highest damage you’ve ever received? You remember C’Thun hit you for some amazing damage last night in the raid, but cannot remember if it the highest damage you’ve ever received.
Hardest Hits is a light-weight addon (less than 25K memory) that solves these problems by helping you keep track and remember the details surrounding your hardest hit or damage dealt and the hardest hit or highest damage you’ve ever received. Hardest Hits keeps track of your historic maximum damage dealt and maximum damage taken in a small, movable window. You are alerted with combat text and a default chat window message when attaining a new maximum. The damage values are maintained across sessions/logins and are able to be reset, recalled and reported anytime with slash, “/” commands or by right-mouse-button clicking the small window.
- Tracks, throughout the lifetime of a character, the hardest hit or maximum damage dealt and the hardest hit, maximum damage received
- Tracks the situational details surrounding the new maximum: date, what player or mob received, dealt the damage, what is their level, what type of damage (spell, melee, thrown), whether the hit was critical, and of course how much
- Alerts you when a new maximum is attained in floating combat text (displays for 5 seconds - green for maximum damage dealt and red for maximum damage taken) and the default chat window
- Captures a screenshot of your Hardest Hit (configurable). The default is enabled. (thank you Tanthalus for the suggestion)
- Able to turn on/off the report going automatically to the default chat window for a Hardest Hit (thank you rybo3282 for the suggestion)
- Able reset window position to the center of the screen (thank you Silentmouse for the suggestion)
- Able to display current configuration, type /hh config
- Report with situational details around maximum hits is available by right mouse button clicking the Hardest Hits window or using slash “/” commands
- Reset the values to zero together or separately
- Roll-back to the previous damage values together or separately
Slash “/” commands:
/hh hide or /hh close - closes the Hardest Hits window
/hh show or /hh open - opens the Hardest Hits window
/hh location - displays your current location - zone and subzone
/hh config - displays current configuration settings
/hh reset - resets all damage to zero
/hh reset_in - resets incoming (worst) mob/player damage received to zero
/hh reset_out - resets damage dealt (best) to zero
/hh resetwindow - resets the window position to center of the screen
/hh report - displays max damage report to default chat window (only you see)
/hh screenshot - turns on/off the screen capture of your Hardest Hits. Screenshot location: ~World of Warcraft\Screenshots
/hh messages - turns on/off the report automatically going to the default chat text on each Hardest Hit.
/hh rollback - resets/rolls back to previous high damage values
/hh rollback_in - resets/rolls back incoming (worst) to previous high damage values
/hh rollback_out - resets/rolls back outgoing (best) to previous high damage values
/hh limit
Report/Tracking Example:Hardest Hits [08/07/08]: Ozik-Black Dragonflight's (lvl 70 Orc Shaman) Frostbolt {Critical} hit Chargerboy (lvl 70) for 2676 Frost damage in Warsong Gulch.
Hardest Hits [08/07/08]: Chargerboy's (lvl 70) melee swing {Critical} hit Jarmenkel-Ysondre (lvl 70 Blood Elf Warlock) for 1493 Physical damage in Silverwing Hold of Warsong Gulch.
Known Issues
Unrealistic, extremely high damage not caused by your abilities skews your record high damage: Quests or events that enable you to do extreme damage with a special prop, like a bomb or charge, can skew your personal best damage output (see quests below). I've begun to exclude damage from those. The following bombing run quests are no longer tracked in Hardest Hits. If you come across quests or events that mess up your numbers, please email me and I'll exclude it and release a new version.
"Arcane Charges", part of The Air Strikes Must Continue (daily quest)
"Dropping Heavy Bomb" from Return to the Abyssal Shelf
"Dropping The Nether Modulator" from The Murketh and Shaadraz Gateways
"Throw Bomb" from Bomb Them Again! (daily quest) and Bombing Run
"Dropping Phase Disruptor" from On Nethery Wings
"Destroy Legion Hold Infernals" from Blast the Infernals!
"Throw Boom's Doom" from Dr. Boom!
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP has a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...