Hotfix rebroke Assassin

[Nataichal]

Same issues as before the patch. Only works if a radiance goes off, or if someone else pulls aggro 1st.

[Qezuzu]

I'd get on to test this but I don't have a good Internet connection right now. Were you definitely able to Assassinate after 14.2 like a pro?

Some people, after 14.2, were still saying Assassinate was broken, but, well, we never came to an agreement. (http://forums.ddo.com/showthread.php?t=386631)

I'm not saying you're lying, but I implore people to wait for further comments from other people who tried to Assassinate things, lest we get another annoying thread.

[Badnade]

I was reading that other thread, and I dont see where you folks were getting the difering results..

Perhaps I passed over it, but it really seems liike half the folks were having no problem, while the other half were..

I would ask what changes there are between sample tests... Are these all rogue pure builds? do any monk bugs interact?

I saw that it was for specific weapons, and weilding two, and locations..

Guess Im wondering if it not an assassinate bug per say, but a set bonus bug, or something along those lines?

[Qezuzu]

I would ask what changes there are between sample tests... Are these all rogue pure builds? do any monk bugs interact?

Guess Im wondering if it not an assassinate bug per say, but a set bonus bug, or something along those lines?

We never got around to what exactly was preventing Assassinate for them, though I wouldn't exactly call their tests "thorough". Didn't report weapons used, didn't report builds, didn't do many trials, etc.

It was an extremely confusing thread and I don't think we ever found a bug that was actually reportable. Some people are able to Assassinate, some aren't. There has to be differences between the two groups. If there's a bug at all, there's no reason why it can't be found.

But at this point I think it's a wild goose chase and I'm being bulls***ed. I mean, the OP opened up with using a CR1 Kobold as his test, people were claiming that those who were able to get Assassinates were trying to cause drama; and one poster actually showed a combat log picture of him Assassinating something, while simultaneously saying that Assassinate was broken.

[Ertay]

We never got around to what exactly was preventing Assassinate for them, though I wouldn't exactly call their tests "thorough". Didn't report weapons used, didn't report builds, didn't do many trials, etc.

It was an extremely confusing thread and I don't think we ever found a bug that was actually reportable. Some people are able to Assassinate, some aren't. There has to be differences between the two groups. If there's a bug at all, there's no reason why it can't be found.

But at this point I think it's a wild goose chase and I'm being bulls***ed. I mean, the OP opened up with using a CR1 Kobold as his test, people were claiming that those who were able to get Assassinates were trying to cause drama; and one poster actually showed a combat log picture of him Assassinating something, while simultaneously saying that Assassinate was broken.

Conflicting reports point to it being caused by certain interfering effects, rather then being caused by a wrong order in general. Turbine themselves never, ever test fixes under working conditions, so likely culprits are:

-new weapon effects introduced during the last update
-improved sneak attack feat
-epic destinies that do anything on hit
-anything that modifies the w() modifier, like deadly weapons or even the improved base from >20 random drops

If I were to test it, I'd say if it doesn't work for you I'd say start with magister ed with points in it and a plain dagger from the harbor and work you way up from there to see what breaks it.

[Nataichal]

When the bug was initially reported, Turbine did respond to the concern, and reported a correct order of application of assassinate and damage was plugged in with the last patch.

All of my assassinate attempts are made on the same character using the same weapons: a pure drow rogue using Lit III and Radiance greensteels. Prior to the patch, when the issue was first reported, assassinate itself WOULD WORK..... if there was something else distracting the mob. Intimidate, aggroed on something else, blindness, etc. However, a solo rogue sneaking up on an unaggroed mob would not be able to assassinate, as the damage would hit before the assassin attempt, thus aggroing the mob on the rogue and removing the requirement of a sneak attack. No saving throw would be present.

Even then, assassinate attempts could succeed, if the assassin was dual wielding, or if a double strike went off, as long as the 1st weapon created a sneak attack criteria (a radiance critical hit causing blindness, for example). The 1st hit would create the sneak, the 2nd would get the assassinate.

What I'm saying is that the problem is back. No assassinate solo on unaggroed mobs without the addition of blindness or something, and no save.

When the patch hit, the issue was fixed, up to Wednesday night. Thursday's hotfix hit, and it changed back to being borked.

[Vormaerin]

I haven't seen any evidence of this bug returning. Just to be sure, I wandered around gianthold solo and was able to assassinate the ogres and giants just fine.

[akiraproject24]

Had a few occasions where the assassinate hot key was activated in stealth unnoticed and NOTHING would happen..kinda like the pale master form not going off. This happend to my rogue 3 or 4 times. Its definately new. But I only played my rogue to prep traps in epic elite since ...U14

[lamborgini]

When the bug was initially reported, Turbine did respond to the concern, and reported a correct order of application of assassinate and damage was plugged in with the last patch.

All of my assassinate attempts are made on the same character using the same weapons: a pure drow rogue using Lit III and Radiance greensteels. Prior to the patch, when the issue was first reported, assassinate itself WOULD WORK..... if there was something else distracting the mob. Intimidate, aggroed on something else, blindness, etc. However, a solo rogue sneaking up on an unaggroed mob would not be able to assassinate, as the damage would hit before the assassin attempt, thus aggroing the mob on the rogue and removing the requirement of a sneak attack. No saving throw would be present.

Even then, assassinate attempts could succeed, if the assassin was dual wielding, or if a double strike went off, as long as the 1st weapon created a sneak attack criteria (a radiance critical hit causing blindness, for example). The 1st hit would create the sneak, the 2nd would get the assassinate.

What I'm saying is that the problem is back. No assassinate solo on unaggroed mobs without the addition of blindness or something, and no save.

When the patch hit, the issue was fixed, up to Wednesday night. Thursday's hotfix hit, and it changed back to being borked.

AS a lvl24 halfling rogue assassin player using every weapon conceivable, the problem was never fixed. It just finally caught up with your game software!!!!

[LazarusPossum]

Ok, did a quick plain-jane test in Sschindilryn on two drow, to be sure on a static mob at or near level (with no attack spiders to muck things up). Also using only one weapon to be sure that too many hit dice were not mistaken for assassination.
Edit: Also going in solo, no hireling, to make sure I'm the only one pulling aggro.

Right hand: +5 Rapier/Left Hand: +6 Proof Against Poison +10 Light Spiritcraft Shield of Lesser Regeneration
Level 23 pure Rogue/Deadly Shadow capstone/level 5 Shadowdancer

Drow Commoner: (Combat): You attack Drow Commoner. You roll a 15 (+46): you hit!
(Combat): you hit Drow Commoner with Assassination.
(Combat): You sneak attack Drow Commoner for 124 points of pierce damage.
(Combat): You killed Drow Commoner.

Drow Guard: You attack Guard. You roll a 19 (+46): you critical hit!
(Combat): You roll to confirm a critical hit on Guard. You roll a 18 (+46): Critical Hit!
(Combat): you hit Guard with Assassination.
(Combat): You sneak attack Guard for 124 points of pierce damage.
(Combat): You killed Guard.

Effects weapon test coming soon...

Next test: +5 Holy Burst Rapier of Greater Elf Bane in right hand (doing these one at a time due to massive amounts of text each encounter when assassinate doesn't proc).

Drow Guard: You attack Guard. You roll a 5(+46): you hit!
(Combat): You hit guard for 4 points of good damage.
(Combat): You hit guard for 7 points of damage.
(Combat): You sneak attack Guard for 103 points of pierce damage.
(Effects): You receive a penalty from Harried.
(Effects): --- Penalty Penalty modifier to Movement Speed: -2%
(Combat): You attack Guard. You roll a 12(+47): you hit!
(Combat): You hit Guard for 10 points of good damage.
(Combat): You hit Guard for 12 points of damage.
(Combat): You hit Guard for 22 points of pierce damage.
(Combat): Guard misses you!
(Combat): You attack Guard. You roll a 4(+33): you grazing hit!
(Combat): You hit Guard for 7 points of pierce damage.
(Combat): You attack Guard. You roll a 6(+33): you grazing hit!
(Combat): You hit Guard for 8 points of pierce damage.
...a lot of back and forth here, in the order of good damage, damage, and pierce damage...until he is killed.

Need to break for a bit, next test coming soon...

Okay, did a few more like the one previous. Same thing with Drow Commoner and a couple of Guards. However...

Blademaster: (Combat): You attack Blademaster. You roll a 16(+46): you hit!
(Combat): You hit Blademaster for 10 points of good damage.
(Combat): You hit Blademaster for 12 points of damage.
(Combat): you hit Blademaster with Assassination.
(Combat): You sneak attack Blademaster for 114 points of pierce damage.
(Combat): You killed Blademaster.

Soooo...that blows the "effects breaking sneak" theory out of the water, at least for Blademasters (not sure if Orange Name makes any difference).

[Dragavon]

Same issues as before the patch. Only works if a radiance goes off, or if someone else pulls aggro 1st.

Why am I not surprised when we see old bugs get reintroduced to the game.

Turbine are experts at this :D

[Qezuzu]

So I found my dorm room's Ethernet jack and the wired Internet 100x faster than the Wifi (I tested this. It is literally 100x faster). So I can play DDO, yippee.

ONCE AGAIN, my Assassinate is functioning perfectly. ಠ_ಠ

This first pic (http://i49.tinypic.com/nwixzc.jpg) is an instant before I actually hit the target. And this one (http://i45.tinypic.com/2lj14ki.jpg) shows that my Assassinate works. This was actually a double Assassinate (I didn't actually notice that second, stealthed mob there). No, it's not possible to Assassinate two mobs with one Assassinate if both are "alert". It only worked here because that stealthed mob was in an "unready" state (he was crouching).

Pure lvl25 Assassin rogue, maxed Shadowdancer destiny using dual eGaros Malices. Improved Sneak Attack taken. On Orien.

When I previously tested this, before u15, I tried all my weapons and I was never able to get Assassinate to not work. I'm just not going to help test this AGAIN just because one poster says his Assassinate is suddenly broken.

So if you are having trouble with Assassinating an inactive mob, and are sure that your Assassinate DC, stealth skills, and experience with the Assassinate ability are enough that you can reliably Assassinate an at level mob, post your weapons used, character level, Epic Destiny (if you have one), server (I've heard a rumor that some bugs are specific to some servers), and whatever else you think could be helpful to find what's going on.

And if we find a pattern we can bug report it. Dammit.

[Seph1roth5]

Yeah I've been having no problem assassinating multiple targets or getting 2 shots off since the hotfix.

[MaximusParthas]

logging in to check. my dc is a 47. that should be enough for a valid test.
I'll be using dual emidnights, echarged gauntlets and red fens venom set.

I know the first bug hit me. I was unable to assassinate anything on a solo run without a prep like bluff.

[Thlargir]

Apologies in advance if this has been covered (I have been unable to follow all the bug threads).

I find when soloing (with no pets, hires, summons, traps etc) I never get sneak damage on a first strike on a non-alert enemy. It is as if when I attack the mob aggro is determined before my attack is resolved.

[MaximusParthas]

ran a tod. didn't have any visible issues. but no moments of unaggro'd monsters.
will try solo tomorrow.

[Arakasia]

ok so took my 13th lvl pure halfling female on Cannith out to the sands for some testing...

dc on assassinate is 31 with dual rapiers, and had nps at all.

i have pics but cant seem to upload them..

copies of combat log
(Combat): You attack Windlasher Gnoll. You roll a 17 (+30): you hit!
(Combat): You roll to confirm a critical on Windlasher Gnoll. You roll a 1 (+30): Failure!
(Combat): You hit Windlasher Gnoll for 2 points of cold damage.
(Combat): you hit Windlasher Gnoll with Assassination.
(Combat): You sneak attack Windlasher Gnoll for 65 points of pierce damage.
(Combat): You killed Windlasher Gnoll.

(Combat): You attack Windlasher Gnoll. You roll a 12 (+30): you hit!
(Combat): You hit Windlasher Gnoll for 1 point of cold damage.
(Combat): you hit Windlasher Gnoll with Assassination.
(Combat): You sneak attack Windlasher Gnoll for 65 points of pierce damage.
(Combat): You killed Windlasher Gnoll.

mainhand weapon is a +4 keen rapier of backstabbing +1 with festival icy burst on it and
offhand weapon is a +3 holy cold iron rapier of deception with festival icy burst on it as well