Difference between revisions of "CommunityAdministrationNetwork/Field Agent"

From BZFlagWiki
Jump to: navigation, search
(New page: {{CommunityAdministrationNetwork}} ==Overview== This page describes the information needed by Field Administrators for the [[CommunityAdminstrationNetwork/About|Community Administration N...)
 
Line 27: Line 27:
  
 
===Be Civil===
 
===Be Civil===
Field admins are expected to conduct there administration in a calm and civil manner. They should not let anger or personal feelings get in the way of there administration duties. All discussions, arguments, or disagreement with players over administrative issues should happen in private so they will disrupt the play for others as little as possible.
+
Field admins are expected to conduct there administration in a calm and civil manner. They should not let anger or personal feelings get in the way of there administration duties, they are expected to not hold any "grudges" against specific users. All discussions, arguments, or disagreement with players over administrative issues should happen in private so they will disrupt the play for others as little as possible. Field admins must remember that it is there job to help all users play the game and have fun.
  
 
===Give the benefit of the doubt===
 
===Give the benefit of the doubt===
Field admins are expected to give a user the benefit of the doubt when dealing with an initial violation. Users should always be approached with private chat text to ask them first to stop the behavior that is causing the violation. The admin should explain what the behavior is, why it is a violation, and be willing to help the user resolve the issue to the best of there ability.
+
Field admins are expected to give a user the benefit of the doubt when dealing with an initial violation. Users should always be approached with private chat text to ask them first to stop the behavior that is causing the violation. The admin should explain what the behavior is, why it is a violation, and be willing to help the user resolve the issue to the best of there ability. Field admins are expected to remove bans on users who have spoken with them or other admin staff in a civil manner and have agreed to not repeat there offenses. Users that abuse this will not be given that courtesy a second time.
  
TODO:: ADD THE REST
+
===Use the least necessary action to resolve an issue===
 +
Field admins are expected to resolve issues with the "lowest" possible admin action. They should not kick when a silence should work, not ban when a kick would do the same. Bans should be the last resort as they are network wide. Field admins are expected to warn before all actions. The CANAdmin plug-in will track and enforce the warning of people before higher level actions are allowed ( kick and ban ). Field admins are expected to work with all users to resolve any violation issues, and never simply "blow them off". They should refer user to the Core admins if a suitable resolution can not be found.
 +
 
 +
===Use CAN admin abilities only for network violations===
 +
All admin actions on servers must be in response to a violation one of the six network rules. No other use of the network admin functions are permitted. The CANAdmin plug-in will require the rule number that is in violation for all actions. Field admins may be granted additional abilities by server owners, and be asked to enforce additional rules. If the Field administrator agrees to this, then they must use the server's local administration system to enforce those additional rules, and not the network system.
 +
 
 +
Violations of rule 5, the minimum language rules, must violate the very specific conditions set forth in the rule. Interpretations of the rule to include additional language that is not mentioned in the rule, based on personal distaste, or beliefs, are not allowed. Violations of rule 5 must be very clear cut before ban level action is taken. Most users who will skirt the edges of rule 5 will most likely break another rule in the process, usually rule 4. For Simple violations of rule 5 can be handled with a simple net silence command after the required warnings. While annoying, violations of rule 5 have the least affect on the game, and are the simplest to resolve, even for regular users ( everyone can use the silence command ). Field admins are expected to understand that different people have different levels of tolerance for language, and may find things more or less offensive then they personally do.
 +
 
 +
Administrators that abuse the network admin features for there own personal reasons, will be removed as network administrators, and possibly banned from the network depending on the severity of the actions. All network actions are logged with the BZID of the admin who applied them. If need be the core administrators can remove any and all network actions caused by any administrator.
 +
 
 +
 
 +
==Administrative actions==
 +
Field administrators may take the following administrative actions on any server.
 +
 
 +
===NetWarn===
 +
  Usage
 +
  '''/NetWarn''' ''Rule'' Player ''Comment''
 +
 
 +
This action will notify the specified player that they are in violation of the specified rule. The warn action will be logged with the central network database. The user will also receive a BZBB PM with the warning and link to the network rules.
 +
 
 +
===NetActivityList===
 +
Usage
 +
  '''/NetActivityList''' Player
 +
 
 +
This action will list the history of warnings, kicks, bans, silences, and other admin actions stored for the player across all network servers. Each actionwill list the action, rule violated, the admin, and the comment given at the time of the action. Players have access to a simplified version of this command that will list all the actions for there call sign, but not any others. Server Admins (anyone with an @) also have access to the full version of this command for informational use.
 +
 
 +
===NetSilence===
 +
Usage
 +
    '''/NetSilence''' ''Rule'' Player ''Comment''
 +
This action will block all chat for the specified user on all network services for a period of one hour. The action will also be logged the same way as a warning.
 +
 
 +
===NetKick===

Revision as of 17:17, 9 May 2007

CAN logo.png This page contains information about an idea called the Community Administration Network Project. It does not represent any rules, opinions, or regulations for the BZFlag project. The C.A.N. was an idea whose author has lost interest. The information is left here for others to use if they wish to take up similar projects.

THE CAN IS NO LONGER AN ACTIVE IDEA



Overview

This page describes the information needed by Field Administrators for the Community Administration Network.

Requirements

Field administrators must meet the following requirements.

Global Registration

Field admins must have a valid global name and login, with valid contact info.

Age

Field admins must be at least 17 years of age, or be approved by the network administrator. Field admins must report there correct age to the administration staff when asked.

Record

Field admins must have a clean record on the master ban list, and not have any outstanding bans or issues on any CAN servers.

Sponsorship and approval

Field administrators must be sponsored by at least one Core Administrator. 3 Field administrators can petition a Core Administrator to sponsor a new field administrator. All new field admins must be approved by the Core Administrators, or the Network Administrator.

Behavior

Field administrators are expected to follow a behavior guideline when playing on CAN member servers.

Follow the Rules

Field admins are expected to follow the same rules as players when playing. Violations of these rules will lead to removal from the administration staff, as well as possible network administrative actions ( bans ).

Be Civil

Field admins are expected to conduct there administration in a calm and civil manner. They should not let anger or personal feelings get in the way of there administration duties, they are expected to not hold any "grudges" against specific users. All discussions, arguments, or disagreement with players over administrative issues should happen in private so they will disrupt the play for others as little as possible. Field admins must remember that it is there job to help all users play the game and have fun.

Give the benefit of the doubt

Field admins are expected to give a user the benefit of the doubt when dealing with an initial violation. Users should always be approached with private chat text to ask them first to stop the behavior that is causing the violation. The admin should explain what the behavior is, why it is a violation, and be willing to help the user resolve the issue to the best of there ability. Field admins are expected to remove bans on users who have spoken with them or other admin staff in a civil manner and have agreed to not repeat there offenses. Users that abuse this will not be given that courtesy a second time.

Use the least necessary action to resolve an issue

Field admins are expected to resolve issues with the "lowest" possible admin action. They should not kick when a silence should work, not ban when a kick would do the same. Bans should be the last resort as they are network wide. Field admins are expected to warn before all actions. The CANAdmin plug-in will track and enforce the warning of people before higher level actions are allowed ( kick and ban ). Field admins are expected to work with all users to resolve any violation issues, and never simply "blow them off". They should refer user to the Core admins if a suitable resolution can not be found.

Use CAN admin abilities only for network violations

All admin actions on servers must be in response to a violation one of the six network rules. No other use of the network admin functions are permitted. The CANAdmin plug-in will require the rule number that is in violation for all actions. Field admins may be granted additional abilities by server owners, and be asked to enforce additional rules. If the Field administrator agrees to this, then they must use the server's local administration system to enforce those additional rules, and not the network system.

Violations of rule 5, the minimum language rules, must violate the very specific conditions set forth in the rule. Interpretations of the rule to include additional language that is not mentioned in the rule, based on personal distaste, or beliefs, are not allowed. Violations of rule 5 must be very clear cut before ban level action is taken. Most users who will skirt the edges of rule 5 will most likely break another rule in the process, usually rule 4. For Simple violations of rule 5 can be handled with a simple net silence command after the required warnings. While annoying, violations of rule 5 have the least affect on the game, and are the simplest to resolve, even for regular users ( everyone can use the silence command ). Field admins are expected to understand that different people have different levels of tolerance for language, and may find things more or less offensive then they personally do.

Administrators that abuse the network admin features for there own personal reasons, will be removed as network administrators, and possibly banned from the network depending on the severity of the actions. All network actions are logged with the BZID of the admin who applied them. If need be the core administrators can remove any and all network actions caused by any administrator.


Administrative actions

Field administrators may take the following administrative actions on any server.

NetWarn

 Usage
 /NetWarn Rule Player Comment

This action will notify the specified player that they are in violation of the specified rule. The warn action will be logged with the central network database. The user will also receive a BZBB PM with the warning and link to the network rules.

NetActivityList

Usage
 /NetActivityList Player

This action will list the history of warnings, kicks, bans, silences, and other admin actions stored for the player across all network servers. Each actionwill list the action, rule violated, the admin, and the comment given at the time of the action. Players have access to a simplified version of this command that will list all the actions for there call sign, but not any others. Server Admins (anyone with an @) also have access to the full version of this command for informational use.

NetSilence

Usage
   /NetSilence Rule Player Comment

This action will block all chat for the specified user on all network services for a period of one hour. The action will also be logged the same way as a warning.

NetKick