AssaultCube Reloaded Master-Server Rules

Preamble

In order to ensure a decent gaming experience for everyone, we have created some rules. These rules can and may change anytime. If you do not like these simple rules, find another master server.

AssaultCube Reloaded, under the command of the AssaultCube Reloaded Task Force, enacts as follows:

Table of Contents

Interpretation

Division 1 — Clients

Prohibited Actions

Voting Actions As Admin Actions on Players (Administrative Actions) Exceptions

Division 2 — Servers

Modifications

Source Code Mods Gameplay Mods Master-Server Functions

Prohibitions

Pushing Maps

Restrictions

Nickname Bans

Division 3 — Auth Users

Abuse

Auth Abuse in General Deban Restrictions Limitations

Division 4 — Administrative Penalties

Clients in Violation Servers in Violation

Interpretation

Division 1 — Clients

In this document,
  1. The “master-server” refers to the official one in operation by this site.
  2. A “server” is software that connects clients, registered on the master-server.
  3. A “client” means someone that is either
    1. playing,
    2. spectating, or
    3. otherwise connected
    on a server connected to the master-server.
  4. An “auth user” is someone that has the privilege on the master-server to gain special access to its servers.

Prohibited Actions

Except as provided in this division, every client, that is connected to any server registered under the master-server shall not do any of the following:
  1. cheat1 in any way that interferes with the gameplay of others;
  2. spam or attempt to spam any server with unsolicited messages.

Voting Actions

Clients shall not abuse the voting functionality of the server.

As Admin

An administrator shall not
  1. veto
    1. a map vote, unless a minimum of 50% of the players have already voted for it,
    2. an administrative vote, unless it is in accordance with section (5), or
    3. any vote that causes advantage to the administrator, or
  2. abuse their privilege in any other way.

Actions on Players (Administrative Actions)

An administrator of a server shall only force an action on a user by
  1. forcing that user to the enemy team, only if
    1. balancing the teams by moving a user from a larger team to a smaller team, where the larger team has at least two players more than the smaller team,
    2. another user is swapped subsequently to switch players,
    3. the server is running a gema map by forcing the users to one team,
    4. the game-mode requires it, or
    5. that user requests it and it is reasonable to do so,
  2. kicking that user, only if that user
    1. does anything mentioned in section (5), (c) to (d), or
    2. uses excessive profanity, and has been warned at least once within the last two minute,
  3. banning that user, only if that user
    1. does anything mentioned in section (5)(d),
    2. reconnects and continues to abuse the server with profanity, if the abuse is done within the same day, for a limit of 20 minutes,
    3. abuses the voting system,
  4. blacklisting, whether temporary or permanently, the user from the server, only if that user
    1. uses cheats, and should optionally report that user to the master-server authority,
    2. does anything that is in violation of the law the master-server is in, or
    3. does anything that is in violation of the law the server is in.

Exceptions

Clients may do the following:
  1. notwithstanding section (2)(a), use cheats
    1. that are fully prevented by the server, and
    2. for the purpose of testing anti-cheat, provided that the server has anti-cheat in development, and not on a production server.
  2. call votes to
    1. perform administrative actions in accordance with section (5), or
    2. perform general actions.

Division 2 — Servers

Modifications

Source Code Mods

All modifications to the source code shall be labelled in the server description.

Gameplay Mods

All gameplay modifications shall
  1. be allowed by the administrators of the master-server,
  2. be labelled clearly in the server description,
  3. have no advantage, unless
    1. that advantage is provided equally to everyone, and
    2. shall run with native code or shall have instructions regarding its usage, and
  4. override the regulation set in section (7) and only be labelled once.

Master-Server Functions

No server shall override the master-server API, including but not limited to the
  1. registration ping,
  2. connect checks, and

Prohibitions

Pushing Maps

Servers are allowed to push maps with its map rotation. This may be changed in the future.

Restrictions

Nickname Bans

A server shall use its nickname blacklist, only to
  1. block profane names,
  2. block clan tags that cause repetitive harm, or
  3. restrict clan tags that the server has agreements with

but shall not use it to

  1. block the use of generic clan tags pursuant to those listed at http://forum.acr.victorz.ca/thread-219.html, or
  2. prevent a large scope of players from connecting2.

Division 3 — Auth Users

Abuse

Auth Abuse in General

Auth users shall not abuse their auth privileges in general3.

Deban Restrictions

Auth users shall not use their deban access to unban themselves from a ban that is given in accordance with this document.

Limitations

Auth users are subjected and restricted to the same limitations as those described in section (4).

Division 4 — Administrative Penalties

Clients in Violation

Any client found to be
  1. in violation of sections (2) to (6), or
  2. using auth in violation of sections (12) to (14)

is subject to these penalties for the

  1. first offence:
    1. an immediate ban of two months that
    2. can be removed upon appeal, immediately,
  2. second offence within one year:
    1. an immediate ban at least six months, but
    2. not exceeding ten months, and that
    3. can be removed upon appeal, after three months has been served,
  3. third offence within two years:
    1. an immediate ban of at least nine months, but
    2. not exceeding three years, and that
    3. can be removed upon appeal, after six months has been served,
  4. where all bans for violations described in section (15)(a)
    1. affect every server connected to the master-server, by barring the client from it,
    2. prevents the client from registering a server on the master-server, and
    3. can be immediately removed if the offence is no longer possible to reproduce, and
  5. where all bans for violations described in section (15)(b)
    1. disable access for auth with the client’s identification and authorization information,
    2. restore the access when the penalty expires, and
    3. can be immediately removed if the offence is no longer possible to reproduce.
  6. In the case that multiple sections apply regarding the penalty, the latter section shall have effect.

Servers in Violation

Any server found to be in violation of sections (7) to (11), shall face the following penalties:
  1. for the first offence:
    1. an immediate ban of two months that
    2. can be removed upon appeal, immediately,
  2. for a second offence within two years:
    1. an immediate ban of one year, but
    2. can be removed upon appeal, after six months has been served,
  3. for a third offence within five years:
    1. an immediate ban of two years, but
    2. can be removed upon appeal, after nine months has been served,
  4. where all bans
    1. prevent the server from registering on the master-server, by barring it, but
    2. does not prevent the banned identifier from playing as a client on other servers.
  5. In the case that multiple sections apply regarding the penalty, the latter section shall have effect.

1 Rank hacks do not qualify as cheating. There is no reason to prevent them; it just displays a number.
2 such as restricting a single vowel from being used in a name
3 They may not even claim privileges with auth without reason