Rules on servers

Rules for players


In short: play nice. That's all. We playing for fun.


  • You can lucispam, pulsespam, blasterspam, tyrant maul spam…
  • You can camp or jetcamp.
  • You can trap an egg with turrets or teslas, or a telenode with acid or hives so long as there remains another untrapped spawn point.
  • You can kill your own team's spawns so long as there remains another untrapped spawn point.
  • You can speak in your own language if you like.
  • You can be a battle-granger, but you should expect to be team-killed often.
  • In other words - you can play freely.

  • You can't cheat – ban.
  • You can't destroy your own base on purpose – ban.
  • You can't teamkill on purpose (when teamkilled player does not agree with that) – ban.
  • You can't use bugs which will cause an imbalance or complete invulnerability of either team – ban.
  • You can't repeatedly abuse on purpose (swearing, vote or bind spam, blocking, teambleeding…) – ban.
  • You must not call a draw when one team is winning or there is still obvious game progress ‒ warn → kick → ban.
  • In other words - you can't be an idiot.

Advice for players

  • You should use teamchat to co-ordinate base moves, attacks etc. Particularly so if you're wanting to move the reactor or the overmind since not informing other players may cause complaints, leading to investigation by admin.
  • Problems with a player? Try talking privately (/m name message) or use teamchat.
  • If there's a serious problem, tell admin. Use public chat or admin chat (/a message).
  • If there's no admin around and you have a deconner to report, you have a few options:
    • Screenshot. Take a snapshot (with the console open; scroll it if needed) and post that. (It is recommended that you crop the image; no point in posting a 1920×1080 screenshot when only the left-hand side is needed.)
    • /condump file – this will create a file in ~/.tremulous/base/ (1.1) or ~/.tremulous/gpp/ (1.2) (on Linux, Mac and similar). Edit that and post it. If you're a junior admin, you should also include /namelog output in the console dump.

Rules for admins


You can be admin only on one server.


Basic ban duration:
  • Deconner: !ban nick 10d
  • Aimbot/wallhack: !ban 30d
  • Others: !kick or small !ban duration (hours, days)

Be tolerant. Use admin commands only if you make sure and it's a necessary case. We don't want admins who command other players and kick them for bad reasons.
The fact you are an admin doesn't mean that you're more important than regular players: you only have a broom with which to sweep up any mess. If you leave the mess, it's your problem; consider that if you want to become admin.


Don't trust players (mainly those with level 0 or 1) who shout "He is deconner, teamkiller, ban him!" if you don't see it yourself. If somebody does what he shouldn't, follow him and make sure he's doing it on purpose, he wants to ruin the game (match) and it wasn't a mistake. Sometimes it's a strategic choice for the team to destroy a spawn or deconstruct a few things. Sometimes it's fun to team kill with someone who agrees.


Admins can see team chat as spectator. So you can see "Moving OM, OM deconstructed". It's unacceptable to join to the other team and tell them "OM down" and begin attacking. You can join but you cannot attack until the overmind is up (or you've left enough time for it to be up).


Admins can switch teams without loss of credits or evos.


Admins can join a team with more players. They mustn't use it to choose a team but only for solving problems, and must leave when the problem is solved (or found to be insoluble). Admin must otherwise join teams in the same way as other players: the team with fewer players, if there is one, else either team.


Admins have an unlimited number of votes. Other players are limited because of vote-spamming. We suppose that admins aren't idiots and won't spam.


You can't call votes for changing or restarting the map after first 5 minutes of a map.


Some command restrictions


In 1.1, commands are prefixed with "!"; in 1.2, they are prefixed with "/".

kick
Mostly used by those who don't have ban.
ban

