Quote:
Originally Posted by HoudiniMan
I intend to distinguish here for classic/hosted servers and private worlds. I fully believe that Classic servers won't be hampered by the limit and should hold themselves to higher standards of management...
...So far nobody has demonstrated how this would cause a server to be hampered in operation. If somebody has a valid reason a classic server couldn't run well with the limit in place, we can certainly discuss changing the limit.
|
The thing is, there are
always exceptions. I've worked on servers where there are have been quite a few dedicated, trustworth staff who have worked on the server in upwards of 2+ years. Why should they be denied promotion and increase in responsibility just because of a silly rule?
Would it hamper operation? Probably nothing major. But, remember, not everyone is on graal 24/7. Just because a manager is only actively on RC around (let's say...) 15-20 hours a week doesn't mean they deserve a demotion. That leaves 148-153 hours in a week in which someone could possibly need something from that person. I'm not sure what the limit is, but by limiting the number of high-level RCs, you are limiting the chances and percetages that a person that is needed will be on.
Can someone just wait? Absolutely. However, is this "hampering operation"? Yes, it is.
Obviously, there is a
very fine line when it comes to this, and no matter what you say or do, there are going to be servers who mess up and give someone irresponsible high-level RC rights. However, these mess-ups are very commonly easily fixed, and they are your job to do so. Not to mention, even when you limit high-level RCs, they can still be given to irresponsible people. You aren't completely preventing anything, just lowering percentages.
Precautions are good, but over-doing it for reasons that aren't 100% necessary can be just as negative as the negative things the precautions try to prevent.