Quote:
|
Originally Posted by Googi
This thread contains the best staff organization system ever. If you're a server manager, implementing this system will greatly reduce corruption on your server. However, you won't actually implement is because you are afraid of losing the power that this system would require you to divest.
|
Just because you call something the best does not make it so. It may be the best in your opinion, but it's quite egotistical of you to go as far as to say that this system is
the best ever.
Quote:
|
Originally Posted by Googi
- Nobody (including, of course, myself) is truly immune from being corrupted by the possession of power. Being corrupted by power is an inevitability for all who possess it. Of course, the server managers reading this believe they are specially immune to this rule (they aren't), and that they will be able to "get tough" with the guy they've been friends with for over a year when it turns out that he's corrupted (they won't).
|
It's not really that they feel that they are "immune" to corruptivity, but moreso that they are just too lazy to go the extra measure to prevent it, or they have done as much as they could.
Quote:
|
Originally Posted by Googi
- There is no reason developers should have the tools of rule enforcement simply because they are developers.
|
Quite a broad statement, which doesn't really apply to all developmental positions. Coders have the ability to develop their own tools of rule enforcement. You could tell them not to, but could you really get mad at them for banning a trainer user/jailing a trouble maker that is currently on the server, not listening to you at all, and no one else is around to handle the situation?
Quote:
|
Originally Posted by Googi
1. The enforcement of rules should be outsourced to NPCs as much as possible. There should be as many anti-scamming and auto-hack-detection mechanisms in place. On 2K1, this would mean owner tags on rocks. Whenever any kind of problem arises with any form of bug abuse or related problems with players, the immediate answer must always, always, always, be to try to script your way out.
|
This seems more like server security advice, and not advice on a staff organization system.
Quote:
|
Originally Posted by Googi
2. Developers would be entitled only to powers related to developments (pretty much just warpto, FTP and update level). As in, they wouldn't be able to ban and jail.
|
As I stated above, this is another broad statement that doesn't apply to all development positions, since you don't need to have the RC right to ban players as a coder to actually ban a player, since you can code yourself a police system.
Quote:
|
Originally Posted by Googi
3. The server manager shouldn't enforce rules on average players (which means the server manager also wouldn't be banning or jailing non-staff players).
|
The server manager shouldn't enforce the rules? Does anyone else see something wrong with this statement?
Quote:
|
Originally Posted by Googi
4. Log as much as possible. If you can log it, you should log it. The only exception would be if logging something would cause unacceptable stress on your NPCServer.
|
Once again, more security advice instead of advice on a staff organization system.
Quote:
|
Originally Posted by Googi
Stuff about number 5
|
First off, you say that the server manager shouldn't enforce the rules, then in this section you state that the GP wouldn't enforce the rules, but the server manager would? Your statements are quite vague and contradictory, or atleast were worded in such a way.
Secondly, this council of players that basically decide the fate of rule breakers is by far the worst idea a server could ever implement. Graal is based on popularity and how many butts you can kiss to become popular. If your best friend broke a rule and you were to decide his fate, I'm pretty sure you would let him go. And, even if you wouldn't, over 50% of the Graal population certainly would, thus making the system useless.
GP's are around to enforce rules and keep servers as friendly as possible. If you log on a server and everyone is cursing off the top of their lungs and have profanity in their nicknames, then obviously something is wrong with the staff team on that server.
A server should never have to rely on its players to do all the work for them.
Quote:
|
Originally Posted by Googi
6. FAQ and Events Team (if the server has them) would be hired pretty much like normal. Usually be a chief appointed by the manager. Of course, neither them nor their chiefs would have enforcement powers. (Although events team members would be able to remove disrupters from events, but not jail them. See proposal 1.)
|
Why would Events Team members have rights to jail anyways?
I've seen events jails before on a few servers, which I found quite ridiculous to be honest with you, but besides that, an Events Team member shouldn't have rights to jail anyways.
Quote:
|
Originally Posted by Googi
Notable problems:
|
Wait, I thought you said this was
the best staff organization system? How can anything be deemed the best when the creator sees problem with his/her own system?
Quote:
|
Originally Posted by Googi
- People can get their friends from other servers to vote for them or the candidate they like. Can be dealt with somewhat by requiring voters to have a certain amount of online time (the second-place candidate could pretty much be relied on to make sure the winning candidate won with legitimate votes.) But even then there's problems like ex-players coming back just to vote, etc.
|
Yes, this supports my popularity statement, and my friendship statement.
Quote:
|
Originally Posted by Googi
- Whoever oversees the GPs could try to use their power to manipulate their actions. The threat is lessened by having an elected and recallable overseer. Ultimately, it may really be better to have the other GPs deal with allegations against a GP. The suggestion of an overseer is the suggestion I am the least certain of in this entire document.
|
Ultimately, it would be better to use the standard GP system with a Chief in charge.
Quote:
|
Originally Posted by Googi
Since these proposals will never actually be implemented on a server, this thread isn't really a suggestion but rather a challenge for anyone who disagrees with me to prove that the current system is superior or to create their own system and prove that it's superior to this one.
|
Oh, you considered it a challenge to prove your system wasn't as perfect as you claimed it to be?
Your proposals are quite preposterous. Why would any manager have random players decide the outcome of rule breakers? If you can't trust the people in your police force, then they shouldn't be staff in the first place.
You can't stop corruptivity, no matter how hard you try, and this system won't lessen corruptivity at all.
You can even limit everyones rights so much that they have to be dependant on the server manager for specific rights to things when they may need it, and even that won't stop corruptivity, because all it takes is a coder to have rights to one wNPC of their own to be able to reek havoc on the server.
So are you now going to suggest limiting the NPC rights of coders to absolutely nothing? And to limit the FTP rights of level makers to nothing?
Because the only ultimate way of stopping corruption is by giving nobody rights on your server and doing all of the work yourself. Inconvenient? Very. Free from corruption? Of course, unless you turn corrupt and ruin your own server.
You need to understand that a staff team is more than a team, but a family. Each staff member should have the will to help each other out, to make the server run more smoothly. You can't just limit all of your staff members rights to the point where it becomes uncomfortable to work on that server and thus have them leave because they can't develop at all without having you around all the time.
You can't make entire assumptions just because a few people go corrupt. Many of the current staff systems work perfectly, but you are just never 100% immune to corruptivity. There will always be that one staff member that you hire that will end up turning corrupt, and you can't do anything about it.
You want to know the best way to not have to worry about staff going corrupt? Keep weekly backups of all files in your FTP folder (which should include the scripts and levels and graphics and so forth). So, if a staff member were to corruptively delete anything, you could easily back it up and notify globals to punish this person for doing so, thus, they get in trouble, and the server is not harmed in any way. Of course, you could have the staff that corruptively reset players and so forth, but you could design systems to backup player attributes after X amount of time and so forth. If that's not efficient to you, then you can always award the players that were unfortunate enough to be in the middle of that corrupt staff member's wrath with some free items to help them back on track and so forth.
There are tons of other methods of lessening corruptivity than to go as far as change your entire organization system. If your a responsible manager, then you shouldn't have any worries. It's the manager's responsibility to make sure that if any staff went corrupt and messed with the players items or messed with the servers files that they would be able to backup those items/files and thus nothing would have been harmed.
It all depends on the type of manager that is managing the server.