Authors CurseForge

r76755 | 7destiny | 2008-06-15 12:55:03 -0400 (Sun, 15 Jun 2008) | 1 line
Changed paths:
  M /trunk/BigWigs/Sunwell/Muru.lua

BigWigs: Sunwell/Muru: add void and humanoid spawn count

http://fish.wowace.com/browse/WowAce/trunk/BigWigs/Sunwell/Muru.lua?r1=76660&r2=76755

Funky, please revert this change. It is absolutely not necessary to know the total number of mobs that have spawned in this encounter, and adding numbers to every single timer bar and warning is pointless, annoying clutter.

Quote from Phanx »

r76755 | 7destiny | 2008-06-15 12:55:03 -0400 (Sun, 15 Jun 2008) | 1 line
Changed paths:
  M /trunk/BigWigs/Sunwell/Muru.lua

BigWigs: Sunwell/Muru: add void and humanoid spawn count

http://fish.wowace.com/browse/WowAce/trunk/BigWigs/Sunwell/Muru.lua?r1=76660&r2=76755

Funky, please revert this change. It is absolutely not necessary to know the total number of mobs that have spawned in this encounter, and adding numbers to every single timer bar and warning is pointless, annoying clutter.

I disagree with you. For me it's a very good change. I know that i have to switch tu m'uru to kill him before the 10th sentinel and now i can see the void sentinel number and adapt my dps on the void and m'uru to be just in time.
Maybe an option to disable this function but for me it's a good one.

ps: sorry for my bad english i'm french.

But that's relevant only to the specific strategy your guild is using. It is not universally useful for the encounter. Some time back it was declined to modify the Curator mod to include the number of spawned Astral Flares; this is exactly the same kind of thing.

I'd have no problem with that. It just annoys the crap out of me when nice clean useful addons get bulked up with a bunch of special-purpose clutter.

I have a request for Felmyst. With the blacklisting of the Main Tank on encapsulates, would it be possible to enable the debuff detection of encapsulate on the Main Tank only? This way you don't get the erroneous encapsulate spam but melee is alerted to run out, even if it is a few seconds later.

Another idea is for encapsulate alerts to be throttled (After warning ingore target switched for say, 5 seconds), since the Main Tank alert is always second after the targeting goes back, as just now we had it alert for 2 people within 2 seconds. The 2nd didn't pull aggro or anything, not sure why they got targeted.

I noticed that when Entropius casts Black Hole, he'll target the person that the gravity ball will be spawning under. Would it be feasible to check his target then, and "/say Gravity Ball on me!" if you're his target? Perhaps it's player error on my part, but as melee I can never see the damned orb spawning until I'm flying around the room.

I wrote a bigwigs external module that tries to announce who the target of Entropius' gravity ball is. It's not perfect, since it has to guess who the main tank is and watch when the boss targets someone other than that tank, but it seems to mostly work. One warning though: as I was testing it, timers for phase 1 would sometimes not start properly. I'm not sure if this is a problem with my code, or if there was some other factor in the raid/my config that I'm not aware of.

I'm open to suggestions as to how I could improve the code and functionality.

firstly, the main tank detection routine is bogus. either use blizzard's maintank unit or scan raidXtarget until you find entropius. checking rage bars and righteous fury buffs is a waste of time.

secondly, don't compare UnitName. use tonumber(string.sub(UnitGUID("token"),6,12),16) and check against 25840

It is not part for our strategy for example, im guessing not even most. With variation from setups, sentinel spawnpoints and fuckups we go into M'uru in between 4-6 waves. Keeping up phase 1 longer is easier than going into a wrong timed phase 2. For me the numbers would add no extra usable information as its just a raidcall being made based on M'uru's health, humanoid timer and sentinel timer.

That being said, i wouldnt mind the counters really if i can turn them off. The enrage or a combat timer already gives you the number in a way, not even talking about the possibility of counting, but i guess that would defeat the purpose of addons helping you with even the simplest tasks :)

Please make Kalecgos Module announce to raid warning the portal numbers somehow. I don't always have a chance to announce it myself to vent and some people mess up. I would really appreciate this invention.

Please do not add more "counters" to ability warnings/timers. BigWigs isn't supposed to play the game for you. You still have to pay attention and be aware of what's going on. As with the last counter that was added, not all strategies for killing a particular boss make use of counters. For Kalecgos in particular, I'm not even sure how it could possibly be valuable to know how many portals have opened, as you can't say "okay, A B and C take the first portal, X Y and Z take the second portal" because it's quite possible that X will be targeted by the first portal, and Q by the second portal, screwing up your planned rotation. If you somehow manage to work a portal count into your strategy, great, but please don't force everyone to clutter their screen with additional information that is more likely than not totally useless for them.

Phanx, you try managing tank rotations without knowing how many portals were opened already. We have to always run DBM and BW simultaneously just because BW does not let people know the portal sequence number. Seriously, BW isn't supposed to play game for me, but it is intended to be a Boss Encounter helper mod, and i guess helping tank rotation is one valuable thing boss mod can do for Kalecgos encounter. I am not willing to force anyone to clutter their screen with what ever, i just asked to change the way portal notification is displayed: not just "Portal soon" but "Portal #4 soon". You can't say that'll flood your screen, eh?

The more text is shown on every bar, the more crap I have to wade through to figure out what the bar is for. I'd actually be happier if the bar just said "Portal" and nothing else. :P

That said, I've done Kalecgos with two guilds, both with quite different strategies, and neither use portal numbers. My current guild uses three tanks, and basically says, "Tank A go with the first portal, Tank B go with group 2, Tank C go with group 4" and swaps if needed due to a tank getting targetted by the portal. When someone in group 2 is ported, Tank B takes the portal, followed by the rest of group 2. Whether or not group 2 is targetted with the second portal or the fifth portal doesn't make any difference.

No, TankB goes with Group2, as in the raid group. If Group2 gets targetted by the second portal, then TankB is indeed going with the second portal. But if Group2 doesn't get targetted until the fifth portal, then TankB is going with the fifth portal. Only the first tank goes with a specific portal, and that's the first portal. The other two tanks go whenever the group they're assigned to gets ported. I don't think "first portal" counts as relying on portal numbers. :P

Hey,
it seems that there is a little bug with the rangeframe for Kil'Jaeden. These ppl who are using the german client can't see a rangeframe for this encounter, the other ppl who are playing with the english client can see the frame. We are using BigWigs v. 78750.