Use bans with reason (Write reason clearly for players. They doesn't have to know what TB means). You can use '!ban slotnumber' or '!ban nick' or '!ban xxx.xxx.xxx.xxx'. If the player will disconnect, you have to use IP ban. !namelog shows player's IP but if you'll wait to the next game, it will be impossible to ban him.


You can ban only verified deconners, teamkillers, cheaters and repeatedly warned players, that annoy somehow.


A deconner is a player who's destroying his base. Human: grenade in base, deconstructing buildings or using a weapon (typically lucifer cannon, pulse rifle or painsaw) to destroy buildings, typically telenodes or the reactor. Alien: destroying or deconstructing buildings, typically eggs or the overmind.


If you see <player> DECONSTRUCTED reactor then, soon afterwards, <player> disconnected in the console, ban him without verifying. Do the same if you see 5 buildables were DESTROYED by <player> then <player> disconnected.


Sometimes, someone destroys a few things by mistake. It can happen that someone throws a grenade into his base by mistake or that he needs to destroy something because it's blocking him. The same in case of teamkilling – if the killed player wants revenge, then it may be that you can't find out who began to team kill on purpose.


So: mistake or obscurity of the case = no BAN, no REVERT.


If someone's shooting to his team mates, warn him. He can be angry (because of anything), but after warning will calm down. If he won't stop, kick him or ban.


Players with level 3+ can't be banned. If such player is deconner, you have to use !setlevel <player> 1.


If you're not sure, do nothing.


[1.1 only] If you want to prevent a problem, use !ffboff. Nobody can team-kill anyone, destroy their own base or deconstruct, so you can find out what's happened; and after solving use !ffon.


[1.2 only] If you want to prevent or rectify a problem, use /pause. The game is now paused; you can examine the build log or the console log and issue commands to try to put things right. Use /pause again to resume the game.


Be careful: players can rename themselves and switch teams. If someone changes name, it may mean that he wants to decon (name change won't help him anyway). The same in case of changing teams.


If you want to ban an aimbotter, record a demo first and mainly ban only CLEAR cases of aimbotters. Don't ban anyone who only looks like aimbotter.


The most common way to ban:

  1. Something has happened: you can see that someone destroyed half of his base, he's deconning a lot of things and someone shouts 'deconner' and/or 'teamkiller'.
  2. !ffboff (only 1.1)
  3. Follow the problem player and you'll find out if it's on purpose or not. And if it's on purpose, you can finish it by ban. If it's happening in the other team, you have to leave your team (if you're not just spectating).
  4. !ffon (only 1.1)
lockall and unlockall
If someone do a mess, you can't ban him and he's repeatedly coming back, lock both teams, until he's bored. Move new players to teams they have chosen.
lock
If one team doesn't have spawns and neither team is strong enough to win, lock the team without spawns. Other players can join the other team, create an advantage and finish the game. Don't use automatically! Sometimes even the team without spawns can win.
putteam
This serves to move players to locked teams, move yourself to balance teams or investigate a problem, or move a player to spectators if the game can't be finished.
mute
If someone spams a lot of rubbish to chat or he's abusing too much. One more time: If too much! Not once, twice or 10 times, but only if it's repeated and too much. Be prepared: he may begin to decon after mute.
ffoff and ffon (only 1.1)

Disables killing of team mates, destroying of own buildings and deconning.

To be used if something bad is happening or you can't find out who's doing it. Since ffoff is turned on, players practically can't do anything bad. It's good for investigation or finishing game without risk.

It's also good if you're watching human base, nowhere any alien and you suddenty hear a grenade being dropped ⇒ ffoff, find the player that wanted to damage the base, find out if it wasn't by mistake and if wasn't → ban. Don't forget that after using this command, players are unable to decon anything! If you don't use it in SD, then don't forget to turn it on by ffon if there is no danger.

ffboff (only 1.1)

Like ffoff, but while you can kill team-mates, you can't destroy buildings. Decon is disabled too. It can be used if you see that someone is killing team-mates but you are not sure who; so to prevent following decon, which is likely to be the next step.

It's better to let a few players be team-killed to idetify the offending player than let him decon a whole base or let him get away with the team-killing.

cancelvote
Use it to cancel absurd or undue votes (teamkill kick vote if someone killed someone by mistake, luci spam etc.). It's also to cancel a change-map vote which was repeated because the first one failed.
warn (only 1.1)
To warn players before planned ban or mute. Write clearly the reason: not TK or TB but STOP TEAMKILL and STOP TEAMBLEED.
allready
Use if players are quietly waiting for the next game.
revert

It's good to repair claims after a deconner. Use this along with a ban to restore what the deconner removed.

If I throw a grenade to the floor by mistake, I can't revert it. Why? Because I just made a mistake; it's part of the game.

spec999

This command is not for arbitrarily moving players with ping 999 to spectators. It's to move a player with ping 999 if the player is blocking something (the end of game, way, etc).

Such high ping is often a temporary situation; moving a player who's still even a little bit responsive isn't nice – he won't be happy if he loses tyrant and 9 evos because you've just moved him to spectators.

rename
Use to change players' offensive/bad names.
restart and map
Use if the game cannot be finished (bug build, tyrant without eggs vs. last human camping in a small hole etc.).
buildlog

Use this to find out if there's a deconner (if you don't have other evidence), what he's destroyed (ditto) and what log entry number to use with revert.

buildlog h shows only human buildings; buildlog a shows only alien buildings; and buildlog 10 shows build log entries 10 to 29.

It's not for checking whether you really sniped that armoury.

Admin commands are not to command other players, act macho and show others everything you can. Admin commands are here to keep tidiness on server.