Download
(48Kb)
Download
Compatible with Retail, Classic & TBC
Updated: 02-26-24 04:46 PM
Pictures
File Info
Compatibility:
Classic (1.15.0)
WOTLK Patch (3.4.3)
Updated:02-26-24 04:46 PM
Created:09-16-19 04:27 PM
Downloads:4,658
Favorites:2
MD5:
Categories:Classic - General, Combat Mods

AutoLoggerClassic

Version: v2.2.4-release
by: cloudbells [More]

AutoLoggerClassic

A World of Warcraft: Classic addon for automatically triggering combat logging on and off in raids.

If you notice any inaccuracies or bugs please let me know!

/alc and /autologgerclassic will open the config.
/alc minimap and /autologgerclassic minimap will toggle the minimap button on or off.

Features

Configure in which raids to automatically combat log in the options. Enter said raid and you will automatically be combat logging (and be notified of it)! Make sure to enable advanced combat logging in Interface > Network.

AutoLoggerClassic
v2.2.4-release (2024-02-26)
Full Changelog
  • Fix new raids not being logged by default
  • Wrap setting missing raids to default in else
  • Set newly added raids to default
    Fix for when new raids are added in SoD they are default not logged
Archived Files (17)
File Name
Version
Size
Author
Date
v2.2.3-release
48kB
cloudbells
02-14-24 01:44 PM
v2.2.2-release
48kB
cloudbells
01-31-24 10:06 AM
v2.2.1-release
48kB
cloudbells
12-26-23 12:31 PM
v2.2.0-release
48kB
cloudbells
12-26-23 08:32 AM
v1.7.1-classic-release
24kB
cloudbells
03-23-22 12:23 AM
v1.7.1-classic-release
24kB
cloudbells
03-23-22 12:23 AM
v1.7.1-classic-release
24kB
cloudbells
03-23-22 12:23 AM
v1.7.1-classic-release
24kB
cloudbells
03-23-22 12:23 AM
v1.7-release
24kB
cloudbells
04-15-21 07:39 PM
v1.7-release
24kB
cloudbells
04-15-21 07:39 PM
v1.7-release
24kB
cloudbells
04-15-21 07:39 PM
v1.7-release
24kB
cloudbells
04-15-21 07:39 PM
v1.7-release
24kB
cloudbells
04-15-21 07:39 PM
v1.6-release
24kB
cloudbells
04-13-21 02:09 PM
v1.5-release
206kB
cloudbells
04-13-21 01:34 PM
v1.5-release
24kB
cloudbells
04-13-21 09:53 AM
v1.4-release
24kB
cloudbells
03-26-21 05:38 AM


Post A Reply Comment Options
Unread 10-11-19, 07:47 PM  
Nihlo
A Murloc Raider

Forum posts: 7
File comments: 158
Uploads: 0
Works fine at Ony and in MC, thanks again.

Would be cool to have some kind of mechanism to turn the logging off again. If you don't log out after raiding and kill all kinds of stuff, it's all in the logs obvs. Kinda hard to do I know, leaving the instance doesn't always mean the end of the raid since you might go elsewhere raiding, repair or whatever.

Maybe some kind of info after a while you have been out of raid and haven't stopped logging manually yet ?
Report comment to moderator  
Reply With Quote
Unread 09-25-19, 04:34 PM  
cloudbells
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 4
Uploads: 3
Originally Posted by Nihlo
Yeah, logging for 20man and 40man is enough, don't need ubrs raids either. World Bosses would be interesting but I guess there is no use trigger the log everytime you come to Azshara, Ashenvale, Blasteds etc.

Maybe a simple solution for Ony is to just post a chat message ? Like:
"You might be at Ony now, autologging doesn't work so don't forgt to trigger manually."

Or a trigger when you engage certain mobs ? The Onyxia Trash is unique...or Azuregos etc.


