The managers can't be held responsible for what is uploaded; so long as they handle the situation as it should be.

Does this include temp folder?
Complete disagree. On Vesporia, our staff ranks are like this:

Staff (development staff; rights are given based on what is needed)
PR (player relations)
That's crazy. Why shouldn't Player Relations staff be able to upload heads, etc? All it does is allow the developers to create a better server.
It's been locked like that for years :p

Yes, instead of fixing this, let's just tell staff to not mass message :)
Can we just link to the Graal rules?
Like what?
I agree, however, rclog.txt is always read-only.
Why? x_x
If someone isn't important enough to the server to have RC, they don't need to warp. Like Skyld said, perhaps being able to warp to certain locations such as events.

Is this a rule, or a guide? You can't log onto Graal if you don't have IP ranges (or PCID) set.
lol ... there aren't many staff tools that aren't abusable, but can still be used to get the job done, always.
Ork is gonna take this one really hard.
I disagree; it's a waste of time to make a jail, and it can even potentially hurt your server by causing un-needed lag (mainly if you suck at scripting).
What are ban reasons for, again?
Even if you follow all these rules, we can still globally ban you, just because we feel like it.

A guide for what globals believe to be a fair ban time for common rule violations.

I meant the ban reason you put in, not the predefined ones. It seems rather pointless to put every single thing in comments.

I agree. Why put it in comments when you can just put it in the ban reason? This also can be looked at globally by all servers(at least, I'm pretty sure it can be) to get an idea of the player, when comments are local to the server, so really serve no purpose beyond the server.

Agreed.

I don't think he's so much against PR staff being able to upload heads. I think he's more against a staff position created with the sole purpose of uploading heads.

I can relate to that >_<.

This is correct. I covered the meaning of that rule, above (in response to Frankie):

Basically put - People shouldn't be in a staff position that was created for the sole purpose of uploading people's heads. Uploading heads should really only be a side-job for a staff position that can handle the time management.

No, but they are responsible for making sure that what is on their server is not stolen or otherwise illegal and will be held responsible if they allow that sort of thing to happen. However, a rogue staff member stealing GFX or otherwise uploading illegal things without the manager knowing will not get the manager in trouble.

Yes.

I agree with you here. I'm don't think that the rules should dictate how the server's staff team is organized.

Again, I agree with the idea of a PR staff member acting as an FAQ/Uploader/GP, but the rule is to prevent certain servers from always having five people on RC at a time whose job is to merely upload heads/bodies/shields.

I agree, this needs to be fixed.

Sure, but a lot of servers need rules that aren't in the normal Graal rules. For example, I'm sure that with Vesporia's unique gameplay, there will need to be rules especially for Vesporia.

A welcome screen for players that displays news, rules, etc. A PM from the NPC-Server upon login. An NPC that when grabbed links/displays rules. Something is needed so that a player can't say "Oh, I didn't know it wasn't a rule" and at the same time a staff member can't say "Oh, that's against the rules" with no basis.

I agree.

I agree...the rule should really be something like "No staff tools should exist for the sole purpose of abuse. (ie: /kill HoudiniMan)"

It's not very hard to make a very simple jail. There is a server option jaillevels= that can be used for individuals who "suck at scripting". Additionally, GPs can even follow a warning system where three warnings = ban instead of first offense = ban.

Seeing that a player has been banned for "Cheating" is often not enough when we have to go and look in to a ban complaint that we get on the support center. Its much easier for us to know what's going on and provide faster support for people when the comments have details on the incident. This way we don't have to look through logs or wait for a staff member to log on.

Good to see that you understand. :D

When I ban someone I keep the reason short and to the point. I put the greater details and evidence and such in the comments.

The ban reason is displayed to the client when they try to log on. It's a short and sweet answer to the question "Why am I banned?!"

Comments are a record of a client's good or bad behavior and evidence for or against them. Comments don't need to be globally accessible because if Johnny was banned on UN for reason "Using trainer in spar" you really don't need to know which trainer or how many times to know he's a cheater, and maybe not the best hire.

I should reword this.

This is meant as "for the purposes of this guide these are the names of positions". Not "You must use these ranks".

On every server there is a top level of staff who manage the rest, and there needs to be one chief in charge of the management who is accountable to the PWA and other global administrators for the state of the server.

For the purposes of these rules, that chief admin is called Manager, and the rest of the admins are called Server Administrators.

Under them then exists the different branches of staff teams. They have chiefs who control the branch but not other branches. Ie, the "PR Admin" of Valikorlia does not hire and fire NATs or GATs (one would assume).

So to review, and I will make this more specific:

For this document, staff are organized as follows:

• Manager - Chief admin of the server who speaks for the entire staff team. Reports to global administrators.
  
• Server Administrator - admin of the server who governs multiple/all staff departments, can generally add/remove staff and rights to enable other staff to do their jobs.
  
• Department Chief - Head of a department of staff. Examples include: GP Chief, LAT Chief, PR Chief, ET Chief, and standalone admins such as PR Admin or Business Admin. These admins oversee their area of expertise and do not control other departments.
  
• Department Staff - Specialist in some area of server staff duties. Examples includE: GP, FAQ, PR, ET, NAT, GAT, LAT, Ganis, SFX, etc.
  
• Department Trainee - Staff in training, who may report to Department Staff with more experience, or the Department Chief directly. Might not have full rights and/or responsibilities associated with their position.

I think this is much more clear now? :D

I had the idea, and many agreed, it would be best to separate job descriptions from the rules and make two threads. So, from this point on let's focus on rules and not so much duties or "managers must ________".

So the difference here is:
Provide training to new staff is a duty.
Do not ban people just because you hate them is a rule.

This is a pretty fuzzy distinction, I know, so if you want to discuss something and you aren't sure then go ahead. Just know that I'll be making a new thread for job duties where we can hammer all that out later.

More clarification:

Also updated in first post.

Well, the reason I use the word "reinvent" is because things like scripted "warpto" or "warpother" are reinventing what's already there. In which case, it would be better from not only a security aspect, but also an organisational aspect, to just use the RC rights. I don't have a problem with things like "summon" because they aren't really needlessly reinventing; they are not strictly already existing functionality.

Wrong. You can rename it to rclogINSERTWHATEVERYOUWANTHERE.txt. For example, I rename mine to something like this after each month:

rclog-july-2008.txt

Perhaps try and list more reasons than just the one. Also, this example could perhaps be reworded, to (I assume) emphasise a hire, upload and firring in a short amount of time. So that people don't read anything into it isn't supposed to provide!