Infraction for itson: Horrible Post

• Aldriana · 09/15/08, 1:50 PM

Post: [Hunter]Help me please
User: itson
Infraction: Horrible Post
Points: 2

Administrative Note:

Message to User:

Okay, this post fails on so many levels. I suggest you take some time to read our forum rules before you continue posting, or your stay here will be very short.

So lets go down the list of your violations, shall we?

Rules 1 and 2: Sentences start with capital letters, and "adv" and "anywayz" aren't words. Please spend more time on your grammar and punctuation.
Rule 4: You specifically said that you knew the answer was out there and couldn't be bothered to search. In the future, bother to search. It may take a little more of your time, but it keeps the thread from getting shitted up with the same questions over and over.
Rule 5: You quoted a monstrous block of text in order to ask a short question about it. There's no reason you needed to quote all that. This is what we call "overquoting". Don't do it.
Rule 8: We don't care that it's your first time posting, if you're going to assert that people "fail at their class" you might want to have some analysis to back it up.

In short: you need to do much better in the future if you wish to keep posting on these forums.

Original Post:

There are many reasons why you might see some end game hunters with lower hit rating then 142.
1. He is eating Hit food.
2. There is a boonkin that raids everyday that gives him 3% to hit via imp FF.
3. There is a drani in the group giving him 1% to hit.
4. he fails @ his class.

Usually, you dont want to resort to eating Hit Food because your better off eating Agi food. boonkin who raids everyday is very hard to find and even if there is a boonkin who raids if he dies, there goes your DPS. and having Drani in ur party is really cool b/c not only you get 1% to hit your pet gets 1% to hit.

anywayz... on to my question.
( my 1st time posting )

so this is 2nd week where I pulled agro on Bloodboil.. yes Im not the only one who has done this before. Omen saying FD was success and being at bottom of the omen watching Bloodboil coming towards me and me assuming the position. I am really scared of DPSing on Bloodboil and on Illidan Flames. please give me some advice on what to do.

This is what i pulled up and AS FAR as i know this is all bull sht. Can someone conform this? What do you guys do on illidan flames and on Bloodboil? ( on Twins i sorta have more of resist threat and Omen keeping up with the Resist and i tend to tab to the caster and keep my DPS up, so Twins isnt a big deal 4 me )

ok, this is the info i found.

Did some testing on this last night as follows. Apologies for overly simplistic testing - I wanted to take as many variables out as possible.

Using the 2 x 70 mobs at the start of SV, Pet was not summoned for any tests, so a successful FD would be obvious as both mobs would immediately return. A partial FD is also obvious, as one mob returns until the other mob receives / performs a combat action, in which case the linking takes effect and the second mob returns. A failed FD is also obvious as both mobs continue without pause.

Note - Feign Death is not displayed at all in the combat log. It is also not logged when /combatlog is used. For this reason I cannot provide combat log excerpts to assist.

Round 1 - No Mods / No Macros

1) Cast Arcane shot
2) Stop attacking and wait
3) Cast Feign Death and immediately jump or strafe.

Results: FD reliably fails in this scenario. The ability is used, and the cooldown commences. There is no resist message and the mobs don't pause.

Round 2 - No Mods / No Macros

1) Cast 2 x steady shot
2) Just as last SS finishes, cast FD
3) Wait

Results: FD reliably works in this scenario.

Round 3 - No Mods / No Macros

1) Cast 2 x steady shot
2) Just as last SS finishes, cast FD
3) Start spamming SS immediately

Results: FD reliably fails in this scenario with a similar result to Round 1. No resist message, Uses cooldown.

No Mod Summary
It is surprisingly easy to reproduce a scenario where Feign Death fails, yet no "Resisted" message is displayed. It is impossible to determine whether this is due to "failed animation" or some other reason, like an overwritten outbound message client-server.

Round 4 - Omen only

1) Cast Arcane shot
2) Stop attacking and wait
3) Cast Feign Death and immediately jump or strafe.

