0420: 2nd range check on critshot says 'out of range'

Reported by ☆ q5i at Wed, 11 May 2016 13:46:30 UTC
gamemechanic bug
new
1 confirmations

Description

When playing a bow wielding class and starting a critshot , the 1st range check will say that the targeted mob is in range, while the 2nd range check, that takes place when the arrow is about to be released, will often state that the mob is out of range though neither player nor mob have moved in the meantime. This might apply to all bow shots in general, but I'm not sure.

Reproduction Steps

1. Approach a mob at max bow range distance
2. Start a critshot.
3. Read both range check messages

Intended Behavior

The calculation of the 2nd range check of a critshot (bowshot in general?) should not be different than the 1st one. If the 1st check says the mob is in range, so should the 2nd one if neither player nor mob have moved.

Evidence

I'm sorry, I can't provide any evidence sources, but this seems like a no brainer to me. I would not have reported it otherwise.

Status

issue is new, and needs confirmation
requires 2 more confirmations
votes (priority): 2
1 player says this report is valid, 2 disagree

Comments

Note: You need to be logged in to post comments.
Loading Comments...