Authors CurseForge

Quote from Rabbit »

Thanks alot for those logs, Mist, really good job.
Suffice to say, our minds are boggled by this data. We will investigate.

Glad to be useful. :D

For the record, we killed them second time yesterday, and didn't notice any issues with BigWigs, same versions, same people... It does seem like *sometimes* there are problems, not repeatable, not guaranteed, hard to debug I guess.

I went through the logs myself a bit too, and the most puzzling thing I found was that WoW messages seemed to be wrong, i.e. people afflicted by marks good few seconds after others. Maybe that could be put down to server lag, still few seconds seems like a lot of lag, and nobody complained about having issues during the encounter.

We're going tonight (or at least will try) to 4H, if i manage to get all BW users updated i will tell you if latest commit worked

I JUST updated my BigWigs . . . with that notes (advised not to update) can you suggest a revision that should be safe?

I've been noticing some weirdness when doing Anubrekhan. Two things : 1. The timer for the swarm is usually off by anywhere from 4-8 seconds. 2. Sometimes bigwigs would just quit working (no alerts/timers etc) in the middle of the fight, then after a minute or 2, begin working again.

Quote from Benea »

I've been noticing some weirdness when doing Anubrekhan. Two things : 1. The timer for the swarm is usually off by anywhere from 4-8 seconds. 2. Sometimes bigwigs would just quit working (no alerts/timers etc) in the middle of the fight, then after a minute or 2, begin working again.

1. You notice how the Anub timer says, "Locust Swarm in ~5 seconds."

Any timer that uses a ~ means in ABOUT that time. It's the same thing with the Twin Emp Teleport, Noth's Blink, or any other timer like that. They all have a ~ to indicate it's an approximation.

The ability is on a cooldown and the boss will use it when he damn well feels like it. The timer let's you know when is the earliest point in time that the ability could be used.

2. I've never personally experienced #2, so I can't really comment on that.

At Loatheb, the Doom sync is REALLY not required, all it does is sending alot of junk on the invisible chat chanel.
I can understand the Spore spawn and Remove Curse syncs, but Doom, everybody gets it so it's superfluous and only adds to the problem, the huge spikes on Doom. We have enough problems at it is with disconnecting people.

Proposed change:

function BigWigsLoatheb:Event( msg )
	if string.find(msg, L["doomtrigger"]) then
		self.doomCount = self.doomCount + 1
		if self.db.profile.doom then
			self:TriggerEvent("BigWigs_Message", string.format(L["doomwarn"], self.doomCount - 1, self.doomTime), "Important")
			self:TriggerEvent("BigWigs_StartBar", self, string.format(L["doombar"], self.doomCount), self.doomTime, "Interface\\Icons\\Spell_Shadow_NightOfTheDead")
			self:ScheduleEvent("bwloathebdoom", "BigWigs_Message", self.doomTime - 5, string.format(L["doomwarn5sec"], self.doomCount), "Urgent")
		end
	end
end

Basically, this replaces the old :Event( msg ) function. Also, all LoathebDoom2 entires must be removed, especially the ones in RecvSync function.

As you've been talking about, the "HorsemenMark2"-based syncs were very inaccurate. All I ended up using the messages for was "look at your debuffs" or "look at the group's debuffs in front of you", since the message would very often come 3-5 seconds before the actual mark hit, in most cases.

Consensus among my guild seems to be that not all of the Horsemen are casting their marks at the same time, so we're getting syncs from people who have gotten hit by a mark, but not the mark we're going into. We haven't yet killed them on the HorsemenMark3 syncs, we'll see how that goes next week.

Ammo take a look at the 4H timers, sometimes its not write the correct times on the marks, and the void zone alert is fully unusable. : >

The countdown bar is pretty inaccurate, yeah. Our healers and Blaumeux tanks learned pretty quickly to ignore that and go by the "Incoming Void Zone" message, or WitchHunt message, which is always accurate because she's casting the spell right then, and you have plenty of time to move.

From what I understood from our addon wiz which was at the first kill when they experimented alot (I was not), the marks are correct as long as the horseman in that corner is alive. If the spirit/ghost has already replaced him, bye correct marks.

any LUA 2.0 Bigwigs in the works ? oO

Quote from funkydude »

Quote from Zulej »

any LUA 2.0 Bigwigs in the works ? oO

i think you mean LUA 5.1 wow 2.0

bigwigs is working in the expansion. apart from bossblock at the moment. you can just delete the file to prevent the error.

yes that one
thanks for the help

r18275 through r18280 on /files are missing their externals, fyi.