Thread: m_clantag
View Single Post
Re: m_clantag
Old
  (#2)
botmeister
Ex-Council Member
 
botmeister's Avatar
 
Status: Offline
Posts: 1,090
Join Date: Nov 2003
Location: Canada
Default Re: m_clantag - 23-09-2005

Did you correctly set m_enforceclanteam on?

m_enforceclanteam on te

In hindsight, the command should be changed since there's really no need to specify "on", but that's the way it is at the momemt.

Also "od" may match up names that are not part of the clan, so I'd specify at least "od-".

Here are all the commands you need to have a look at:

m_enforceclanteam [ on < te | ct > | off ]
Non clan members who are on the designated clan team, and clan members
who are not on the designated clan team, will get blown up automatically
at start of each round. A private message will be displayed telling
the person they are on the wrong team, and how to switch teams.
default minimum access level: clan member

m_clantag <"clantag">
If you set this CVAR to match your clan tag and turn on
m_enforceclanteam, players who have the matching clan tag
in their name will be forced to play on the specified team.
All other players will have to switch to the opposing team.
This CVAR corrects the problem of not having all clan
members registered in the user.cfg file. To disable, simply
set the m_clantag to an empty string "".

NOTE: the clan tag cvar is not case sensitive.

examples: m_clantag "[mean][mf]"

m_allowonclanteam < userid > [ yes | no ]
Allows non clan member to join the clan team when m_enforceclanteam
is on.
default minimum access level: clan member

m_allowoffclanteam < userid > [ yes | no ]
Allows clan member to join the opposing team when m_enforceclanteam
is on.
default minimum access level: clan member


Maker of the (mEAn) Bot.Admin Manager

"In theory, there is no difference between theory and practice. But, in practice, there is." - Jan L.A. van de Snepscheut
  
Reply With Quote