Blood Guard trains themselves, blames innocent bystander! :D

[Puluin]

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.

Hate to burst your bubble, but no where on that rule page does it say ANYTHING about hail locking.... in fact.... if you ctrl F "hail" there isn't a single hail word in the entire post. as far as "lock" or "locking" goes, they refer to lockout timers or locking up a mob AFTER you have agro.

[Spyder73]

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

Hate to burst your bubble, but no where on that rule page does it say ANYTHING about hail locking.... in fact.... if you ctrl F "hail" there isn't a single hail word in the entire post. as far as "lock" or "locking" goes, they refer to lockout timers or locking up a mob AFTER you have agro.

This might have flown in TMO days but the staff has repeatedly stated 'letter of the law vs intent of the law' and in this case you would be convicted in P99 court of raid stalling since you were doing it for no other reason but to grief another guild.

[Puluin]

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

This might have flown in TMO days but the staff has repeatedly stated 'letter of the law vs intent of the law' and in this case you would be convicted in P99 court of raid stalling since you were doing it for no other reason but to grief another guild.

Can't grief by hail locking. (With the exception of obvioisly being a duche by draging the mob to some obscure or annoying corner with zero intention of killing it) The mob is still there to agro and get a FTE message.

[Legday]

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

Can't grief by hail locking. (With the exception of obvioisly being a duche by draging the mob to some obscure or annoying corner with zero intention of killing it) The mob is still there to agro and get a FTE message.

I have to agree with that. A hail lock is a stall only if there is competition there trying to pull it from it's spawn point. Thats just common sense. As long as you aren't doing it in a way that keeps another guild from FTEing and killing, the staff isn't going to give you any problems.

On the other hand if I'm an AM monk I'm trying to perfectly time when KT's agro drops on AG people so I can get a clean FTE and bring to my raid. Hail locking is just poor form in that situation, but idk about being explicitly against no stall rule.

[beargryllz]

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

This might have flown in TMO days but the staff has repeatedly stated 'letter of the law vs intent of the law' and in this case you would be convicted in P99 court of raid stalling since you were doing it for no other reason but to grief another guild.

It's not stalling. That other guild can so, so, so, so easily get FTE if some dork is hail locking. That's like competitive raiding 101. If you want an absolute guarantee that your guild goes home with nothing, hail lock the boss so the other guild can FTE it

[Phatez]

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

It's not stalling. That other guild can so, so, so, so easily get FTE if some dork is hail locking. That's like competitive raiding 101. If you want an absolute guarantee that your guild goes home with nothing, hail lock the boss so the other guild can FTE it

bLABH blah nbLAH bLAH bLAH bLAH BLAH blah blah blah blah blah blah.


REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.

Your wrong. Sirken considers it stalling so its stalling.

[Teako]

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

It's not stalling. That other guild can so, so, so, so easily get FTE if some dork is hail locking. That's like competitive raiding 101. If you want an absolute guarantee that your guild goes home with nothing, hail lock the boss so the other guild can FTE it

In the words of the great poet Dwayne "The Rock" Johnson;

IT DOESN'T MATTER WHAT YOU THINK.


Sirken said it's against the rules years ago. It has always been against the rules. Being able to perpetually lock a mob in your raid camp until you're ready to engage it is shady. Ex: locking Dain at the bottom of the well while other guilds are up top, etc. No feasible way to pull it.

Ignorance of this rule is not excuse of this rule. Hail locking a mob in your camp disqualifies you from that mob, period.