Get an Epic Experience with Premium


Data Export Login to Add Favorites
  • World of Warcraft
  • 385 Monthly Downloads
  • Supports: 6.2.0
  • 119,827 Total Downloads
  • Updated 06/24/2015
  • Created 05/03/2009
  • 104 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: v6.2.0.0
Support development! **

About AutoLog

AutoLog - Auto combat Log

As of v4.0.1.9 the development of this addon has been taken over from the original author - Rylanor

AutoLog automatically turns on and off your combat log while going inside or outside raid or dungeon instances. Includes a data broker to show whether or not AutoLog is currently active.

Bug Reports / Change Requests

Please use the ticketing system here.

Why, and for who ?

Because sometimes people who are "making logs" just forgot to launch them, because they may want something to do this alone.


  • Global 'enable' key, that allow you to block all combat logging changes from AutoLog
  • Option to turn logging on for any Heroic 5 player instance
  • Logging preferences 'by raid instance'. Can differ between 10/25/10 heroic/25 heroic
  • Always shows you in the configuration frame if combat logging is turned on or off
  • Supported raid instances (10/25 normal and heroic modes, if available):
    • Naxxramas
    • The Eye Of Eternity (Malygos)
    • The Obsidian Sanctum (Sartharion)
    • Vault of Archavon (+ Emalon / Koralon / Toravon)
    • Ulduar
    • Trial of the Crusader
    • Onyxia's Lair
    • Icecrown Citadel
    • Ruby Sanctum (Thanks to sbourget and mysticalos)
    • Blackwing Descent
    • The Bastion of Twilight
    • Throne of the Four Winds
    • Baradin Hold
    • Firelands
    • Mogu'shan Vaults
    • Terrace of Endless Spring
    • Heart of Fear
    • Throne of Thunder
    • Siege of Orgrimmar
    • Blackrock Foundry
    • Highmaul


  • Configuration frame localised for all clients - if anyone would like to assist with localisation, please visit this page.


  • Rylanor - Original author
  • Warp42 - for the German translation
  • Booblik - for the Russian translation
  • BNSSNB - for the Traditional Chinese translation
  • Maknae - for the Korean translation
  • Aratar - for a bug fix relating to relogging
  • Beregond - for identifying the The Dragon Wastes zone for the Fall of Deathwing and for testing LFR functionality Changed: Updated for 6.2
Added: Mythic dungeon difficulty logging
Added: Hellfire Citadel Changed: Updated for 6.1 Fixed: Ticket 18 Added: Simple data broker Fixed: Stopped logging when in a Garrison Changed: Updated for Warlords of Draenor Added: Challenge mode added by request of Goneril Fixed: Logging toggling when it shouldn't Changed: Logging control rewritten
Fixed: Bug preventing autologging in dungeons Fixed: Removed debugging messages I left in Changed: Added a 5 second delay in an attempt to prevent logging not being reenabled on a consitent basis
Fixed: Compensated for Blizzard bug when using slash command to open the options panel Fixed: Bug reported by aibon3010 Changed: Updated for 5.4
Added: Siege of Orgrimmar
Added: Flex raiding added Changed: Updated for 5.3 Fixed: Bug reported by h2pveiledm thanks to RuniX, Bravolas, djouga Changed: Updated for 5.2 Fixed: Ticket 15, by Jsutan Changed: Update ToC for 5.1 Changed: Locale update Fixed: Ticket 14 reported by CelestialFury Fixed: Zoning bug reported by Jsutan
Fixed: Corrected localisation implementation issue Added: Keybinding option, requested by Dinytran
Added: Full support for current locales
Added: On screen combat log status
Changed: Improved instance detection
Changed: Removed LibBabbleZone dependency
Changed: Removed AceAddon dependency Changed: Update ToC for MoP
Added: Added new MoP raid instances Added: Minor update to add 'The Dragon Wastes' to French locale Fixed: Fall of Deathwing detection, 'The Dragon Wastes' manually added to localisation pending LibBabbleZone update, many thanks to Beregond Added: Added support for LFR raids Added: Added detection for Fall of Deathwing component of Dragon Soul Changed: Temporary fix added for French Dragon Soul translation, tested and working this time :-) Changed: Temporary fix added for French Dragon Soul translation, thanks to RuniX for the translation Changed: Tagged to repackage with latest LibBabble-Zone release Added: Dragon Soul raid instance
Changed: ToC updated for 4.3 Changed: Tagged to repackage with latest LibBabble-Zone release Changed: Tagged to repackage with latest LibBabble-Zone release Fixed: Relogging now checks for log enabling, reported and fixed by Aratar
Added: Now checks normal as well as heroic 5 player instances Changed: Repackaged to include updated LibBabble-Zone translations Added: Firelands
Changed: ToC updated for 4.2.0 Added: Korean localisation thanks to Maknae
Changed: Localisation handling Changed: ToC updated for 4.1.0 Added: Traditional Chinese (zhTW) translation thanks to BNSSNB Fixed: Package externals issue Added: 5 Player instance logging as requested by Eingang Added: Russian localisation thanks to Booblik Added: German localisation thanks to Warp42 Added: Support for Baradin Hold as requested by Asteague Added: Support for Cataclysm raids Initial 4.0 game client release after taking over from the original author - Rylanor


