[Croco]

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

Your position before is that you did not kite towards KT. Then your point was that it was not kited at all. Now your point is that it was not kited on purpose.

Intent is irrelevant in this situation. You either pulled it to back to the throne room or you didn't. Video shows you did. Since you did, you need to concede. There's no other argument here. Nothing else to discuss. Riot took it back to the throne room. All of the evidence shows this.

Q10: What about a raid mob being indefinitely kited, stalled, or occupied?
A: It is against server policy to indefinitely kite, stall, or otherwise keep occupied a raid mob without intention of killing it. You either bring it to your raid, die, or zone out. Obvious stalling of a raid mob, especially in situations to prevent engagement by another guild/party, is against the rules. Ignorance is not an excuse to break this rule. If you are pulling raid targets, we expect you to know what you’re doing.

Q12: What exactly does the Staff consider a stall?
A: As far as engage stalls, the Staff will grant you one DA, or about that much time on an engage before considering it a stall. So it’s important that guilds do not engage a mob until they are ready to kill it. The spirit of the rule (and what we are looking to do here) is to prevent guilds from locking up a target before they are ready to kill it, just to prevent other guilds that are ready to kill it first/faster. If you stall, you need to drop aggro immediately and concede/forfeit the mob. Any number of players can be considered to be stalling a mob, what we look for is the engage of the kill force. I know some of you want an exact number of seconds, or players, or DPS done. But the fact is that’s just not realistic with guilds being so vastly different in numbers and strength, while also competing for the same content. The most important thing here is the statement about the spirit of this rule stated above.

I'm going to dumb it down for you since you are having a really tough time understanding. Per the raid rules, not just whatever vanq wishes to make up and word vomit everywhere, Staff affords each attempt at a mob "one DA, or about that much time" before considering it a stall/kite. By the server rules, which again vanq has repeatedly said they adhere to religiously, no rule was broken and it was not a kite/stall. KT was moving away from camp for "one DA, or about that time".

You can keep saying over and over and over that it was a kite but that doesn't make it true. No rule was broken and if you think one was I would love for you to quote me the exact rule you believe we violated, and we can examine that.

As it stands currently you keep saying the same incorrect debunked trash over and over in a desperate attempt to will it to be true. No rules were broken. It does not fit the definition of a kite per server rules.