Jump to content

Archived

This topic is now archived and is closed to further replies.

Belgica

OwlGaming - Game Administration Team Rules

Recommended Posts

Introduction:

 

 

The Game Administration Team is the main administrating body of this community. In order to create an abuse-free environment, a set of rules is to be followed by the members of this team. In order to allow members of this community to have a better eye on what can and cannot be done by this team, these rules have been publicized.

 

 


 

 

1) Becoming a member of the Game Administration Team

 

It is only possible to become a member of the Game Administration Team after having been trough a 30 day long training in the Supporter Team. There is no way of entering this team without going through that phase.

 

 

Reinstatements on the other hand can lead to an exception. If the community member was an administrator in the past, he can reinstate in a position one rank lower than his rank upon leaving. Exceptions can be permitted when sufficient reasoning is given before leaving.

 

 

Becoming a member of the Supporter Team will require your account to be created at least 1 month prior to applying. You will have to possess a fair amount of hours played and experience in any role play field. Your behavior must also be outstanding, which will be proven via your admin history.

 

 

 

2) Game Administration Team hierarchy

 

The Game Administration Team consists of several ranks, with several duties and perks. The team can be split up in two big groups, which are the Game Administration Team and the Upper Administration Team. The Upper Administration Team is responsible for the management of the server, including rules, staff reports and recruitment, ... The Game Administration Team, on the other hand, is responsible for the day-to-day management of the server.

 

 

Each team can again be split up in several ranks. The Upper Administration consists of Head Administrators and Lead Administrators. Their perks and tasks are similar, but the eventual decisions and responsibilities lie with the Head Administrators. The Game Administration Team consists of Senior Administrators, Game Administrators and Trial Administrators. Their tasks are similar as well, but their perks are different. Trial Administrators do not have access to as many commands as the ones above them, yet can already handle a majority of the in-game reports and almost all the forum reports.

 

 

 

3) Handling reports

 

The Game Administration Team is responsible for the correct handling of reports made by community members. These reports range from potential abuse being reported, to support being requested. All reports are equally relevant, only the complexity can vary.

 

In-game reports

 

In-game reports are probably the most defining task of the Game Administration Team. They are to be handled swiftly and in an efficient matter. Reports are only to be made via the F2-panel, in order to allow the previously mentioned efficiency to happen.

 

 

An Administrator may only accept a report he can handle. It is for that reason that the command /ri must be used before taking a report. Accepting and closing reports which you cannot handle is strictly forbidden. However, private messaging a community member that his report cannot be taken for the moment, due to a lack of a specific kind of staff at that moment, is allowed. When a report has been taken accidentally, the administrator should send a private message to the community member to let him know it was a mistake and then drop the report with /dr.

 

 

Administrators should also refrain from handling report in which they are involved. This includes themselves and their faction, if it involves the faction as a whole. Reports about a specific faction member may be handled, if the staff member can assure the community member he can remain neutral.

 

 

UCP Reports

 

UCP reports include 'Player reports', 'Refund requests', 'Unban appeals', 'History appeals' and other similar reports or requests. These reports also demand complete neutrality about the situation. It is obvious that the administrator may not handle the report if his opinion may be biased. If he's assigned to this report or request, he must ask for an Upper Administration member to reassign the thread to another administrator.

 

 

Administrators involved in the situation must always post their version of the story or post their view on the situation in these threads. The same goes for community members in 'Player reports'. Failing to do so, may result in a sanction.

 

 

When these threads are not being handled fast enough, it is the task of the Upper Administration to assign administrators who are able to handle the report or handle it themselves. Administrators who fail to respond to a ticket assigned to them after 7 days may result in a infraction. If a administrator has filed a inactive report, they must reassign tickets they will not be able to handle so they can still be dealt with.

 

 

Community members are encouraged to contact a member of UAT if their ticket is not being responding to for a prolonged amount of time greater than 7 days.

 

 

Community members may not request for a specific administrator to handle a certain report. Neutrality has to come from both sides.

 

 

4) Punishing

 

Members of the Game Administration Team are expected to handle reports in a fair way, this includes punishing. A community member may only be punished if sufficient evidence is found and if he has not been punished for it yet. Specific punishment times or actions are not set on any offense, as the administrator is to handle each issue in a unique way.

 

 

Administrators may also not punish other staff members. Staff members, and VCT-members, can only be punished by the Upper Administration. Exceptions to this are official side-team, such as Forum Administration Team,...

 

 

If an administrator has punished a community member in an excessive way, he may be punished for this. The community member should report this via a 'Staff Report', which is hidden for any staff member, to assure anonymity.

 

 

 

5) Punishing reasoning and automated posts

 

In order to keep track of the punishments given and to be able to check what a players history is, it is important that all punishments are well-defined. "Because I told you so" is not sufficient and will lead to a sanction for the staff member who performed the command.

 

 

If an automated post is made, and the reason did not include everything, a reply to the thread should be made, in order to clear up the story. This is important as other staff members must be up to date with what happened and why. Ban threads must always be accompanied by a reply with the evidence for the ban.

 

 

 

6) Announcements and global OOC chat

 

Both chats are only accessible to staff member, unless toggled for the whole server. They are very different and should be used as 2 different chats.

 

 

