
What are
"[TiC]Clan's RCON GUIDELINES" for:
Non-members, Screened
Appllicants, Guests, non-Rconing Members:
PLEASE
read ALL of these guidelines BEFORE you open
your mouth or type ANYTHING about a [TiC]Clan
Server any where if you want to stay out of trouble.
[TiC]Clan Rconers:
The purpose of the MiGHTY [TiC]Clan's "Rcon
Guidelines" are to set a "STANDARD
POLICY" for [TiC] Rconers.
[TiC] Rconers are the specially selected
group of Members of the [TiC]Clan that have
been chosen to and trusted with a "Rcon
Password(s)" (aka "rcon access"
or Admin-Mod access) to a [TiC]Clan game
server, because of an endless stream of work
and loyalty given to the Clan by them. We
call these people "Rconers".
These guidelines are to ensure that --ALL-- [TiC]Clan
Rconers globally administrate --ALL--
of the [TiC] game servers in a professional
and organized way. To ensure consistency in
server operation and in server's settings in
all of [TiC]Clan's game servers.
Note, not all Rconers have rcon access to
every [TiC] server.
[TiC]Clan "SERVER OWNERS":
The [TiC] Rcon Guidelines are NOT for our
Server Owner. Server Owners are what we call
the people that own the servers (or work at
the place that owns the servers). They
volunteer to operate their server for us.
Server Owners may or may not be in our clan,
they might even be in another clan.
The Rcon Guidelines are NOT for when Server
Owners are "tweaking" their own
servers (as needed for bandwidth,
performance, etc or for other personal
preferences). A Server Owner can rcon THEIR
own server how they like, our Rcon Guidelines
are pretty fair, and since our Server Owners
are usually pretty fair people, they follow
our Rcon Guidelines VOLUNTARILY on their
server.
However, if a Server Owner has been issued
the rcon password to another [TiC] Server
Owner's server, they will have to follow the
[TiC] Rcon Guidelines -WHILE- they are
rconing that other Server Owner's [TiC]
server. If 2 Server Owners were working
together with one another's permission to
'tweak' one of their servers, then the Rcon
Guideline's limited "Allowed Rcon
Commands" list would not apply while
they are "tweaking".
If a Server Owner is not in the [TiC]Clan, we
still respect their input on any server
issue, and they are generally treated as if
they ARE a part of the MiGHTY [TiC]Clan
Family (however, [TiC] Secret RW channels/pages
still require a Screened Applicant Interview,
GUEST QUIZ, or a [TiC] Membership
respectively).
[TiC]Clan's Rconing
Guidelines:
Guidelines for RCONing
on [TiC] Clan's Servers
|
| # |
RULE |
Date
Changed |
| 1. |
We do --NOT-- MAKE CHANGES
FOR OTHER PEOPLE:
The [TiC]Clan family does --NOT-- make changes to our
servers for other people.
So "Kids", don't even bother
asking us to change the gravity, change
the map, change the class limit, turn off
friendly fire, etc, etc.
Sorry, we will NOT change our servers for
you.
Our servers are for OUR Club, sorry. ;-)
|
7oct00 |
| 2. |
Do --NOT-- bother the [TiC]Clan
"Servers Owners".
If a [TiC] Member needs something changed on a [TiC] server,
simply post
your "suggestion" on the [TiC] Forum,
do --NOT-- contact a [TiC] Server Owner directly.
If you need a "Rconer" for
an [TiC] Event, post your request for an
[TiC] "Rconer" on the [TiC]
Forum with the Event's type, time, and
date.
Non-members,
Screened Applicants, Guests, and non-Rconing
Members do -NOT- ask/bug/contact
Server Owners to make changes on their
servers, that is the job/
responsibility of the "[TiC] Rconers"
to do the DAILY RCONing and to act as
liaisons for our Server Owners to the
rest of the World. If you want to stay
out of trouble follow this Rule.
Even
[TiC] Rconer's need to post their
individual server suggestions on the
Forum for approval.
The Server Owners are busy and are not to
be bothered. If you have an idea for a
major server change (i.e.. map cycle, map rotation
change, game change, adding or
subtracting a map, other server
adjustment, more "allowed commands",
etc, (that you think would greatly help
the [TiC]Clan), simply post your
suggestion / request on the [TiC]Clan
Forum.
Once your "server suggestion"
is posted on the [TiC] Forum (this allows -ALL- the [TiC]
Members a chance to offer their "opinion"
on that topic), the
Council Members will
approve or disapprove it and possibly
delegate a [TiC] Rconer to contact the
Server Owner to make any approved changes.
|
24sep01 |
| 3. |
Do NOT bother asking anyone
for the Rcon Password to a [TiC] server.
The Server Owners and [TiC] Rconers will
simply send you to the [TiC] Council Members. (where
they
will commence to give you a royal BuTT
chewing). Members and NON-members do NOT
ask [TiC] Server Owners for the rcon
password, PERIOD !
The RCON passwords are an "earned right" here in the [TiC]Clan
that requires a major commitment and
major work contribution to the [TiC]Clan
and are ISSUED by the [TiC] COUNCIL.
If the [TiC] Council see that you fit
these requirement, THEY will contact you.
If you think you have a --NEED-- or
deserve a rcon password, contact a [TiC] Council Member,
not the Server Owners if you want to stay
out of a lot of trouble.
|
7oct00 |
| 4. |
Always respect the wishes of
the individual Server Owner.
Some Server Owners have *SPECIAL*
server settings and server rules, follow
them as long as they are legal above the
[TiC]Clan's Server Guidelines. If a
Server Owners becomes way "off base"
from the basic [TiC]Clan philosophy
we will disassociate ourselves from that
server and post a message on the [TiC]
Forum informing everyone.
|
10may01 |
| 5. |
To have a rcon password to a
[TiC] server is a "JOB" -AND- a
"RESPONSIBILITY".
Make sure YOU take the time to rcon to
fix any "problems" you see
while on a server. If someone is on [TiC]
RW and needs a "slot" on a [TiC]
server (that you are currently playing on),
take the time to do the job of rcon and
open a slot on the server. If you see a
troublemaker, take YOUR time to warn,
kick, ban. Take the required actions to
keep the teams evens. If you see a
violation of our RULES, correct them.
Rconers
are REQUIRED to spend some time helping
advertise [TiC] Servers and occasionally
volunteering to rcon for [TiC] Events.
There are sets of "Rconer message
binds", that are available and have
the handy "NO cussing, NO spamming,
NO etc" bind, "[TiC] wants to
play CT" bind, etc, etc. Rconers can
get a copy of these binds from looking at
[TiC]EVIL's
TFC Scripts Set.
You do not have to use those rcon binds. You can change
those binds as needed. If you don't want to use binds at
all, you could simply do a lot of typing.
|
24aug01 |
| 6. |
ALWAYS lead and RCON by
example, ALWAYS.
People should always treat everyone
inside and outside our Club the way they
would want to be treated.
Troublemakers should be WARNED. If they
continue to break rules, they should be
KICKED. If they then continue to break
rules, they should be BAN (or LIMITED BAN). There are
other special punishments allowed too (see Effective
Punishments below).
Always take the time to ask the
individual "by name" to please
reframe from conduct that is unacceptable
on a [TiC] server.
Sometimes it is very hard to be fair to a
new violator, after you have dealt with
three or four bonehead cretin
troublemakers in a row. Especially, if
the other troublemakers were more
disrespectful after being warned and
insulted you or the clan. Rconing will
test anyone's patience, we all are only
human.
Dealing with people from all parts of the world and all
different religions sometimes demands tact and patience.
What you might find offense, may be slang or joking to
them. Their statement might have been jokingly directed
toward one of their buddies on the server that
understands the statement completely.
|
13apr03 |
| 7. |
EFFECTIVE FAIR PUNISHMENTS:
LLAMIFICATION OF MINOR MOUTHY BRATS ALLOWED:
Sometimes there are not many people online and a troublemaker on the server will start to mouth off. Usually, following the warn, kick, ban guidelines, these brats would end up banned, but because the rconer might want some "bodies" on the server to play against, we grant the rconer the option of "llamafing" the troublemaker (if the server has admin_mod). This will mute the troublemaker's big mouth. If troublemaker had been TKing or what not
too, we would recommend following the "warn, kick ban"
procedure instead. "llamafing" is an option to out right banning "mouthy" troublemakers that warrant being ban. "llamafing" carries the same weight as a "ban", so record the Wonid, IP, game name and reason for this action. We do not un-llamify, although a "llamification" seems to "wear off" with time.
Once the server fills up, if you then want to ban the
llamified brat, it would be ok.
SLAYING TEAMSHOOTERS:
Sometimes troublemakers come on our servers simply to be
nasty and cause trouble as we are a very old Club that
is high profile and World Famous, and everyone knows
they can still find us at
www.ticclan.com no
matter how long they have been away. Sometimes there are
random brats that also show up from time to time.
It is very important to consistently let little jerks
know that we do not allow asinine behavior on our servers
at any time. A common ploy of brats is to purposely
shoot their teammates leaving respawn, then say
"Oh, I am sorry", when it is obvious that they did it on
purpose. If someone does this, immediately slay them (or
"warn, kick, ban", but do not argue with them).
If someone honestly does teamshoot or TKs someone, and
apologizes, then no punishment should be warranted. If
anyone teamshoots leaving respawn, you should instantly
slay them if you believe it was done purposely, no
matter if they answer you with a lie (you also have the
option of "warn, kick, ban). Anyone accidentally
teamshooting or TKing should of course quickly apologize to
their victim and say they are sorry.
NASTY PLAYER NAMES MUST BE CORRECTED IMMEDIATELY:
If someone gets on the server with a cussword in their
game name, ask them to change their name immediately,
because, if that person plays long enough on one of our
servers with Stats page, their nasty name will show up
on that server's stats page (if they get rated). So
their name must be changed immediately. If they won't
change their name, then "llamify" them then "unllamafy"
them (you could of course use the warn, kick, ban
procedure). This will change their name to "NotALlama".
If they ask, tell them no cussing is allowed on the
server. If they change their name to a cussword after
that, you can kick or ban them as you see needed. You
could also simply ask them to change their name
initially and if they refused, kick or ban them as you
see needed. We have an extensive anti-cussword feature
on most of our servers that catch most cusswords. If you
notice troublemakers using a word that you think should
be added to the cussword list, post it in the [TiC]
Private forum with an explanation with the exact
spelling of the word. We have most of them covered, but
not even the [TiC]Clan is perfect.
;-)
LIMITED BANS ARE ALLOWED:
[TiC] Rconers will be granted
the option of possibly giving a "LIMITED
BAN" to "REPEAT MINOR Offenders".
If someone, possibly a "newbie"
or "Player", repeatedly commits
some "minor infraction" (say
like they will not even the teams
repeatedly) after warning and kicking,
but is not nasty or smart mouthed about
it, the [TiC] Rconer can individually
decide to give him only a "LIMITED
BAN" of 2000 minutes (appox. 1 1/2
days), or may still choose to PERMANENTLY
ban the offender.
"LIMITED BANS" should only be
issued if a PERMANENT BAN was warranted.
Do not forget to record their WONID, game
name, and why they were ban (just like
you would for a permanent ban).
PLEASE USE "WARN, KICK, BAN":
Rconers should always follow the "WARN",
"KICK", "BAN" (or
"LIMITED BAN") sequence of
steps. Really nasty rude or blatantly ignorant behavior
can grant instant permanent bans If the Rconer decides
that they simply was not going to be able to correct the
troublemaker's bad behavior with "warn, kick ban".
BAN ANYONE INSULTING [TiC]:
Insulting a known [TiC] Rconer or the [TiC]Clan is one of the very few reasons to
instantly ban someone without any warning if a [TiC]
Rcon so chooses, also a llamification would be allowed.
Anyone knowingly insulting a [TiC] Rconer is similar to
spitting on a Cop, it will not be allowed on a [TiC]
Server at anytime without a quick response. We don't
allow idiots that show up on our server simply to harass
us or our friends in an attempt to hurt our Club or the
friends of the [TiC] Clan on our own servers. We have to
put up with too much crap in the generally unclean
public forums and servers and simply have ZERO tolerance
for it on our own servers.
BAN BY WONIDs, SAVE THEIR DATA:
When an individual has been
banned, their WON identification number
and "why they were ban" (and
their IP# if available) and date needs to be recorded
and posted on the "[TiC]Banned List" Forum with any
other details you have. ONLY
BAN by WONID in Half-life, NOT by "game name".
The reason "why" is someone can
simply change their name and re-join if
they were ban by their game name. The reason we
record the IP number is it could uncover a trail to
other bad behavior in other areas, also some hackers
have multiple CD keys or WONIDs.
|
13apr03 |
| 8. |
ACCEPTABLE RCON COMMANDS: Do NOT change maps in the middle
of a game, UNLESS you are going to have an Event on that
server, because it is generally annoying to the other people currently playing on that map.
"mapvote" is enabled on some of our servers. Usually the
ratio of people needed to vote for a map in order for it
to change is set rather high, usually 80% or more people
on the server have to vote for that map before it
changes.
"votekick" is enabled on some of our servers. Usually
the ratio of people needed to votekick a troublemaker
off a server is set rather high, usually 80% or more
people on the server have to vote for that map before it
changes.
Any acceptable changes * (see
the "Allowed Rcon Commands"
section on this page) one makes to the
server should be restored to their
original configuration before leaving the
said server.
If you TEMPORARILY "USER Password"
(rcon sv_password) a server for an Event, Class, or
Match,
make SURE that you are there to UN-USER-password
it, at the end of that Event, etc. If you
"user-password" a server, make sure you ICQ or EMAIL the
"user password" to the Server Owner and ALL the other
[TiC] Rconers or post a message in the [TiC] Private
Forum. You would preferably do this ahead of
time. Make the user passwords VERY easy
non-rhyming, all "lower case" words, as it
will be easy to tell people the password verbally over
the RW channel, (using simple color names like "black",
"red", "green", etc, etc are good examples of simple
passwords).
If you TEMPORARILY enable "pausablity"
(rcon pausable 1) on a server for an
Event, make SURE that you TELL the people
that are on the server that you will be
pausing the server sometimes for 2-5
minutes during the training class. Make
sure you disable pausablity (rcon
pausable 0) at the end of that Event. There is a message
bind at
TFC Script Set that lists has this message.
See the complete list of "acceptable commands" listed
below in "Allowed [TiC]
Rcon Commands" list.
|
13apr03 |
| 9. |
Rconers, do NOT mess with any
other server settings other than the
"Allowed Rcon Commands",
EVEN IF YOU COULD with RCON. [TiC]
servers are are only "tweaked"
by their Server Owner. Do NOT experiment
on [TiC]Clan servers, only the "Server
Owners/ hosters" will do that . This
will ensure that the servers are always
running and always consistent. If you
want to experiment, simply create a
server on your own computer.
EXAMPLE:
Do NOT change gravity, do not change max
players, do not change min and max rate,
do not change map cycle, etc, etc. You
can call up a special map that might be
on the server but not in it's server
rotation for a Clan Event thought.
|
24aug00 |
| 10. |
If you ABUSE the RCON POWERS,
you WILL have the rcon power --STRIPPED-
away from you, ALWAYS REMEMBER THAT.
|
7oct00 |
ALLOWED* [TiC]
RCON COMMANDS:
The "Allowed
Rcon Commands" (--OR--- EQUIVALENT
Admin_Mod Commands) that OUR selected Members
(Rconers) will limit themselves to and use,
are as follows:
rcon_address,
rcon_port, rcon_password, rcon say, rcon
changelevel, rcon map, rcon users, rcon status, rcon sv_password, rcon
sv_password "none", rcon
pausable 1, rcon pausable 0, pause, rcon
kick, rcon banid 0 kick, rcon banid 2000
kick, rcon writeid, rcon removeid (only remove
auto-bans).
EQUIVALENT ADMIN_MOD COMMANDS:
admin_say, admin_map, admin_userlist,
admin_pass, admin_nopass, admin_pause,
admin_unpause, admin_t, admin_ct,
admin_kick, admin_ban 0, admin_ban 2000,
admin_llama, admin_unllama, admin_slay, admin_rcon (but only the rcon above
commands).
ALLOWED*
[TiC] RCON COMMANDS EXAMPLES:
|
| RCON |
ADMIN_MOD
|
rcon_address insert
server IP number
rcon_address
208.45.95.202
|
n/a |
rcon_port insert
server port number
rcon_port
27016
|
n/a |
rcon_password
insert rcon password
rcon_password
eviltest
|
setinfo "pw-admin"
"insert password"
setinfo "pw-admin"
"eviltest"
|
rcon say insert your
message
rcon
say STOP doing that
|
admin_say insert your
message
admin_say STOP
doing that
|
rcon
changelevel insert map name
rcon
changelevel 2fort
rcon changelevel de_dust
|
admin_map insert map
name
admin_map
2fort
admin_map de_dust
|
rcon map insert map
name
rcon
map 2fort
|
admin_rcon
map insert
map name
admin_rcon
map 2fort
|
rcon users
rcon
users
|
admin_userlist
admin_userlist
|
rcon status
rcon
status
|
admin_rcon status
admin_rcon status
|
rcon
sv_password insert player password
rcon
sv_password black
|
admin_pass insert
player password
admin_pass black
|
rcon
sv_password "none"
rcon
sv_password "none"
|
admin_nopass
admin_nopass
|
rcon pausable
1
rcon
pausable 1
|
admin_pause
admin_pause
|
rcon pausable
0
rcon
pausable 0
|
admin_unpause
admin_unpause
|
rcon kick # insert
user's number
rcon
kick # 235
rcon kick exact game
name
rcon
kick Player
|
admin_kick exact game
name
admin_kick Player
admin_rcon kick # insert
user's number
admin_rcon kick #
235
|
rcon banid 0 insert UIN kick
rcon
banid 0 123456 kick
|
admin_ban insert UIN 0
admin_ban 123456 0
|
rcon banid
2000 insert UIN kick
rcon
banid 2000 123456 kick
|
admin_ban insert UIN 2000
admin_ban 123456
2000
|
rcon writeid
rcon
writeid
|
admin_rcon writeid
admin_rcon writeid
|
rcon removeid
insert
UIN
rcon
removeid 123456
|
admin_unban insert UIN
admin_unban 123456
|
| n/a |
admin_t insert
user's name
admin_t Player
admin_t insert UIN
admin_t 123456
|
| n/a |
admin_ct insert
user's name
admin_ct Player
admin_ct insert UIN
admin_ct 123456
|
| n/a |
admin_llama insert
player UIN
admin_llama
1234567
|
| n/a |
admin_unllama insert
player UIN
admin_unllama
1234567
|
| n/a |
admin_slay insert
player UIN
admin_slay
1234567
|
| n/a |
admin_rcon insert
allowed rcon command
admin_rcon kick #
235
admin_rcon map 2fort
admin_rcon status
|
HANDY LINKS:
This page was
originally created 7 Sept, 00 by
[TiC]EVIL. Last updated 04/27/03.
|