I've released the newest version of CT Raid Tracker (6.35) to WoWInterface. In it includes three bug fixes.
- Fixed an issue where it was adding Unknown-Server as a member of the raid.
- Fixed a lua error resulting from converting from Raid to Party.
- Lastly made the join/leave recording more accurate.
I am going to try to make these posts every time I update the addons. This update was made to the addon on May 22nd with a quick hotfix that was released on the 24th.
6.35 was released days ago and has the lua error and other issues. Didn't you mean to put a more up to date version out like 6.36?
I replied back on that thread about the hotfix for the lua error from converting from raid to party. I went ahead and updated the 6.35 version rather than making it an entirely new version since it was just a small hotfix. I realize now that can be confusing so I am going to go ahead and update it again with 6.36, as to remove confusion.
What lua errors are you getting?
Julise and I did some testing last night with the current version of the tracker and we no longer have the raid to party errors but she does get errors which seem to be coming from the DKPMon addon. She will post the error for you to see and it usually happens when doing Garrison Work Orders or loots a mob, etc.
When Julise posts her lua error she can add anything that I may have missed. And thanks for the updates.
Thanks for the info! I've seen lua errors like that before, but thought I got them all fixed up. I tried reproducing it in my garrison and couldn't get any lua errors to occur. I'll definitely need a copy of the lua errors that Julise is receiving so that I can keep digging.
Copy of error:
Date: 2015-05-29 00:49:19
Error occured in: Global
Message: ..\AddOns\DKPmon\Looting\looting.lua line 78:
bad argument #2 to 'format' (string expected, got nil)
This error occurred when I looted a random mob. I also receive the error when I loot work order boxes. It's not a consistent error, but a persistent one. I'm running 6.36.
A head's up: The past 3 times I have had this error this past week have ALL been when I was looting while running the Apex daily quest. And if memory serves me correctly, the error occurred on the first time I looted. But not at any other time (this week). Maybe this will help isolate the error. And I will try to be more descriptive when I get this error in the future.
Issues with the tracker continuing to track raiders who have left the raid:
The tracker is NOT properly recording raiders who leave early. This issue has not been corrected from my observations. Our Monday, Tues, Wed (June 01/02/03) the raids have members who left early. The tracker does NOT reflect this. They remain in the tracker until I end it. For example, tonight we had a couple and a 3rd guy who had to leave early – around 7:30pm. They physically LEFT the raid. As raid leader, I removed one of the 3, the other 2 removed themselves. However the tracker tracked them as being in the raid until I ended it at 11:03pm.
I can provide the strings and raider names if needed.
I've unfortunately been unable to reproduce or fix the lua error thus far. It has been hectic for us the past two weeks. We just got settled into our new office in Atlanta and still have some set up and configuration to go. I hope to get some time into the addon this week and I'll let you know!
Sorry for how long it is taking :(. In the meantime, it is still operating sufficiently for you during raids right?