Announcements are to be made when certain out-of-character, server-wide events have occurred. Also reminders to rules frequently broken, automated posts about vehicle respawns,... This can, however, never be used to announce local events or other, irrelevant news.

 

 

The global OOC chat should rarely be used. Only if a small addition has to be added to an announcement by the person who made it, ... Annoucements, reminders to rules, et cetera should be made with /ann. This chat should definately not be used for fun remarks and jokes.

 

 

 

7) On-duty standards

 

Admins are no longer allowed to be roleplaying while on duty. Being on duty means you are active, and ready to accept reports. Being in a "hidden" state, using /hideadmin, leaves Administrators immune to this rule as they are not publicly declared as being able to actively accept reports.

 

However, administrators are expected to come on-duty as soon as reports stack up and become overwhelming for the on-duty administrators. They are also expected to help out supporters and other staff members on-duty, but also while being off-duty. This can mean answering simple questions in staff chats, but also performing certain commands.

 

 

Roleplay is being put on a second place as soon as one joins the Game Administration Team. This means that if you are one of the few members online at a time where a lot of player play, you will most likely not be able to roleplay.

 

 

 

8) Voiding roleplay

 

Administrators have the right to void roleplay if the situation is deemed too complex or unsolvable. If two players accuse each other of certain actions and none of both can provide consistent evidence, the administrator has the right to void a roleplay scene and let both players go their own way. Voiding roleplay scenes should be limited to a minimum.

 

 

If players both agree to void a roleplay scene without administrator, they are not eligible for a refund. This is put in place to assure us that players don't go around wasting bullets (OOC'ly) and then both claim to have the situation voided.

 

 

In order to get situation such as character kills or other more complex issues voided, a refund request must be made.

 

 

 

9) Administrators and rules

 

The administrators are expected to have full knowledge of all the rules of the OwlGaming community. They are set an example for new and experienced players. Fulfilling that role goes further than blindly learning these rules and following them, but includes looking to enhance them (and suggesting it), involving yourself in discussions in a professional matter,...

 

 

Failing to do so can lead to an immediate removal from the team, in extreme cases.

 

 

 

10) Server-wide commands

Administrators must keep the usage of commands which affect the whole server to an absolute minimum. Server-wide repairs, refuels and similar can break the immersion.

 

 

Also the usage of commands which create lag, such as restarting certain resources or deleting large amounts of items from the server is restricted to the absolute necessary. They must also be used in low-population moments.

Share this post


Link to post
Share on other sites

Updated with the underlined part.

1) Becoming a member of the Game Administration Team

It is only possible to become a member of the Game Administration Team after having been trough a 30 day long training in the Supporter Team. There is no way of entering this team without going through that phase. Reinstatements on the other hand can lead to an exception. If the community member was an administrator in the past, he can reinstate in a position one rank lower than his rank upon leaving. Exceptions can be permitted when sufficient reasoning is given before leaving.
Becoming a member of the Supporter Team will require your account to be created at least 1 month prior to applying. You will have to possess a fair amount of hours played and experience in any role play field. Your behavior must also be outstanding, which will be proven via your admin history.

Share this post


Link to post
Share on other sites

For the sake of having it written down... updated:

10) Server-wide commands

Administrators must keep the usage of commands which affect the whole server to an absolute minimum. Server-wide repairs, refuels and similar can break the immersion.Also the usage of commands which create lag, such as restarting certain resources or deleting large amounts of items from the server is restricted to the absolute necessary. They must also be used in low-population moments.

Share this post


Link to post
Share on other sites
3) Handling reports

UCP Reports

UCP reports include 'Player reports', 'Refund requests', 'Unban appeals', 'History appeals' and other similar reports or requests. These reports also demand complete neutrality about the situation. It is obvious that the administrator may not handle the report if his opinion may be biased. If he's assigned to this report or request, he must ask for an Upper Administration member to reassign the thread to another administrator.Administrators involved in the situation must always post their version of the story or post their view on the situation in these threads. The same goes for community members in 'Player reports'. Failing to do so, may result in a sanction.When these threads are not being handled fast enough, it is the task of the Upper Administration to assign administrators who are able to handle the report or handle it themselves. Administrators who fail to respond to a ticket assigned to them after 7 days may result in a infraction. If a administrator has filed a inactive report, they must reassign tickets they will not be able to handle so they can still be dealt with.

Community members are encouraged to contact a member of UAT if their ticket is not being responding to for a prolonged amount of time greater than 7 days.

Community members may not request for a specific administrator to handle a certain report. Neutrality has to come from both sides.

Clarified to be changed to UCP reports as we no longer handle reports on the forums.GAT members may be punished for taking to long to respond to a ticket that has been assigned to them when they do not have a inactive report filed.

Share this post


Link to post
Share on other sites

 

7) On-duty standards

 

Admins are no longer allowed to be roleplaying while on duty. Being on duty means you are active, and ready to accept reports. Being in a "hidden" state, using /hideadmin, leaves Administrators immune to this rule as they are not publicly declared as being able to actively accept reports.

 

However, administrators are expected to come on-duty as soon as reports stack up and become overwhelming for the on-duty administrators. They are also expected to help out supporters and other staff members on-duty, but also while being off-duty. This can mean answering simple questions in staff chats, but also performing certain commands.

Duty standards updated based on rule discussion:

https://forums.owlgaming.net/index.php?showtopic=8656

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy and follow our Guidelines.