The thread wasn't about warrior aggro mechanics, it was about a threat modifier at the beginning of an ignite stack continuing on when the players(mage's) threat modifier changes.... referring directly to the 100% threat reduction given by the spore buff on Loatheb. Ofcourse ignite ticks always generate threat, but if the threat is reduced by 100% it doesn't really matter what the tank is doing as long as he has auto-attack on now does it. I don't really see what your post has to do with the topic.

His posts NEVER have anything to do with the topic, im shocked more havent noticed heh.

Having done loatheb last night, I can say with a reasonable degree of confidence that ignites threat DOES change dynamically when people pick up the spore debuff (ie even if you have a ignite running before you get it when you pick up the debuff your threat goes to 0 from any subsequent ticks) as we had mages miss the debuff and pick up a slightly later one while owning the ignite stack still and they wouldve pulled agro straight off the tank if it didnt. Unfortunatly i have no dps/ktm to show you this in action tho, was too excited by the huge difference the darkmoon faire buff is, saved me a shadow pot :P

sorry guys :(

threat is calculated at the time the damage lands.

cause your damage is multiplied with your threat modifier at that specific time.
as Tel just said: if you have the spore buff there is little to no threat generated.

Let me explain a situation to you:

Loatheb - 5 Fire Mages in Group 1, 1 Fire Mage (new recruit) somewhere in Spore Group 4.

New Recruit crits early, before getting the Spore buff, Group 1 Mages continue the Ignite on with the Spore Buff, New Recruit continues receiving Ignite ticks.

New Recruit receives Spore Buff (and continues to receive Ignite ticks).

New Recruit pulls aggro and dies 20 seconds after getting the Spore Buff.


This happened last week. What happened here?

This would support my thinking on the situation, that the threat modifier attached to ignite is set in stone from the mage's threat reduction when he BEGINS the ignite tick. Your scenario would also coincide with my scenario which was about the opposite, I begain the ignite tick with the spore buff and then missed next spore buff while ignite tick kept going for 1.5 min and I did not pull aggro, even though I was about 200k damage above rest of raid group.

Don't underestimate the threat a tank can generate on this fight.

While doing training without any offensive buffs, I missed the first spore but managed to get a crit before the other fire mages (they were in first group to get spore so that's like 15 sec into the fight), with the result that the ignite was ticking for 3000-3500 (we were unbuffed afterall) with me getting threat for all of it since I owned it. If I recall correctly, I pulled aggro at around 160k damage done, with a displayed DPS of slightly beyond 2k. I may be remembering this wrong but I'm sure it was an impressive amount of time I could keep up that ignite before drawing aggro with only a minor head start for the tank. If we had had our best tank on the job (Thunderfury etc.), he had been using offensive buffs too (for what it's worth) and he had gotten a 90 second headstart before the ignite, I don't see an aggro pull happening within the next 90 seconds (or twice that), even with 5k ignite ticks, assuming you're Alliance.
I'm using 52% threat reduction.