![]() |
|
#231
|
||||
|
Quote:
The reason this was ruled a non-kite was: 1. You did not have a sufficient force in zone to claim that you were ready to engage and we did; 2. It was still, regardless of path, within a perfectly reasonable time frame. In the Talendor instance here: 1. You did not have a sufficient force in zone engage and we did; 2. It was outside of a reasonable timeframe. | |||
|
|
||||
|
#233
|
||||
|
Quote:
| |||
|
|
||||
|
#234
|
||||
|
Quote:
| |||
|
|
||||
|
#235
|
||||
|
Quote:
Talendor 1. Incorrect 2. Incorrect [You must be logged in to view images. Log in or Register.] Your own boy hitpoint agrees tal is slow and takes more than 4 mins to get to camp. Messaging fail. Try again! | |||
|
|
||||
|
#236
|
|||
|
Quit crying and quit afk tracking. Why must TMO raid interfere on our pulls, is this a final desperation attempt....
| ||
|
|
|||
|
#238
|
||||
|
Quote:
| |||
|
|
||||
|
#239
|
||||
|
Quote:
| |||
|
|
||||
|
#240
|
||||
|
Quote:
Maybe TMO want to pull it to the center of the zone then was going to pull it to OT? but that doesn't make sense as it would just be delaying the time to engage. They only had 2-3 mobs + Talendor, so there was no need to make some crazy split. In this case there are only three options. 1) I am just lying about everything 2) They tried to delay the engage (Kite) 3) They got lost or moved camps, which I attest would still be a Kite by way of ignorance. I have no idea what happened before with all the FTE/LDSK crap. The amount of time on the pull matters, but I wouldn't care if you were making your way to the camp with the dragon. I absolutely won't be sitting there with a stop watch counting seconds, but you can tell from the pull path that it is a clear delay. All I saw was a puller going in one direction then making a U-turn and start pulling in a bizarre direction. A change in direction such as this has no purpose and provides clear proof of a delay to engage, either intentional or by accident. Ruling this type of pull as acceptable sets, yet again, a bad precedent that will lead to more confusion and tomfoolery. | |||
|
|
||||
![]() |
|
|