Problem: Often my character fails to hit the target.

[Ombra]

Greetings everyone.

Problem: Often my character fails to hit the target.

I explain.
- Patch 1.11B.
- LoD.
- D2Loader (11 Nov 2005)
- DirectDraw.
- Sting's MapHack 2.24.
- No mods.
- Single player.
- Nightmare Diff.
- Act 1.
- Assassin character (a Martial Arts build).

I first noticed this problem in Normal Diff, but I thought it was
mainly because of my poor Attack Rating.
With more Claw Mastery points I have increased the AR, and
things have apparently become easier.
Yet there still was the occasional long series of "miss" (from 4 to
6 consecutive) when swinging my claws to hit the enemy.

I may be a rookie, but I think that now that I'm in Nightmare and
have built an AR well above 2200 I should at least be granted
nearly 100% chances to hit a stupid Fallen in Act 1.
Especially now that I can make extended use of Phoenix Strike
and its 3rd charge to freeze packs.

I noticed that when the Chaos Ice Bolt freezes something I am
often unable to hit the passive monster. Why??
(this also happens with slow moving targets, such as zombies)

I have made a few quick tests.
If after I freeze someone with Chaos Ice Bolt I click to attack him
my Assassin won't hit him at all until the freeze goes away and
the monster returns to move (he gets the first hit, the moment
he thaws and can move).
Even by looking at the animation there is something wrong.
The tip of the claws are always too far away from the monster.
No wonder I can't hit him, but why my Assassin keeps such a distance?
Things are different if I manage to maneuver to get closer to the
frozen dude before he thaws. When I do, it's always 100% hits.

Besides being rather annoying to be forced to maneuver instead
of focusing directly on the attack, this problem nullifies the tactical
advantage of freezing a pack of monsters. Because by the time I
move (trying to click without triggering an attack) and actually kill
the 1st target, the other frozen monsters will thaw.

Anyone else has experienced this?
I've searched for an explanation, but this seems a problem nobody has posted about anywhere, so far.

The problem seems to be that my character doesn't get close
enough before attacking. What can I do?



Thanks In Advance.
Ciao ciao : )

[Bloodangel26]

i've had similar problems with my smiter before...smite is supposed to always hit or whatever, but i've also experienced times where i just could not seem to hit things...check your char screen and see what your % chance to hit is. if its pretty high and you are still having this problem, it might be some kind of bug

[Arc]

go right beside him before u attack then if he doesnt get close enough b4 he attacks

[A.D.]

I'd wager lag.

[slimp]

you'd wager lag in single player? I'd wager stupidity on your part "AlmostDeadly".
I think it's probrably because you're not close enough to the thing, don't click directly on the monster, click near it, then when you're near it SMACK IT. it's just a bug that makes it so your char doesn't get close enough to the specified monster and I'm guessing it's not possible to fix it, and if it is.... it's in the scripts or something, i'm guessing.

you can't get the kind of lag that ****s up your AR unless you're using the internet, because it's not the FPS that lags for that stuff to happen, it's the ping.

sorry I don't mean to be an asshole... but I worked all day, and I'm not in my own environment, i'm in the farm, and i'm pissed off cause i don't want to be here anymore, a week was enough

[Ombra]

@ AlmostDeadly:
Pardon? Lag? In Single Player?
You teasing me, eh? : ))

@ slimp:
Surely is like you say. I need to get closer than what my char
automatically does. But it's so annoying...
Since you mentioned scripts, I tell you what I just tried.
In the "Weapons.txt" there's a field named "RangeAdder".
This field states the extra range (in yards?) that can be added
to weapons. Specifically, all the Assassin's weapons have this field
set to 1 (one). If I increase it (I tried 5) the bug isn't corrected.
The only effect is that I see my Assassin swatting flies with her
Claws at even a greater distance than before. Yet, she won't land a
hit, just like before.
My second attempt has been to try a negative value, like -1 (hoping it
would reduce the range and maybe solve the problem).
But seems like the RangeAdder field accept only unsigned integers.
Meaning that a value of -1 gets reverted either into positive 255 or 65535
(probably the former), therefore drastically increasing the range of claw
class weapons.
Now, that was funny to see : ) I could hit anyone, anywhere, providing
I could click on him with the mouse. I tried regular monsters,
champions and uniques. Always 100% hit/land ratio for all the time I
played. Even with bare hands. Not a single miss.
Setting RangeAdder to 0 was the last try, and didn't solve the problem.
Well, at least we know it's not a poor AR or Hit % related bug.
Can a better modder than me shed light on how to fix this?



