This wiki is archived and useful information is being migrated to the main bzflag.org website
Editing CommunityAdministrationNetwork/About
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: Archived wiki
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
==Overview== | ==Overview== | ||
− | The Community Administration Network is an independent organization of server owners and administrators who have chosen to group together to provide the best possible play experience to | + | The Community Administration Network is an independent organization of server owners and administrators who have chosen to group together to provide the best possible play experience to bzflag players. |
− | + | ||
− | + | ||
− | + | ||
==Organization== | ==Organization== | ||
The Network is made up of servers whose owners have chosen to provide the network administration staff the ability to manage and enforce a specific set of rules on their servers. | The Network is made up of servers whose owners have chosen to provide the network administration staff the ability to manage and enforce a specific set of rules on their servers. | ||
− | + | The network is made up of the following groups. | |
− | + | ||
− | The network is made up of the following groups | + | |
===Server Owners=== | ===Server Owners=== | ||
− | These are server owner/operators that have chosen to participate in the network. The owners have agreed to the rules for servers and have been accepted into the network. They run the CANAdmin plug-in as part of their server setup | + | These are server owner/operators that have chosen to participate in the network. The owners have agreed to the rules for servers and have been accepted into the network. They run the CANAdmin plug-in as part of their server setup. |
− | ===Field | + | ===Field Administrators=== |
− | These are | + | These are administrators chosen from the community to do the day-to-day administration of network servers. They are normal players that have agreed to the terms and rules for CAN Field Administrators. They use the CANAdmin plug-in on network servers to perform their administration actions. All actions by all administrators are logged by the network for review. |
===Core Administrators=== | ===Core Administrators=== | ||
− | These are a smaller group of administrators that in addition to the abilities of the | + | These are a smaller group of administrators that in addition to the abilities of the Field Administrators, is responsible for arbitrating disputes between players and field administrators and for adding or removing field administrators when needed. The Core administration team is also responsible for approving and reviewing the servers that make up the network. |
===Network Administrator=== | ===Network Administrator=== | ||
− | The network administrator | + | The network administrator is the one person responsible for the entire network. He/she creates the rules to which all other administrators and server owners agree. The network administrator has the power of veto over any action of the other administrators but must provide a reasonable explanation, or face the other administrators abandoning the network (making it pointless). |
==CANAdmin plug-in== | ==CANAdmin plug-in== | ||
− | The network administrators make use of a special plugin that server administrators install to allow network administration. This allows | + | The network administrators make use of a special plugin that server administrators install to allow network administration. This allows admins to apply network wide warnings, kicks, and bans to users that violate the network rules and regulations. The network admins are only able to enforce the network-specific rules on servers and by default do not have any additional administrative permissions or abilities on any server. A server owner may choose to give network administrators additional abilities, but it is not required for network membership. |
==Rules== | ==Rules== | ||
The network has a very specific set of rules that it applies to servers. This rule set is expected to be a small subset of the rules on any one server. CAN Administrators will only enforce these specific rules by default. Every administrative action (warn, kick, and ban) will be logged with the rule number to which the violation applies, as well as any applicable logs or records needed. | The network has a very specific set of rules that it applies to servers. This rule set is expected to be a small subset of the rules on any one server. CAN Administrators will only enforce these specific rules by default. Every administrative action (warn, kick, and ban) will be logged with the rule number to which the violation applies, as well as any applicable logs or records needed. | ||
− | ===1) No Cheating=== | + | ===1) Global Registration=== |
+ | All users must be globally registered and identified to play. This includes spawning and talking. Violations of this rule never have administrative action, as it is automatically enforced by the CANAdmin plug-in (i.e., unregistered players cannot connect to servers using the plug-in, they are automatically rejected). | ||
+ | |||
+ | ===2) No Cheating=== | ||
Users must not use modified clients to gain an unfair advantage over other users. This includes any modification that changes the behavior of a player tank from the release version of the game, or any modification that provides additional information or reaction time to the game. | Users must not use modified clients to gain an unfair advantage over other users. This includes any modification that changes the behavior of a player tank from the release version of the game, or any modification that provides additional information or reaction time to the game. | ||
Examples include (but are not limited to): | Examples include (but are not limited to): | ||
Line 44: | Line 42: | ||
Additional items may be added based on the observations of the administrator. If a user is experiencing network or software problems that may appear to be cheats, then it is up to them to work with the Administration staff and/or the project development to rectify the issue as soon as they are warned. The administration staff will be more then happy to work with the users to determine the cause of any software- or network-related issues. If the issues are network-related and cause the disruption of play with other users, network administrators can request that the user discontinue play on a specific server until such time as network conditions improve. The administrators are expected to speak to the players about the behavior before taking any action to determine its cause. | Additional items may be added based on the observations of the administrator. If a user is experiencing network or software problems that may appear to be cheats, then it is up to them to work with the Administration staff and/or the project development to rectify the issue as soon as they are warned. The administration staff will be more then happy to work with the users to determine the cause of any software- or network-related issues. If the issues are network-related and cause the disruption of play with other users, network administrators can request that the user discontinue play on a specific server until such time as network conditions improve. The administrators are expected to speak to the players about the behavior before taking any action to determine its cause. | ||
− | === | + | ===3) No Exploiting=== |
Users must not use in-game features or flaws to gain an unfair advantage over other players. This includes using game features or bugs to create artificial lag spikes, tweaks or changes to the input system, or the operating system / drivers to create positional discrepancies or speed changes. If the administration staff asks a user to discontinue an action that is causing a problem, the user is expected to refrain from that action. This includes the use of external applications to modify the game's internal state or network data. | Users must not use in-game features or flaws to gain an unfair advantage over other players. This includes using game features or bugs to create artificial lag spikes, tweaks or changes to the input system, or the operating system / drivers to create positional discrepancies or speed changes. If the administration staff asks a user to discontinue an action that is causing a problem, the user is expected to refrain from that action. This includes the use of external applications to modify the game's internal state or network data. | ||
− | === | + | ===4) No Griefing=== |
− | Users must not engage in behavior that is disruptive to the play of the game. This includes actions such as intentional team-killing, intentional | + | Users must not engage in behavior that is disruptive to the play of the game. This includes actions such as intentional team-killing, intentional self-genocide, or capturing the user's own team flag in a CTF game. This also includes message spamming. The administration team does understand that isolated accidents do happen. Users warned of this offense are expected to take care to not repeat the actions. |
− | === | + | ===5) Minimum Language Rules=== |
− | Users are expected to adhere to a set of [[ | + | Users are expected to adhere to a set of [[CommunityAdminstrationNetwork/DisallowedWords|minimum language rules]] that disallows a set of very specific words when using public or team chat channels. Users are also expected to refrain from attacking or making disparaging remarks about other users, race, creed, or beliefs. The in game chat is for chat about the game while playing. Users who are warned for language violations are expected to discontinue use of the offensive language, and continue to play in a civil manner. It should be noted that individual servers can and will have more strict language polices in place that they may administer locally. The minimum language policy applies to user callsigns, and in game e-mail addresses, as well as chat text. |
− | === | + | ===6) No disruption of pubic services=== |
− | Users are expected to not take actions that would disrupt any of the network's or project's public services. This includes any websites or forums, IRC channels, or servers operated by the network itself, or the | + | Users are expected to not take actions that would disrupt any of the network's or project's public services. This includes any websites or forums, IRC channels, or servers operated by the network itself, or the BZFlag project. Actions of this nature are very serious and will not be taken lightly. |
− | BZFlag project. Actions of this nature are very serious and will not be taken lightly. | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
==Common Questions and concerns== | ==Common Questions and concerns== | ||
Line 66: | Line 58: | ||
===Questions=== | ===Questions=== | ||
====Does the network do range bans?==== | ====Does the network do range bans?==== | ||
− | + | All bans are handled by the CANAdmin plug-in and are done based on the BZID of the users. Since a requirement to be a CAN server is to only allow registered users, IP bans of any sort are not needed. | |
===What the Network Is=== | ===What the Network Is=== | ||
Line 72: | Line 64: | ||
====The CAN is a group of people:==== | ====The CAN is a group of people:==== | ||
− | The network consists of people | + | The network consists of people. People that the server owners have chosen to trust to enforce a set of rules. It is run by people for people. People are human. It is assumed that people can and will make mistakes on both sides. Mistakes can be fixed as long as both parties are willing to work at fixing the problem in a civil manner. |
====The CAN is reasonable:==== | ====The CAN is reasonable:==== | ||
Line 82: | Line 74: | ||
====The CAN is a team:==== | ====The CAN is a team:==== | ||
Network administrators work together. Any administrator can work on any problem, regardless of who the issue started with. Administrators are encouraged to work together, with other administrators, and players. | Network administrators work together. Any administrator can work on any problem, regardless of who the issue started with. Administrators are encouraged to work together, with other administrators, and players. | ||
− | |||
− | |||
− | |||
===What the network is not=== | ===What the network is not=== | ||
====The CAN is not your mom==== | ====The CAN is not your mom==== | ||
− | The network does not exist to arbitrate small disagreements in playstyle or behavior. It will not make Billy stop touching your flag. It does not exist to decide what is or isn't fair in games. The rules that the network enforces have nothing to do with gameplay or any specific game ruleset. The CAN will not and | + | The network does not exist to arbitrate small disagreements in playstyle or behavior. It will not make Billy stop touching your flag. It does not exist to decide what is or isn't fair in games. The rules that the network enforces have nothing to do with gameplay or any specific game ruleset. The CAN will not and can not do such actions as resetting flags, balancing teams, or changing server variables. |
====The CAN does not take over a server.==== | ====The CAN does not take over a server.==== | ||
Line 101: | Line 90: | ||
== See Also== | == See Also== | ||
− | + | [[CommunityAdminstrationNetwork/Server Owners]] | |
− | + | ||
− | + | [[CommunityAdminstrationNetwork/Field Administrators]] | |
− | + | ||
− | + | [[CommunityAdminstrationNetwork/Core Administrators]] | |
+ | |||
+ | [[CommunityAdminstrationNetwork/Players]] | ||
+ | |||
+ | [[CommunityAdminstrationNetwork/CANAdmin Plug-In]] |