Originally Posted by cloudbells
Yeah I noticed the same. I've made a fix which will be pushed tomorrow, and also disabled support for dungeons since i) there isn't support for dungeons on WarcraftLogs (for good reason), and ii) the solution required minimal effort and allows the addon to not have to create a bunch of timers to check when the player enters a dungeon/raid.

The issue was (specifically for Onyxia) that the ZONE_CHANGED_NEW_AREA event triggered outside the instance, as is the case for e.g. Deadmines and some other dungeons. This then triggered a check for which instance the player was in, and since the player was still in Kalimdor, combat logging didn't trigger. The only way to trigger it then was to either /reloadui or check the Onyxia's Lair checkbox twice while inside the instance.

It's frustrating that there is no good event for when a player enters an instance, only raid.

If you want an all-around logging addon that will work for dungeons as well, then there are other ones available :-) I mostly made this one for myself quickly.
Well, it should work for all raids now.
Report comment to moderator  
Reply With Quote
Unread 09-20-19, 08:32 PM  
Nihlo
A Murloc Raider

Forum posts: 7
File comments: 158
Uploads: 0
Yeah, logging for 20man and 40man is enough, don't need ubrs raids either. World Bosses would be interesting but I guess there is no use trigger the log everytime you come to Azshara, Ashenvale, Blasteds etc.

Maybe a simple solution for Ony is to just post a chat message ? Like:
"You might be at Ony now, autologging doesn't work so don't forgt to trigger manually."

Or a trigger when you engage certain mobs ? The Onyxia Trash is unique...or Azuregos etc.


Originally Posted by cloudbells
Yeah I noticed the same. I've made a fix which will be pushed tomorrow, and also disabled support for dungeons since i) there isn't support for dungeons on WarcraftLogs (for good reason), and ii) the solution required minimal effort and allows the addon to not have to create a bunch of timers to check when the player enters a dungeon/raid.

The issue was (specifically for Onyxia) that the ZONE_CHANGED_NEW_AREA event triggered outside the instance, as is the case for e.g. Deadmines and some other dungeons. This then triggered a check for which instance the player was in, and since the player was still in Kalimdor, combat logging didn't trigger. The only way to trigger it then was to either /reloadui or check the Onyxia's Lair checkbox twice while inside the instance.

It's frustrating that there is no good event for when a player enters an instance, only raid.

If you want an all-around logging addon that will work for dungeons as well, then there are other ones available :-) I mostly made this one for myself quickly.
Report comment to moderator  
Reply With Quote
Unread 09-20-19, 07:07 PM  
cloudbells
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 4
Uploads: 3
Originally Posted by Nihlo
Thanks for the addon, works nicely in MC but doesn't trigger at Onyxia.
The zone is "Onyxia's Lair" while the exact zone name might be different, forgot the cmd to show it though.
Yeah I noticed the same. I've made a fix which will be pushed tomorrow, and also disabled support for dungeons since i) there isn't support for dungeons on WarcraftLogs (for good reason), and ii) the solution required minimal effort and allows the addon to not have to create a bunch of timers to check when the player enters a dungeon/raid.

The issue was (specifically for Onyxia) that the ZONE_CHANGED_NEW_AREA event triggered outside the instance, as is the case for e.g. Deadmines and some other dungeons. This then triggered a check for which instance the player was in, and since the player was still in Kalimdor, combat logging didn't trigger. The only way to trigger it then was to either /reloadui or check the Onyxia's Lair checkbox twice while inside the instance.

It's frustrating that there is no good event for when a player enters an instance, only raid.

If you want an all-around logging addon that will work for dungeons as well, then there are other ones available :-) I mostly made this one for myself quickly.
Last edited by cloudbells : 09-20-19 at 07:08 PM.
Report comment to moderator  
Reply With Quote
Unread 09-19-19, 11:31 AM  
Nihlo
A Murloc Raider

Forum posts: 7
File comments: 158
Uploads: 0
Thanks for the addon, works nicely in MC but doesn't trigger at Onyxia.
The zone is "Onyxia's Lair" while the exact zone name might be different, forgot the cmd to show it though.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: