![]() |
|
#1
|
|||
|
![]() On Drinal, if there was not an agreement between competing guilds for a zone/target, the generally accepted/enforced policy was first in zone with sufficient minimum raid force had rights. This was generally honored and worked fairly well. There are obviously details/specifics of this such as how many people is sufficient for the zone/mob in question, how long does that claim last (1 try, given time interval, etc), and such, but that's the general policy that was in place for the time I was around. (Up through GoD/OoW timeframe)
| ||
|
#2
|
|||
|
![]() First to engage means just that. Some encounters are regarded as multi-mob (e.g. NTOV) so FTE for the entire encounter is based on FTE the first mob. Clearing trash is not engaging the mob. There is no such thing as "leapfrog" unless the encounter has been engaged by guild A and guild B engages the next mob in the encounter.
Two rules (GM enforced): No training, no ksing. As has been previously mentioned the ks rule often wasn't enforced due to practicality, unless it was a common occurrence and could be predicted. The reality is most guilds realize that acting like asshats will get the same asshattery back at them (probably from multiple guilds on this server) - the net result for those guilds is a much harder time, more wipes, and less loot. It doesn't make sense in the end. Whatever the rules turn into, please, please, do not have anything that gives precedence to who was in zone first - that would be poopsock all over again. | ||
|
#3
|
|||
|
![]() Off-topic, sounds like you've got some sort of FFA anti-camping rules for before the mob spawns. AND I LOVE IT! Tracking/killing'd be awesome.
A solution to leapfrogging/ksing would be to use timers still, but only after the boss spawns. 15 claims, second has to have 15 to call time. Change the timer length for CT or any planar boss while trash is up to 1:30 or 2 hours to allow for clearing.
__________________
Accersitus Mage
Ennui Monk Vita mid 40s Cleric | ||
|
#4
|
|||
|
![]() They made instances...
| ||
|
#5
|
|||
|
![]() In my experience rulings were made mostly on a "how do I get out of this with the least amount of drama" perspective from the GM's. As the top guild we were pretty much always ruled against regardless of the situation simple because another farm kill for us was less of a loss then an important or step up kill for an up and coming guild
It eventually got bad enough that a forced rotation was created | ||
|
#6
|
|||
|
![]() Like has been posted, officially the GM policy only considered single mobs at a time so you could leapfrog to your heart's content and GM's couldn't/shouldn't have done anything about it.
| ||
|
#7
|
||||
|
![]() Quote:
| |||
|
#8
|
|||
|
![]() GM's rule pretty much was whoever got the loot from dps, got the loot. Unless the GM witnessed something himself. The "player rules" (first come first serve) > all, and while there was some guilds that exceeded the player made expectations, those guilds were well known, and got the same respect they showed.
It worked well the race was fun, when you won, and sucked when you lost, just like any competition. And sometimes you would loose the race, but the guild would wipe from racing and you'd win the war. | ||
|
#9
|
|||
|
![]() There is only one solution that will even come close to working. And it's one you definitely don't want to do.
Spawn the raid mob manually, flag it as unkillable. Stand there until a raid force is assembled. At 15 players, it's their mob. When the poopsockers log on top of the mob, warp them out. When the next guild zones in to try to leapfrog, send them packing. When the first raid force nears the boss, flag it as killable. This is the only way to ensure fairness among a playerbase of exploiters, kill-stealers, and douchebags. It's not the least bit classic, but neither is the attitude of the playerbase. It's akin to standing over a group of kids to make sure they don't hurt each other on the playground. But that's what they are; a bunch of kids. This crew can't handle fair-play or even friendly competition. They WANT to piss off their rivals. And they'll do it any way they can. And they get a huge thrill out of getting away with it. Aye, you have much better things to do than babysit every raid kill on your server. Although, would it be any less time-consuming than dealing with the shit that's happening now on raid kills? You've already got one full-time babysitter in EC, and that's been effective. Might be something to think about. People still get their phat lewtz, and it could still be random...as random as you want it to be. | ||
|
#10
|
||||
|
![]() Quote:
| |||
|
![]() |
Thread Tools | |
Display Modes | |
|
|