468x60 Ads

1. Features

Mani admin plugin is an administration plugin for Counter Strike Source servers. It has many features most of them set in one cfg file called mani_server.cfg :

manage adverts
manage tem killing
manage player and weapon stats
manage reserverd slots
manage high ping kicker
manage admin messages
chat flooding control
auto team balance
voting functionality
and many others..

2. Installing Mani admin plugin

In order to install this administration plugin, download the Mani admin pluginn installer here and unzipp it anywhere on disk.

Run the installer and select as installation directory, the main folder of your server (if you have installed the server using our tutorial, the main folder should be called SRCDS )

The installer will set the plugin up for your server. Then go to SRCDS\cstrike\addons\metamod and open metaplugins.ini using Wordpad or Notepad. Add there this line:


3. Configuring Mani admin plugin

The core file of the plugin is called mani_server.cfg and you can find it in SRCDS\cstrike\cfg . This file is used to turn on/off functionality and to also config options within the plugin. By default the main functions are turned off. For the most part the on/off switch is usually the first cvar under each module (i.e mani_adverts, mani_stats, etc).

In order for this config to be used by the plugin an exec command must be placed in the server.cfg file within the SRCDS\cstrike\cfg folder. Add there a line like this : exec mani_server.cfg

Now you can open the mani_server.cfg and configure it as you like.

3. Adding admins in Mani admin plugin

In order to add admins you will have to create a text file in SRCDS\cstrike\cfg\mani_admin_plugin and save it as adminlist.txt . Then copy these lines into it:

// Add your IP's Steam addresses, Names and Passwords
// in this file for admins
// e.g STEAM_0:0:21233123
// THOSE OPTIONS UNLESS YOU HAVE mani_reverse_admin_flags set to 1
// in your autoexec.cfg
// Restriction options are :-
// k = restrict admin from kicking players
// r = restrict admin from executing rcon commands via ma_rcon
// q = restrict admin from executing rcon commands from the menu
// e = restrict admin from the adminexplode command
// m = restrict admin from slaying players
// b = restrict admin from banning players
// s = restrict admin from running ma_say
// o = restrict admin from running ma_chat
// a = restrict admin from running ma_psay
// c = restrict admin from changing maps
// p = restrict admin from playing sounds
// w = restrict admin from restricting weapons
// z = restrict admin from plug-in config menu
// x = restrict admin from running admincexec commands
// y = restrict admin from running admincexec from the menu
// i = restrict admin from running blind commands
// l = restrict admin from running slap commands
// f = restrict admin from running freeze commands
// t = restrict admin from running teleport commands
// d = restrict admin from running drug commands
// g = restrict admin from running ma_teamswap and ma_balance commands
// j = restrict admin from running gimp commands
// R = restrict admin from running rcon vote
// v = restrict admin from running random vote map
// V = restrict admin from running vote map
// Q = restrict admin from running question vote
// C = restrict admin from running Cancel Vote
// A = restrict admin from being able to accept/refuse a vote they started
// B = restrict admin from running a menu rcon vote
// D = restrict admin from running a question menu vote
// E = restrict admin from using ma_rates
// F = restrict admin from running burn commands
// G = restrict admin from running noclip command
// H = restrict admin from running ma_war command
// I = restrict admin from running ma_mute command
// J = restrict admin from resetting all the player ranks
// K = restrict admin from setting player cash
// L = restrict admin from using rconsay commands setup as type R in commandlist.txt
// M = restrict admin from having custom skins to choose
// N = restrict admin from being able to set a players skin
// O = restrict admin from running ma_dropc4 command
// P = restrict admin from running ma_setadminflag command
// T = restrict admin from running ma_timebomb command
// U = restrict admin from running ma_firebomb command
// W = restrict admin from running ma_freezebomb command
// X = restrict admin from running ma_sethealth and derived commands
// Y = restrict admin from running ma_beacon command
// S = restrict admin from running ma_setcolour or ma_setcolor
// Z = restrict admin from running ma_give and ma_giveammo
// p = restrict admin from running ma_spray 
// An example would be if you wanted to prevent admin
// with steam id STEAM_0:0:2388333
// from being able to play sounds and rcon command
// STEAM_0:0:2388333 rp   // Admin can't rcon and play sound !!
// Another example
// STEAM_0:0:3389333 kmc  // Admin can't kick, slay or change maps
// You can also use admin groups instead of flags, you setup admin groups
// in the admingroups.txt file then use them in this file.
// For example if you setup a group called "Clan Member" and "Kick Only" you would set it per
// player like this:- 
// STEAM_0:0:1234234 Clan Member // Fred
// STEAM_0:0:234884 Kick Only // Jim
// If you wanted an admin to be created by IP Address you 
// set your entry to be in the format
// ;IP Address flag
// Example
// ; rp // Admin can't rcon and play sound !!
// ; kmc // Admin can't kick, slay or change maps
// If you want to have an Admin created by both steam ID and IP address you
// use the format STEAM_ID;IP_ADDRESS flags
// Example
// STEAM_0:1:877489; rp // Admin can't rcon and play sound !!
// If you only use an IP Address, the character ';' MUST be directly in
// front of it.
// There must be a space between the steam ID/IP Address and restriction flags
// or the plug-in will assume that it is part of the Steam ID/IP Address
// Another alternative to using a steam id is a name and password
// The format of this is ;;"name";password flags
// For example I would use
// ;;"Mani";maniadminplugin rp // Admin can't rcon or playsound
// In order to use the password, put 
// setinfo _password mypassword 
// in your config.cfg file in your client installation.


//IP Admin supreme example


You have there all the instructions you need.


Blogger said...

DreamHost is ultimately one of the best web-hosting provider for any hosting plans you might require.

Post a Comment