CheckInteractDistance works fine on mobs though (given that you're using a UnitID and not a GUID). Here's the code I wrote for my version of BigWigs, which works just fine on Putricide:
local bossId = self:GetUnitIdByGUID(36678);
if bossId and CheckInteractDistance(bossId, 3) then
self:FlashShake(71255)
end
That could be the "random combatlog error". Check if you have something in your combatlog (anything really). If not, just relog (a reload is NOT sufficient) and it should be fixed.
That could be the "random combatlog error". Check if you have something in your combatlog (anything really). If not, just relog (a reload is NOT sufficient) and it should be fixed.
It's not, several combatlog-dependant addons are working, including Skada. Some of the latest revisions broke some kind of detection i guess.
What language client are you using? One reason it would break is if a missing localization caused AceLocale to send an error, causing Blizzard's error handler to break the addon. I may just turn off AceLocale sending error messages since I have a script to submit them. It has caused way too many problems.
What language client are you using? One reason it would break is if a missing localization caused AceLocale to send an error, causing Blizzard's error handler to break the addon. I may just turn off AceLocale sending error messages since I have a script to submit them. It has caused way too many problems.
I'm not sure it wouldn't work since I haven't changed anything about detection for a while. Your client would default to English phrases. What version are you using?
Yes, that's an accepted feature I'm going to work on. See the ticket about the proximity window.
I'm not sure it wouldn't work since I haven't changed anything about detection for a while. Your client would default to English phrases. What version are you using?
I'm allways running the latest version to be found on wowace. so currently v471. I think this started occuring after v468, several of my guildmembers also reported no timers/bars after updating to v468. It's quite random though, so i'll see if it still happens on the raid tonight.
That could be the "random combatlog error". Check if you have something in your combatlog (anything really). If not, just relog (a reload is NOT sufficient) and it should be fixed.
If you get the random combatlog error, Shadowed's addon fixes it with no relog/zone required.
DXE failed to start on rotface last night. I hope this fail to start bug can be fixed since it pops up time to time. We do everything hardmode so maybe that's why it's happening.
this often happens after i switched speccs and made a ui reload(have to do this combination quite a lot because of range check issues with grid and changing spell ranges)
strangely though another ui reload fixes it for me
Hi, my guild is currently working on Heroic Sindragosa and we modified the Encounters.lua phase 2 positions to match our strategy. The base file was from v471, but comparing the Sindragosa portion to v477 there doesn't appear to be any changes aside from a small Instability modification.
Our problem is that half the time the arrows and "MOVE XX XX" notifications do not show up even though all 6 symbols are correctly assigned. I'm wondering if it has anything to do with this line?
"scheduletimer",{"checkbeacon",0.2}, -- allow time for raid icon to set
We plan on changing 0.2 to 1 before we go back at it. Anyways, any assistance you can give me would be appreciated. The Encounters.lua I am using is located at http://www.woodle.org/files/Encounters.lua (except we modified the version number to 35 to distribute it)
The code is correct. It could be scheduling too fast. I don't know if they changed anything to Sindragosa in the patch. I'll have to look at the logs next week unless you have one.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
CheckInteractDistance works fine on mobs though (given that you're using a UnitID and not a GUID). Here's the code I wrote for my version of BigWigs, which works just fine on Putricide:
Here are some combat log entries if that helps.
It's not, several combatlog-dependant addons are working, including Skada. Some of the latest revisions broke some kind of detection i guess.
I play on a EU server, so enGB i guess.
Yes, that's an accepted feature I'm going to work on. See the ticket about the proximity window.
I'm not sure it wouldn't work since I haven't changed anything about detection for a while. Your client would default to English phrases. What version are you using?
I'm allways running the latest version to be found on wowace. so currently v471. I think this started occuring after v468, several of my guildmembers also reported no timers/bars after updating to v468. It's quite random though, so i'll see if it still happens on the raid tonight.
If you get the random combatlog error, Shadowed's addon fixes it with no relog/zone required.
http://www.wowinterface.com/downloads/fileinfo.php?id=16001
this often happens after i switched speccs and made a ui reload(have to do this combination quite a lot because of range check issues with grid and changing spell ranges)
strangely though another ui reload fixes it for me
Our problem is that half the time the arrows and "MOVE XX XX" notifications do not show up even though all 6 symbols are correctly assigned. I'm wondering if it has anything to do with this line?
We plan on changing 0.2 to 1 before we go back at it. Anyways, any assistance you can give me would be appreciated. The Encounters.lua I am using is located at http://www.woodle.org/files/Encounters.lua (except we modified the version number to 35 to distribute it)
Sindragosa Encounter: