![]() |
Managing Players
I've been working on servers for a while now, and I believe I've found a system to effectively deal with players, while letting developers do work.
First, I propose removing all different "departments". All development becomes "Staff". All management (manager, administrator) becomes "Admin". This is for public; it is okay to maintain a structure within a server. However, it should be limited. It is important that you still have a basic hierarchy. The number represents how many of this staff there should be. Manager [1] [Admin] - should be someone who is available to staff members. The job of the manager is not to develop, but to make sure everything runs smoothly. The manager needs to make sure staff get along, and that they have everything they need. Administrator [1; 2 for large servers] [Admin] - should be someone trustworthy. They should have rights to hire/fire, in case of an emergency, but should not use these rights unless it is urgent (e.g. someone is going to delete things). The administrator keeps an eye on things, making sure players' needs are met. Development Chief [Staff] - only needs the rights needed to do their job. This person is not in charge of a department (e.g. NAT Admin), but is a normal developer, who can be trusted to make sure everything runs smoothly in "their" department, and make sure quality standards are met. This person is also trusted with the task of hiring. This does not mean they get the rights to do it themselves; they are trusted with deciding who will be best for the job. Development [Staff] - these people have differing rights. They have only the rights needed to do their job. Why does a graphic maker need to be able to warp? Development chiefs also fall under this category; they don't receive any extra rights just for being the chief, unless they need rights to check on how other people are doing. This is why it's very important that there is an active manager. The manager has to make sure the developers have the rights they need. That's the end of development staff. What about non-developmental staff? They fall under "Player Relations". There is only one type of player relations staff. There is no reason for a chief of any kind; the manager can handle the hiring of these people. There should always be at least one player relations staff member on! This means that you may need fifteen player relations, if you have a large server. Additionally, when the manager or server administrator is not busy, they can put on a player relations tag and help. Player relation staff members should all have the same rights, so that no one feels like they are not important. I recommend the following rights:
PR staff should deal with players needs only, and contact a staff or administrator when they are unable to help someone with something (a glitch in a script, can't log on, "I swear it was my brother who was hacking", etc). Many staff like to wear tags as they work. For example, level makers will wear their "LAT" tag while they are creating a level. First of all, following this system, there is no such thing as a "level maker" or a "LAT", only a developer staff. Staff should never wear their tag unless it is essential to the task. There is no need to wear your tag while scripting, unless it is necessary. Player Relations, on the other hand, should always wear their tag while they are helping so that they can be recognized. Administrators should wear their tag as well, when they are not overwhelmed with work. However, it should be clear to players that they need to go to Administrators, and eventually Staff, as a very last resort (e.g. no PRs are on, or the PRs are unable to assist the player). I believe this system is able to keep players happy, while also keeping staff happy and efficient. Comments? |
The general consensus is that development staff wear their corresponding tags (LAT, GAT, NAT, etc), so that people know who to contact. What good is contacting a GAT, when there's something wrong with your inventory? Personally, I think PR staff are pointless. If the staff member doesn't get an RC, then the position they're in is otiose. All PR staff ever do is forward a message to the corresponding department (got a problem with a player?: forwarded to GPs; inventory screwed up?: forwarded to NATs; level not loading correctly?: forwarded to LATs; somebody stole your personal body?: forwarded to GATs). Essentially, all that's left for them to do is answer questions regarding the use of the server, which wouldn't be needed at all if you provide a decent tutorial.
Departmentalizing (meaning, you have heads of departments that run the show) is essential to most servers, especially large servers. The manager deals with the huge issues and schedules, and the department heads deal with all the technical stuff. On Valikorlia, a department head as always been the person to hire staff; the manager just gets the final say-so. Consequently, department heads also do the firing. You can run your server like this, but I'll run mine how I like to (not that I run a server, but still). But, I definitely think that it's important that development staff have their tags on all the time, and that PR are useless. |
Quote:
|
nice system, and PR are not pointless in my opinion.
although its true you need 2 know who to contact for a developer problem... |
I don't really like it.
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
|
Quote:
I quit asking questions because either staff dont answer or are rude when they do (a lot of the time, not all) |
Quote:
For example, they could leave a note for scripters "There's a glitch in the inventory where you can't scroll". This way, staff aren't bothered with questions that they can't answer, wasting their development time. PRs could answer questions about the game immediately, and leave notes for others. |
Quote:
I think its a good, logical, setup. And PR is useful, look at GMs in WoW? You dont need one for every department though, just one or two online at any time period. I never bothered myself by giving ranks to people though, in a server you shouldn't need that much staff that no one knows every "employee". Just make sure that everyone knows their place, and your good. |
I know I was really blunt in my reply, just trying to think of a way to explain it.
|
I think all staff should have RC, builds community. Why don't you want non-development staff having RC? Segregation went out a long time ago.
Also, I am NPC Admin on Valikorlia, making me head of NAT and the one with the final say (besides the Manager(s)) on everything scripted related. So you're saying I don't need to be scripting admin or have all rights? I also do stuff beyond my job, like banning, jailing, and banning. Also, if a player has questions that were answered in the tutorial that he or she didn't do then its their own stupid fault. I also put my NPC Admin tag on when I'm working so people know who to come to if there are bugs and stuff. I suppose I could script a support ticket system sometime in the future, that could be used for bug reporting and other things. I wish Stefan would release external scripted windows so I could integrate jail system into RC. |
Quote:
:asleep: |
Quote:
|
Quote:
Quote:
Quote:
Quote:
Quote:
|
Quote:
|
Quote:
Quote:
So yes I do need to be "scripting admin" so I can boss people around and harp on them when they do something they shouldn't be doing, and have the power to back up related threats. Quote:
If people are trustworthy, then limiting rights is simply an annoyance. I don't have enough fingers to count how many on Val have change rights and such. Quote:
Quote:
Quote:
|
Quote:
Quote:
This may not apply directly to you, but I designed the system to work in as many situations as possible. Quote:
Quote:
Quote:
Quote:
Quote:
|
Quote:
Yes, there is -> Good, give them RC access. No, there isn't -> Don't give them RC ... Why? ... It works a week or two but then they start to idle on RC day and night, the players pm then and never get an answer -> people get sick and leave the server About "Chiefs", "Captains" etc.. it is ok to have a teamleader for each development section. If you have a big team with maybe 10 people it's also ok to hire some secound team leader. But it really gets stupid if you start to create positions like "Chief's Asst.", "Co-Chief", "Captain", "Captain's Asst.", "Co-Captain" and just have 2 team members. There is absolutly no need for that and things only get worse. What I say now happened lots of time to me back when I started developing for servers... You ask the first one above you to do something and he agrees, the one above him says no and so on after days passed the teamleader finally says no and you get frustrated because all you work was useless. The same basically goes for such crazy creations like "Account Manager", "Head Uploader", "Serverconfigurator" etc. These "jobs" are not needed because that's the managers work. But lots of people have friends and want to give them RC with all rights they will never need because they do nothing instead of slowing the development process down. Yes, sure you did rent the server and if you want to have people with such weird job fine - but then you shouldn't complain if your server doesn't start growing. Later on if you have a huge server, and I'm talking about a playercount like back in Classic Graal times you might need more people to deal with things and then it's also ok to to have a FAQ Chief, FAQ Captain and also a Co-FAQ Chief and a Co-FAQ Captain but not while your server is in development.. But whatever - such things will always happen, there is no way to stop it and somehow that's fine. Means we got at least something interesting to talk about :D |
Quote:
Quote:
|
Quote:
For the most part, Valikorlia has been pretty successful, when it comes to its staff. We've had long-running, active staff members (some have been around for nearly 10 years, back when Kharlia was a part of the original client world). We usually get along, and we usually get things done. Valikorlia also has FAQ staff. They are useless. Once in a blue moon, they're asked questions. When they are, they repeat the question on RC, because they either can't do anything about it (jailing, etc), or it's related to development. I went on UN to report somebody harassing me over global PMs through that server. I had to contact a PR person, because no GPs were on tag. They directed me to a GP. I could've skipped the middle man and saved time. Also, tutorials are usually the first thing you do on a server, and you rarely have a choice in the matter. Personally, I find that a good idea. We should probably do that with Valikorlia. But, you know. It's your server, so it's your choice. Not everybody wants to be friends with their staff, or even trusts them. On Valikorlia, we tend to. Of course, every once in a while, somebody will delete the server. But, that's a small price to pay for tradition. ^^ Quote:
|
Quote:
Quote:
I'm also a lazy slob. |
Quote:
You bring up a good point though; this system could use some work to add a community aspect, or other things based on trust. Quote:
Quote:
You bring up some very good points that I didn't think of. |
Quote:
|
Quote:
Quote:
|
I think all staff regardless of position should at least put some sort of effort in helping players with issues even if it's not their job to do so.
|
Quote:
|
Quote:
Even NATs and LATs sure can answer questions, too. They are the people who create the server and should know about it best, better then the Support staff. So what should be wrong about answering a question - nothing. |
Quote:
|
Quote:
|
Quote:
Because if one FAQ has RC and the other hasn't they start to fight and you age bugged again and again until you say ok to giving their RC back. Be strict from the beginning on and you will have less problems. |
Quote:
Quote:
I couldn't Manage any other way, and didn't have staff, thus why I am not Manager any more. |
Quote:
|
Quote:
|
Quote:
|
I dislike the fact that scripters no longer have their own "NAT" position which is an equal to GAT or LAT. They are now "Developers" or "Scripters" or something silly where they're pretty much free to do whatever they want (UN being a prime and significant example) as eveyrone is desperate for "good" "NATs".
|
I've always used the tags:
Graphics Levels Scripting Animations Audio |
Back to a old Post from someone.
Promotion players fast for doing alot of work is bad. They actually keep working for a promotion. And when they get it they work less.. And less, And thats how they stop working. |
Why promotions? You only need promotions from x to Admin and from Admin to Manager, everything else is basically useless. Just give them more rights when they really need them to do their work ;o
|
| All times are GMT +2. The time now is 03:55 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.