First Previous Page 4 of 11 Next Last
  • #115

    I don't know if author is still active or not, but if you want AutoLog to work with SoO, change the following in Core.lua:

    - Add the value ["55SOO"] = 953 to the array (line 18)
    - Add the value "55SOO" to the raid_list, raid_heroic and raid_lfr arrays (lines 24, 25, 26) 

    That's it.  It now appears in your options as a checkable raid and it autologs just like previous raids.

    I don't care to fix this to work with Flex.  Dev can do that or someone else can post instructions how to (it's not that much harder). 

    Last edited by jsutan on 9/10/2013 6:01:19 PM
  • #117
    Quote from jsutan »

    I don't care to fix this to work with Flex.  Dev can do that or someone else can post instructions how to (it's not that much harder). 

    Checking the LFR box turned it on for flex after adding it in like you said. Thank for the tip!

  • #116

    Yes I'm still around, but not going to get chance to sort this out till the weekend as I'm working away atm.

  • #114

    Thanks to RuniX, Bravolas and Djouga for the info. I did check the wowpedia page shown but it seems it's changed since I looked. I've adjusted the code accordingly. Thanks for the info and thanks for your patience.

  • #110

    I think Blizzard renamed GetRaidDifficulty to GetRaidDifficultyID and GetDifficulty to GetDifficultyInfo.

    I changed all the occurences myself and it works.

    And it is indeed ["54TOT"] = 930

  • #111

    Thanks djouga, but I am already aware of the API changes you mentioned and they have been applied to Auto Log

    Auto Log doesn't use the API GetDifficulty, but it does use it's own implemention. If you have replaced that you have likely overidden the settings that control what difficulty level of instance is logged.

    I could still do with knowing what is returned by:

    /script print(GetRaidDifficultyID())

    As I need to understand why it failed in the first place.

  • #113

    i just changed the valors on Core.lua like this :


            if difficulty == 3 then raidType = "raids10"
            elseif difficulty == 4 then raidType = "raids25"
            elseif difficulty == 5 then raidType = "raids10h"
            elseif difficulty == 6 then raidType = "raids25h"
            elseif difficulty == 2 then raidType = "lfr" end


    and now its working fine at 10man ToT.

    I dont know the value of, but i suppose its 2 :)

  • #112

    Hi, and thanks again for this addon.

    I did test 

    /script print(GetRaidDifficultyID()) 

    when I was in ToT (10 man normal) and
    It returned me 3 instead of 1

    Since it was different to what you expected I searched at

    And here are the new values :


    Number : The player's (or group leader's) current raid difficulty ID preference.

    3 → 10 Player
    4 → 25 Player
    5 → 10 Player (Heroic)
    6 → 25 Player (Heroic)

    Hope this helps you maintaining your add on ^^ I'll try to fix it for my own use

    Last edited by RuniX on 3/10/2013 7:11:27 PM
  • #108

    This doesn't seem to be working for ToT as of today's update. 

  • #109

    I'm not raiding at the moment so this is difficult for me to test. AutoLog works by looking at map ids (which is also where it gets the instance name from) - this part appears to be working, but there may be another map id I'm not aware of. There was also a change in the last patch to the way raid difficulty if reported.

    If would be very helpful if you could type the following commands for me as soon as you enter the instance and let me know what gets printed:

    /script print(GetCurrentMapAreaID())

    /script print(GetRaidDifficultyID())

    You should be getting 930 for the first and 1 for the second (assuming a normal 10 man instance)

  • #106

    update for thunder throne pls

  • #107


  • #105

    Working perfectly now... Thanks for the update

  • #93

    Mogu'shan Vaults does not work correctly (maybe only in german localization).

    Autolog doesn't start the combat log. But after dying it is disabled again (don't know if autolog does that)

  • #97

     I think I either have the wrong Map ID for Mogu'shan Vaults, or the Map ID is changing at the point of re-entry after a wipe. I'm not raiding at the moment so it would be really helpful if I could get those Map IDs.

    They can be seen by typing:

    /script print(GetCurrentMapAreaID())

    I need the ID from entering the instance, and the ID after resurrection when AutoLog is not enabling logging. It would also be useful to have confirmed, is AutoLog actually disabling logging on re-entry? It should disable on ghost, then re-enable on re-entry.

  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Alienware X51 (R3) Giveaway