Blood Guard trains themselves, blames innocent bystander! :D

[Heebs13]

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

Imrahn dumped KT and both of the level 65 red con rampaging flurry guards directly on the archway plowing AM to smithereens. THAT'S why you conceded, not because "we leapfrogged you and trained ourselves" - then you continued to train KT around and have 4 people spam hail lock it despite being warned repeatedly by every guild on the server AND GM staff that hail locking mobs isn't allowed.

Sorry you had to concede King Tormax, but frankly you trained us -- and yourselves -- to tee total smithereens with bad monks who don't know how to pull KT or kite his guards.

For reference as to why this is your fault:


Dumping mobs in a place that can train the shit out of an established raid force on purpose constitutes a raid violation. Imrahn waited until the mobs got to the end of the bridge before flopping where it was directly in range of our raid force, and started triggering FTEs immediately after he FD'd.. Sorry not sorry.

You're still having trouble with this aren't you? Did you miss the part where your monk got FTE before it aggroed the rest of your raid, or do you not understand how that indicates that you're wrong? Did you miss my post with the logs? Did you miss the log that showed the train that killed us came from a DAP member?

[Phatez]

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

You're still having trouble with this aren't you? Did you miss the part where your monk got FTE before it aggroed the rest of your raid, or do you not understand how that indicates that you're wrong? Did you miss my post with the logs? Did you miss the log that showed the train that killed us came from a DAP member?

Your logs don’t show where that monk was, which was next to our clerics.

[Teako]

You do realize that feigning something on to our raid force, with Shaolen sitting in camp, is not training some random player in the back corner of king xorbb's gorge, right?

Shaolen was sitting in our camp. You feigned it close enough to where all 5 mobs engaged our raid force immediately, and slaughtered us.. Then tried to cheat to re-engage it with hail locks.

I'm losing patience with trying to teach you that AG constantly violates raid rules yet continually acts like the P99 white knights.

[Maliant]

And why did people from your raid peek around and run into arch as soon as AG monk got engage message but not for the several minutes before when AM monks were splitting out KT and had FTE messages?

[Heebs13]

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

You do realize that feigning something on to our raid force, with Shaolen sitting in camp, is not training some random player in the back corner of king xorbb's gorge, right?

Shaolen was sitting in our camp. You feigned it close enough to where all 5 mobs engaged our raid force immediately, and slaughtered us.. Then tried to cheat to re-engage it with hail locks.

I'm losing patience with trying to teach you that AG constantly violates raid rules yet continually acts like the P99 white knights.

Your monks were sitting in camp with your clerics? What were you doing sitting at the ice bridge in front of our raid with your monks sitting in camp not pulling?

As an aside, because I honestly don't doubt you on the hail lock thing but I have never seen the ruling that says you can't hail lock a mob, can you link me to where that rule is listed?

[Phatez]

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

And why did people from your raid peek around and run into arch as soon as AG monk got engage message but not for the several minutes before when AM monks were splitting out KT and had FTE messages?

AM monks far superior to AG monks. They kept control of KT so that he did not train the two raid forces. When AG monk attempts to split he trains everyone. Send AG monks to split camp. It’s next to splitpaw. You can practice using beads to pull in other zones like befallen and solb if you do not feel confident enough to use them at raids without training guilds.

[Phatez]

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

Your monks were sitting in camp with your clerics? What were you doing sitting at the ice bridge in front of our raid with your monks sitting in camp not pulling?

As an aside, because I honestly don't doubt you on the hail lock thing but I have never seen the ruling that says you can't hail lock a mob, can you link me to where that rule is listed?

We had 15 monks on that raid. Takes two to split KT. The other monks were behaving themselves, not training the raid. Maybe your monks should learn from this.

[Teako]

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

Your monks were sitting in camp with your clerics? What were you doing sitting at the ice bridge in front of our raid with your monks sitting in camp not pulling?

As an aside, because I honestly don't doubt you on the hail lock thing but I have never seen the ruling that says you can't hail lock a mob, can you link me to where that rule is listed?

Hail locking is considered disruption, and exploiting the mob's ability to re-set naturally. It is a raid interference. It has -always- been against the p99 ruleset to hail lock raid mobs with factioned characters to prevent them from resetting.

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.

https://www.project1999.com/forums/s...d.php?t=189856

You were moved half way up the ramp. We had to position as to not train your raid force while pulling. Shaolen triggered zero FTE's on King Tormax at all - he was not part of our pull team for this mob. However, Imrahn triggered LOTS of FTE's prior to his final FTE that triggered AM's slaughtering.

Not to mention Zotspox has 17 engages, Mistersmilez has 11 engages, and by my log/fraps I have about 8 different Azure Guard members spam hailing King Tormax as he was trying to reset naturally.

Sorry bucko, AG was in the wrong here. First, trained us. Second, stalled King Tormax with kiting for well, WELL over 18 seconds (roughly 2mins) Third, repeatedly re-engaged King Tormax with the same players in attempt to continually train all of Aftermath so we couldn't compete, and last but not least - Fourth hail locking KT so he couldn't reset.

AG was 100% in the right to concede this mob and get out of Kael immediately. This is four 20 day suspendable occurrences in once single raid. Ignorance of the raid rules is not excuse of the raid rules.

[Heebs13]

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

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.

Does hail locking prevent engagement by another guild/party? Maybe that's why they think it wouldn't be against the rules. Hail locking a mob makes it just as easy for your guild to pull it as ours.

Third, repeatedly re-engaged King Tormax with the same players in attempt to continually train all of Aftermath so we couldn't compete

Seriously, do you really think our master plan was to train you intentionally and concede or earn another 20 day? Even if Imrahn brought that train to your raid without it chaining to your pullers at all, it would have been purely accidental. We gain literally nothing from training another guild.

[Phatez]

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

Hail locking is considered disruption, and exploiting the mob's ability to re-set naturally. It is a raid interference. It has -always- been against the p99 ruleset to hail lock raid mobs with factioned characters to prevent them from resetting.


https://www.project1999.com/forums/s...d.php?t=189856

You were moved half way up the ramp. We had to position as to not train your raid force while pulling. Shaolen triggered zero FTE's on King Tormax at all - he was not part of our pull team for this mob. However, Imrahn triggered LOTS of FTE's prior to his final FTE that triggered AM's slaughtering.

Not to mention Zotspox has 17 engages, Mistersmilez has 11 engages, and by my log/fraps I have about 8 different Azure Guard members spam hailing King Tormax as he was trying to reset naturally.

Sorry bucko, AG was in the wrong here. First, trained us. Second, stalled King Tormax with kiting for well, WELL over 18 seconds (roughly 2mins) Third, repeatedly re-engaged King Tormax with the same players in attempt to continually train all of Aftermath so we couldn't compete, and last but not least - Fourth hail locking KT so he couldn't reset.

AG was 100% in the right to concede this mob and get out of Kael immediately. This is four 20 day suspendable occurrences in once single raid. Ignorance of the raid rules is not excuse of the raid rules.

[You must be logged in to view images. Log in or Register.]