AssaultCube Reloaded Master-Server Rules

1. The “master-server” refers to the official one in operation by AssaultCube Reloaded.
2. A “server” is software that connects clients, registered on the master-server.
3. A “client” means the AssaultCube Reloaded, in an interactive mode, where the person is
   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.

1. provides advantage to that client, or
2. interferes with other clients’ gameplay

unless

3. that cheat is fully prevented by the server, or
4. the cheating is for the purpose of testing anti-cheat, when
   1. the server is labelled with “development” or anything that refers to anti-cheat development,
   2. the cheating is immediately stopped at the request of an admin, and
   3. strictly never on a production server.

1. votes that provide advantage to them,
2. a map vote, unless valid reason exists to do so.

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, when autoteam is disabled,
   4. the game-mode requires it, or
   5. that user requests it and it is reasonable to do so,
2. subduing or kicking that user, only if that user
   1. does anything mentioned in section 3(3), (c) to (d), or
   2. uses excessive profanity and has been warned at least once within the last two minutes,
3. banning that user, only if that user
   1. violates this document regarding client rules,
   2. does anything mentioned in section 3(3)(d),
   3. reconnects and continues to abuse the server with profanity, if the abuse is done within the same day, for a limit of 20 minutes,
   4. abuses the voting system, or
   5. requests it,
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,
   3. does anything that is in violation of the law the server is in, or
   4. any other valid reason is present.

1. provides no advantage, unless provided equally to everyone, and
2. either
   1. runs with native code, or
   2. has instructions regarding its usage.

1. a server description¹, or
2. a message of the day (MOTD),

that advertises any website or service.

1. an AssaultCube Reloaded clan, or
2. a public tournament for AssaultCube Reloaded.

1. block profane names,
2. block clan tags that cause repetitive harm, or
3. restrict clan tags for whom the server has agreements with,

but shall not use it to

4. block the use of generic clan tags pursuant to those listed at http://forum.acr.victorz.ca/thread-219.html, or
5. prevent an unreasonably large scope of players from connecting.

1. registration ping,
2. connect checks, and
3. auth requests and verifications.

1. the server owner,
2. a member of the clan that the server serves, or
3. any person appointed by the server owner to have a password,

is guilty of admin abuse by its operators, and

4. the offence of the client or clients shall be
   1. completely waived and ignored for it/them, and
   2. transferred to the server and considered a server violation.

1. 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,
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. first offence:
   1. an immediate ban of two months that
   2. can be removed upon appeal, immediately,
4. where all bans for violations described in sections 2-3
   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 4
   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.

1. 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,
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 the first offence:
   1. an immediate ban of two months that
   2. can be removed upon appeal, immediately,
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.

1. they deem it is necessary to do so, or
2. there is reasonable cause not defined here,

if

3. at least 60% of them vote, or
4. a public poll succeeds with at least 55%

in favor of that ban.

1. changing his IP address at least twice, or
2. spoofing his GUID,

1. on August 22, 2017, or
2. when a newer version is available,