AutoCombatLogger
Overview
Season of Discovery: The new Blackfathom Deeps is under Instances in the settings. Normal is the old 5 player instance only in regular Classic and 10 is the new version in SoD. The game client considers the new BFD a 10 player instance/dungeon and not an actual raid.
AutoCombatLogger automatically enables or disables the combat log based on location. It's specifically tailored to control the logging based on the raid name and difficulty.
Logging can be controlled for the following locations:
- Raid (Can be customized per raid, raid size, and difficulty)
- Instances (Can be customized per instance, current only)
- Arenas (Can be customized per arena)
- Battleground (Can be customized per battleground)
- World
- Garrison
- Brawler's Arena
Currently, you cannot customize logging in the world.
It also provides an LDB launcher and a minimap icon to control it.
Options are set under Interface Options or typing /acl.
Going to add the new raid?
wount autolog in dazar alor yet :(
Hey !
I would love to submit enhancement (like making the behaviour of the Raids config behave the same way as the instance (so only enabled when custom)), is there a way to submit to you this ? (via a github for example ?)
Thanks !
In reply to Isak59:
In reply to talryn1:
At the moment, this is not auto logging in Uldir.
Edit: Works now after the alpha build was just applied to stable. Thanks talryn1!
I've sent the dev a fix for ToS, meanwhile you can get it here: https://pastebin.com/raw/Zk3T81zP
Replace the contents of AutoCombatLogger.lua, not fully tested yet but should be fine.
Arcway(1079), Court of Stars(1087), and Cathedral of the Eternal Night(1146) need to be added
the Return to Karazhan (1115) mapID needs to be fixed
you can find all the mapID's here http://wow.gamepedia.com/MapID#The_Broken_Isles
Autolog by Rylanor is worth checking out.
I used this in WoD and it worked great for me. But this time around i am running into issues.
Today i ran Emerald Nightmare and it only logged the oozes before the first boss but nothing after that. Last week i had it only log the first couple of pulls on the second boss (the eye in the tree) but not the couple after that.
Is there anything i need to do or make sure of?
Still no update for Legion Raids and dungeons. Anyone knows when?
This doesn't work well. It sometimes doesn't log fights, specially at the beginning or end of raids. It logs LFR raids when I set it up not to.
I think Ill just go back to manual logging. Thanks though.
I want to be able to log dungeons and scenario instances, but with WoD, this is logging garrisons, instances at the end of zones, etc. Is there any way to filter to turn on log for dungeons and scenarios only?
The game reports these as a party. I'll have to include additional checks to avoid the logging. I've figured out the garrison and will post an alpha soon that fixes it. I'll need to do the instances at the end of zones to find out how to differentiate that from a real instance.
Hi i just wanted to post to say I was having the same issues as the last two people.
The update the other day fixed my issue and the addon is working properly for me again.
Thanks for the great addon.
I finally had this issue myself. After investigating for a while, I believe it has to do with the updating of the Data Broker icon. I've throttled the update on that icon to once every 5 seconds. So far things are working well.
If you still have issues, please let me know.
Had an issue tonight (EU) where I was in an instance and autocombatlogger didn't automatically "turn on".
I tried reloadui, exited game.
Add-on was loaded (showed the icon on the minimap) and out of date add-ons were enabled.
Even after clicking the button to make it record it didn't.
Also I checked that SoO was checked to be loaded on.
Bug or something to do with me?
This also happened to me except it did record for 1 hour then somehow turned logging off for the rest of the raid (3 hours total) and possible I might of crashed though it normally re-enables even after I crash, first time ending up with an incomplete log.
Edit: Ah cool, will test it out in our raid tonight.
Possible bug report. Starting yesterday with the 5.4.2 patch, I could not get WoW to actually write anything to WoWCombatLog.txt with this addon enabled. Disabling the addon allowed the combat log to be written normally again.
Hi, thanks for feedback. It correctly logged a SoO raid for me just yesterday. Could you give me some more information? It is possible there are changes that I do not know about that could affect it.
I assume it was working correctly for you before. Based on your settings it will enable or disable logging when you zone so it is possible that turns off logging if you manually enabled or disabled it.