PDA

View Full Version : Agility bug?


FBG_Winston_Wolfe
05-22-2007, 02:46 PM
Since I have no chance against the front page, I have been battling some noobs in order to test out different configurations.

I battled the noob spinacz 3 times with the following configuration with my largesword skill at 100, Agility 34, Dex 10

In those 3 battles, I missed 20 times( 7,5,8) , spinacz missed 11 times with weapons (not spells)

I then battled the same person twice with the same weapons, Agility 10, Dex 10.

In those 2 battles, I missed 3 times (0,3) , spinacz missed 6 times with weapons (not spells)

To the untrained eye, agility seems to have a negative effect on my character.

FBG_Winston_Wolfe
05-22-2007, 03:25 PM
Since I have no chance against the front page, I have been battling some noobs in order to test out different configurations.

I battled the noob spinacz 3 times with the following configuration with my largesword skill at 100, Agility 34, Dex 10

In those 3 battles, I missed 20 times( 7,5,8) , spinacz missed 11 times with weapons (not spells)

I then battled the same person twice with the same weapons, Agility 10, Dex 10.

In those 2 battles, I missed 3 times (0,3) , spinacz missed 6 times with weapons (not spells)

To the untrained eye, agility seems to have a negative effect on my character.

I just attacked two more times.

34 agility = I had 10 misses
10 agility = I had 4 misses.

Something seems amiss (pardon the pun)

I seem to miss more when I equip more agility.

Crepitus
05-22-2007, 08:34 PM
Could explain why 1/2 of the front page mugged me overnight! :eek:

I have 40 Agi/ 45 Dex

FBG_Winston_Wolfe
05-23-2007, 01:43 PM
:tap:
:nip:
:bump:

FBGOnetime
05-23-2007, 02:54 PM
::goodposting::

I have seen the same effect, there must be a bug somewhere.

FBGsartre
05-23-2007, 09:28 PM
I also noticed something strange around the time you posted this. After a closer examination tonight though, I think the trends are going in the right direction. Perhaps the problem was fixed?

FBGsartre
05-28-2007, 10:20 PM
This bug came back for an hour or two earlier this evening, but seems to be fixed again.