Quote:
Originally Posted by Frieza_Prexus
[You must be logged in to view images. Log in or Register.]
Regarding the consecutive kill rule, if you put a limit so that a guild cannot kill a mob twice in a row, it becomes a situation where two guilds will likely dominate the mob. In this case, TMO and FE. If you say that no guild can kill a mob more than once in the last three times it pops then it will be TMO, FE, and probably IB. This order will continue until the situation become a sort of rotation for each individual mob. It naturally establishes a pecking order. These situations are undesirable to some guilds because 1) it prevents focusing on specific mobs and 2) it lessens the competitive nature of the server by precluding the competition from contesting any given kill.
The issue is not "only TMO is getting kills." That problem would indeed be solved by the above rule. The problem is that smaller guilds are unable to meaningfully compete and participate in the end game due to the extreme dominance of several hardcore guilds under the variance system. Spread the kills more evenly among the hardcore does nothing to address the problem of casual exclusion. (NOTE: For the diction hawks I use casual here to define something other than TMO and FE because it's easy. Deal with it)
In short, no one simple solution has found enough broad-base support. When you eliminate the impossible (simple solutions), you're stuck with whatever is left over no matter how complex or unlikely.
|
Again, it may (probably) set up a 3 guild rotation, but it also gives every other guild 2 more chances at a kill. This wouldn't exclude any "tier B" guilds from "tier A" mobs, it wouldn't guarantee any guild a mob on any given day, and it would guarantee you big guild types the need to have that coveted "chase".
We both know that there's no way were going to get an agreement with rules that segregate the guilds into a lesser/greater tier (caste).