Results: FD reliably fails in this scenario. Now with Omen on, I can see that my threat on the primary mob is being removed (according to omen), yet there is no pause in either mob, and still no "Resisted" message.

Round 5 - Omen only

1) Cast 2 x steady shot
2) Just as last SS finishes, cast FD / Also tried waiting before FD cast - no difference
3) Wait

Results: FD reliably works in this scenario. Omen removes threat unless there is a genuine "Resisted", in which case threat stays and FD fails as expected.

Round 6 - Omen only

1) Cast 2 x steady shot
2) Cast Feign Death at any point in time before mobs reach 5 yard min range
3) Instantly spam any shot

Results: I could reproduce the bug with any pre-FD timing, and any ability which required the shooting animation, including autoshot. Omen will still drop threat bar, when mobs had not dropped threat.

Round 7 - Omen only

1) Cast Aimed shot or Spam 3:2 macro
2) Spam FD while in the middle of another action
3) Wait

Results: FD reliably worked in this scenario, so actions prior to the casting of FD seem to have no effect?

Discussion on Omen and FD

At this point it is important to note how Omen works with Feign Death. Because there is no combat log message - Omen essentially starts off by assuming FD worked, and then invalidates that if the "ERR_FEIGN_DEATH_RESISTED" event is detected by the UI Error Message hook.

The reason it works this way is for safety sake. Because the client cannot tell which mob resisted the FD - it assumes that none of them did.

It is important to note for these tests that using Omen / Threat 2.0 amounted to nothing more than a fancy way of displaying when FD was resisted and whether the UI Error Message was displayed.

As far as I can tell the UI Error Message is the only way the client has of knowing if FD failed or not.

Suggestions

Three things would be good as outcomes out of this:

1) Other hunters to do some more / different testing (especially on the PTR) and see what effects you can reproduce.

2) Blizz to (if nothing else) reproduce the above bug internally and turn FD into a proper instant-cast spell (would be super nice if this worked off physical hit not spell hit as well)

3) Blizz to add Mob-specific FD messages to the combat log, for both completeness of information and robustness of addons.

I was able to reproduce a similar experiment. I was also able to accurately predict when my Feign Death would work, and when it would fail yet Omen would still drop threat with no combat log message of a resist.

The issue is starting a new ability or moving while attempting to FD. Allowing time for the FD to resolve (up to 1.1 seconds some times) before starting another shot rotation, or moving, is the way to get it to work properly. Casting FD, and then immediately going back go a shot rotation, or moving, will cause FD to go on cooldown, drop threat on omen, keep you casting, and keep your threat on the mobs you have aggro on.

The suggestions I can think up for helping with this problem are:

1. /stopcasting
/cast Feign Death
This macro can actually help reduce the chances of breaking your own FD by forcing you to stop casting while feigning; thus reducing the chance you will break it through a lagged auto/steady shot.

2. Ask for salvation instead of another buff.
While asking for salvation may seem like a decrease in your DPS, I say the following to anyone, "Dead players do zero DPS. Zero DPS is less than whatever you would do with salvation while alive."

3. Wait for your Feign Death to go off before starting anything. This could mean having to wait upwards of 1.0 seconds before starting a shot rotation again. Instances where I was able to see this happening include using Feign Death, and watching the mobs stop running toward me, but still target me and stand in place for 1.0-1.1 seconds after feigning, and then running back to their original places. Feign Death is not on a global CD but is effected by lag like everything else. Give it time to resolve before getting up and shooting again.

so does this macro work?
/stopcasting
/cast Feign Death

and should i kill my DPS experimenting with staying down when i cast MD for UP TO 1.x sec like this post said?

I know, I am 100% sure this has come up before, I am sure that someone has posted about this before, TRUST ME i know. Please dont post "try searching this has already been answered" Searching for this will take me years. and the search took me to that post. I want to get some input on what you guys do against those fights, and how do you guys deal with FD. Thanks in adv.