![]() |
|
#11
|
|||
|
28 seconds between FTE and first non-FD aggro by FE. Long time, but I guess what's good for the goose is good for the gander.
How did TMO miss a 5 second aggro head start by Option? Are they blind?
__________________
| ||
|
|
|||
|
#12
|
|||
|
Still wondering when this enormous code undertaking will be completed to get mobs to announce their engage. Whenever hate list is empty, and a new target is acquired with more than 0 hate (or w/e default value is for a body pull), announce it.
| ||
|
|
|||
|
#13
|
||||
|
Quote:
| |||
|
|
||||
|
#14
|
||||
|
Quote:
| |||
|
|
||||
|
#15
|
||||
|
Quote:
| |||
|
|
||||
|
#16
|
||||
|
Quote:
__________________
| |||
|
|
||||
|
#17
|
|||
|
Option disengage time of 21:52:36 yet able to engage again at 21:52:29? Hmmmm.... Logs clearly doctored.
| ||
|
|
|||
|
#19
|
|||
|
option had FTE on the mob, if you don't know that you clearly weren't there.
| ||
|
|
|||
|
#20
|
|||
|
Solution? Do what I do.
Post in the bugs section about being invuln and still getting Trak touched. Find a lil evidence because you gotta prove to the pixel hungry masses (and sometimes Nilbog too) that this was the case. | ||
|
|
|||
![]() |
|
|