Game Mechanics: Archery (all ranged attacks?) non-functional near max range

[Haynar]

Dont worry. With what Zaela dug up, will code a fix later. Will add another 5 server side too, to make up for any sync differences.

H

[khanable]

This is very exciting

[Jimjam]

Originally Posted by Zaela [You must be logged in to view images. Log in or Register.]

The fact that you mentioned big mobs with large hitboxes made me think that the range calc is supposed to be "edge to edge" rather than "center to center". Fired up my test server and tried it out: yep, the ranged attack button will grey out at much further distances against bigger targets. Can grey it out at ~190 distance with a 100 range bow and 25 range arrow against a size 50 target (dragons are size 25).

I'm surprised if that wasn't figured out a long time ago. There's a comment in the EQEmu code that kind of hints at it...

float range = RangeItem->Range + AmmoItem->Range + 5; //Fudge it a little, client will let you hit something at 0 0 0 when you are at 205 0 0

5 extra range would probably be enough to account for it against small targets.

Can't necessarily be sure that this is actually classic and not something that was introduced in later clients... but it's a pretty fundamental thing so it probably wouldn't have changed since the early days. And it makes sense; avoids the situation where a short range throwing weapon can only hit a huge dragon from within melee range and such.

I remember in classic being able to stand in the melee range of a giant or treant but still being able to shoot my bow, which suggest for the minimum range of range attacks it is measured from the centre of the mob.

[Ciroco]

bump

[Ciroco]

Did this ever get implemented? Still seemed to be having this issue on elephants the other day.

Also:
[You must be logged in to view images. Log in or Register.]
I'm no math whiz, but that doesn't seem right.

[Brocode]

usually when i shoot at max range(250), button greys out but no javelin is thrown and have to wait the delay to throw again, and thats why i avoid run and throw at the same time as this might happen and instead of instant tag, i get a 2 segs delay.

[evilkorn]

It's still slightly buggy if you are at max range. It's not like there's a ring around the range distance to test it in game if you are on the edge or not. It is also pretty inconsistent and might have to do with throwing then backing up over the range too quickly or like you said running up and throwing I find to be an issue as well where I usually have to wait on the cooldown to throw again.

[Nirgon]

Read entire thread

Goog

[Haynar]

Due to time delays between server and client, there is no way to make this work 100% while either is moving.

Stationary, its working pretty good.

H

[Nirgon]

archery, bolts and throwing were always a little wonky

no denying that