This is where you place all your users that you wish to have access to have immunity to certain functions of the plugin. The default file explains how to setup your immunity lists.
Edit the file $BASE/cstrike/cfg/mani_admin_plugin/immunitylist.txt
For reference here is an example extract: -
// // Add your IP's Steam addresses, Names and Passwords or immunity groups // in this file for immunity // // // e.g STEAM_0:0:21233123 // 213.44.33.47 // // ADDING FLAGS MEANS YOUR ARE MAKING ADMINS IMMUNE TO THOSE OPTIONS // THOSE OPTIONS UNLESS YOU HAVE mani_reverse_immunity_flags set to 1 // in your autoexec.cfg // // Restriction options are :- // // j = make user immune from being gimped // k = make user immune from being kicked // m = make user immune from being slayed // b = make user immune from being banned // x = make user immune from having cexec commands run against them // i = make user immune from being blinded // l = make user immune from being slapped // f = make user immune from being frozen // t = make user immune from being teleported // d = make user immune from being drugged // g = make user immune from being team swapped // c = make user immune from being auto swapped // e = make user immune from being burned // h = make user immune from being muted // n = make user immune from being kicked due to a reserve slot player joining // o = make user immune from having their skin set by admin // q = make user immune from being time bombed by admin // r = make user immune from being fire bombed by admin // s = make user immune from being freeze bombed by admin // u = make user immune from being turned into a beacon by admin // v = make user immune from being blinded when anti ghosting is turned on // w = make user immune from the ma_give and ma_giveammo commands // y = make user immune from the ma_colour and ma_color commands // // a = allows the user to be immune from the autokick/ban name/pname functionality // p = allows the user to have access to reserved skins // // // An example would be if you wanted a user // with steam id STEAM_0:0:2388333 // to be immune from being banned or slayed // // STEAM_0:0:2388333 mb // User can't be banned or slayed // // Another example // STEAM_0:0:3389333 ilf // User can't be blinded slapped or frozen // // // You can also use immunity groups instead of flags, you setup immunity groups // in the immunitygroups.txt file then use them in this file. // For example if you setup a group called "No Kick or Ban" and "NoFun" you would set it per // player like this:- // // STEAM_0:0:1234234 No Kick Or Ban // Fred // STEAM_0:0:234884 NoFun // Jim // // // If you wanted an user to be created by IP Address you // set your entry to be in the format // // ;IP Address flag // // Example // // ;213.133.76.58 mb // User can't be banned or slayed // ;113.124.36.2 ilf // User can't be blinded slapped or frozen // // If you want to have a user created by both steam ID and IP address you // use the format STEAM_ID;IP_ADDRESS flags // // Example // // STEAM_0:1:877489;231.192.67.5 ilf // User can't be blinded slapped or frozen // // IMPORTANT NOTES !!!! // // 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 ilf // User can't be blinded slapped or frozen // // In order to use the password, put // // setinfo _password mypassword // // in your config.cfg file in your client installation. // //