Anyway...
The more I read (and see with my own eyes) about P1.11b the
more I get disappointed by Blizz programmers.
What happened to the old saying "if it ain't broken, don't fix it?"

They have corrected the "150% damage to Undead" string-bug only to
introduce a similar one affecting that affix that adds to AC
based on the character's level. I don't remember the name, but it
adds much less that what it states in the tooltip.

Locked Chests can be opened without keys at all. I'd swear I did
need keys in the beginning, but things have changed when I moved keys
inside the H.Cube. IIRC that's when it started that I could open
Locked Chests without keys.

Character's (at least the Assassin) strangely fail to hit their target
even though they have 69% chance to hit a specific enemy (like
a Fallen, in Nightmare Diff), and an attack rating of 2566.

The Phoenix Strike 1st Charge no longer plays the Meteor impact
sound when the meteor strikes and explodes in a burst of flames.
That sudden 'mute' is so frustrating... you expect a BOOM, but get
only silence.

Again for the Assassin, not only she often fails to hit a target (as I
described), but she also VERY often fails to release the charges
when she finally manages to hit (I forgot to mention it earlier).
I can't properly hit. I can't properly release charges.
What good is a Martial Arts Assassin for??? Blasted Blizzard...

And then there are the various monsters changes made past
patch 1.09D. The patch texts state that monsters have been
beefed up etc etc...
In patch 1.09D my Assassin would often die in Normal Difficulty
(even if using a MapHack in order to avoid major threats).
In patch 1.11B, instead, my Assassin had to reach Nightmare
Difficulty to die for the first time.
I noticed things were much easier than what I was used to (1.09D),
and so I disabled the Maphack roughly around half of Act 3.
I thought it would add a challenge to a boring experience. Yet I
managed to reach and kill Baal without problems.
I haven't played D2 in a couple years. That should tell you something.

But I'm not saying that I'm a great player. Rather, the new patches
(or just the 1.11B) have turned Normal Diff. into a boring walk in
the park.

Though heavily bugged in 1.09D, at the very least the Assassin
could fight her way up to Hell Diff.
Now in 1.11B I have problems to advance through Nightmare Act One!
And not because monsters will kill me (I died only once), but
because my Assassin cannot fight the way she's meant to.
I died because I kept killing targets without releasing the 3 Cobra
Strike charges that would have saved me.

Great, I'm ranting like a gramp...
Does anyone know if it's possible to solve these problems?

More importantly, were the problems in patch 1.10 as well?
Please understand, I never played 1.10. I'd need to dig for a number
of old downloads and build a new char to discover it myself, so...
can a kind soul answer me?

Regards,
Ciao ciao : )

[Nubli]

It could still be lag, as in game lag. Ironically when I upgraded my computer the game ran worse overall in Single/Multiplayer. It happens in many games, you think you're right next to your target, when in fact it's just a model bug and possibly somewhere else.

Common fix: move a step away and then back.

[slimp]

yeah nubil that works, but I think he's looking for a way that he doesn't have to do that, and i don't think that's possible.

was your lag model lag or fps lag? never heard of that model lag thing, unless the game was modded.

[Bloodangel26]

ombra, every character BUT assassins need keys to open locked chests...its explained in those books that come with the game...

[Ombra]

@ Bloodangel26:
No way! Are you serious?
oh my god, you are. I've overlooked it all this time...?

Haha. So it's not a glitch. Ignorant me.
But I clearly remember me needing keys to open the Locked
Chests, using the Assassin. How weird...
Oh well, it's not the end of the world.

Thank you,
Ciao ciao : )


Oh, btw. This may be of interest.
Speaking of glitches, to fix the missing meteor impact
sound that should be played when using Phoenix Strike 1st charge:

1) open the file "Missiles.txt"
2) locate the line starting with "royalstrikemeteorcenter" (or scroll down to the line with ID 564).
3) Go to the "HitSound" field of this line (in excel it would be the "EV" column). The field is actually blank.
4) Type-in exactly: "sorceress_meteor_impact" (without quotes) to re-enable the meteor impact sound ^_^

When your Assassin will call the meteor, you will hear the explosion sound as it impacts with the ground, and as it should have been since the beginning of this unlucky patch (blasted Blizzard...)

I have tested it. Works without causing problems, even if calling meteors like crazy.

I still want to fix the incorrect engage range or whatever it is that makes my Assassin swat flies instead of landing hits. Any idea?



Best regards,
Ciao ciao : )