[Simon.]

hmm this is wierd, i cant get it to work either, im not sure if i have done something wrong ;P

custom-chatcolors.cfg

PHP Code:

//        Custom Chat Colors is written by Dr. McKay (http://www.doctormckay.com)
//        Simple Chat Colors (Redux) is written by Antithasys
//        The configuration is very similar, so I've stolen Redux's documentation :P
//
//        How to edit this file:
//        "admin_colors"                                        <--    Leave this alone
//        {                                                                <--    Add all groups/steamids after first bracket (Leave this alone)
//
//            "STEAM_0:1:1234567"                        <--    Here is a steamid example with a tag (don't duplicate steamids)
//            {
//                "namecolor"        "#RRGGBB"                        <--    This is the color for the name (#RRGGBB in hex notation or #RRGGBBAA with alpha)
//                "textcolor"        "#RRGGBBAA"                        <--    This is the color of the text
//            }
//
//            "groupname"                                            <--    This can either be a steamid for a specific player, or a group name
//            {                                                            <--    Open the group
//                "flag"                "z"                            <--    This is the flag(s) assoicated with the group.  This field doesn't matter if the group name is a steamid
//                "tag"                "[admin]"                    <--    This is the text for the tag
//                "tagcolor"        "O"                        <--    This is the color for the tag
//                "namecolor"        "G"                        <--    This is the color for the name
//                "textcolor"        "T"                        <--    This is the color of the text
//            }                                                            <--    Close the group
//        }                                                                <--    Add all groups/steamids before last bracket (Leave this alone)
//
//        NOTE:
//        If you don't enter a steamid then the group name does not matter, it's just for your reference.
//
//        For colors, either a hex notation of a color (#RRGGBB or #RRGGBBAA) or one of the supported shortcuts (O - Olive, G - Green, T - Team) is required
//
//        --------ORDER OF OPERATIONS--------
//
//        The order in which you place items in the config file matters.  Here is what determins what color they get:
//        1. SteamID
//            If there is a steamid present, it will always override everything.  If you put a steamid in twice
//            then the first entry (top to bottom) will be used. (I think, just don't do it!)
//        2. Groups
//            The plugin will search (top to bottom) for a postitive match for the flag string.  The player' flags
//            will be compared with the group flag character (NOTE: only one flag per group! "a" is okay, "ab" is NOT),
//            and if the player has the flag, it will stop there.
//            For example. Admins with the "ad" flags and donators with the "a" flag.  If you place the "a" flag group
//            above the "d" group then the admin will get the "a" colors. Order matters.
//
//        ---------DO NOT EDIT ABOVE THIS LINE---------
"admin_colors"
{

    "Owner"
    {
        "flag"                "n"
        "tag"                "[Owner] "
        "tagcolor"            "#9EC34FAA"
    }

    "Staff"
    {
        "flag"                "i"
        "tag"                "[Staff] "
        "tagcolor"            "#9EC34FAA"
    }

    "Developer"
    {
        "flag"                "m"
        "tag"                "[Developer] "
        "tagcolor"            "#FF1493"
    }

    "Admin"
    {
        "flag"                "b"
        "tag"                "[Admin] "
        "tagcolor"            "#9EC34FAA"
    }

    "VIP"
    {
        "flag"                "o"
        "tag"                "[VIP] "
        "tagcolor"            "#9EC34FAA"
    }
} 


admins_simple.ini

PHP Code:

"STEAM_1:0:112961809" "99:moz" //simon 


errorlog

PHP Code:

L 11/09/2016 - 12:23:54: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:23:54: [SM] Call stack trace:
L 11/09/2016 - 12:23:54: [SM]   [0] PbReadString
L 11/09/2016 - 12:23:54: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:23:54: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:23:54: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:23:54: [SM] Call stack trace:
L 11/09/2016 - 12:23:54: [SM]   [0] PbReadString
L 11/09/2016 - 12:23:54: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:23: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:23: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:23: [SM] Call stack trace:
L 11/09/2016 - 12:28:23: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:23: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:23: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:23: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:23: [SM] Call stack trace:
L 11/09/2016 - 12:28:23: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:23: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:24: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:24: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:24: [SM] Call stack trace:
L 11/09/2016 - 12:28:24: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:24: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:24: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:24: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:24: [SM] Call stack trace:
L 11/09/2016 - 12:28:24: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:24: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:25: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:25: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:25: [SM] Call stack trace:
L 11/09/2016 - 12:28:25: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:25: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:25: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:25: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:25: [SM] Call stack trace:
L 11/09/2016 - 12:28:25: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:25: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:26: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:26: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:26: [SM] Call stack trace:
L 11/09/2016 - 12:28:26: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:26: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:28:26: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:28:26: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:28:26: [SM] Call stack trace:
L 11/09/2016 - 12:28:26: [SM]   [0] PbReadString
L 11/09/2016 - 12:28:26: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:30:11: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:30:11: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:30:11: [SM] Call stack trace:
L 11/09/2016 - 12:30:11: [SM]   [0] PbReadString
L 11/09/2016 - 12:30:11: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:30:11: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:30:11: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:30:11: [SM] Call stack trace:
L 11/09/2016 - 12:30:11: [SM]   [0] PbReadString
L 11/09/2016 - 12:30:11: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:30:12: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:30:12: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:30:12: [SM] Call stack trace:
L 11/09/2016 - 12:30:12: [SM]   [0] PbReadString
L 11/09/2016 - 12:30:12: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2
L 11/09/2016 - 12:30:12: [SM] Exception reported: Invalid field "params" for message "CCSUsrMsg_SayText2"
L 11/09/2016 - 12:30:12: [SM] Blaming: simple-chatprocessor.smx
L 11/09/2016 - 12:30:12: [SM] Call stack trace:
L 11/09/2016 - 12:30:12: [SM]   [0] PbReadString
L 11/09/2016 - 12:30:12: [SM]   [1] Line 353, D:\Libraries\Documents\Repos\Simple Chat Processor\scripting\simple-chatprocessor.sp::OnSayText2 


[Dr. McKay]

1. As noted (very prominently) in the first post, CS:GO doesn't support arbitrary colors
2. You need the CS:GO version of Simple Chat Processor. Unfortunately I don't know off-hand where to find it. I think it's somewhere in this thread.

[xines]

Originally Posted by Dr. McKay 2. You need the CS:GO version of Simple Chat Processor. Unfortunately I don't know off-hand where to find it. I think it's somewhere in this thread.

https://forums.alliedmods.net/showpo...postcount=1047

[Mitchell]

Originally Posted by xines https://forums.alliedmods.net/showpo...postcount=1047

That's a link to my Custom Chat Colors for csgo, which is what Simon. would need, also Simple Chat Processor is linked here: https://bitbucket.org/minimoney1/sim...-processor/src

[Cripix]

Hi

I have an error with the command sm plugins list but the plugin works very well

L 11/10/2016 - 18:21:06: [SM] Exception reported: Fatal error creating dynamic native!
L 11/10/2016 - 18:21:06: [SM] Blaming: custom-chatcolors.smx
L 11/10/2016 - 18:21:06: [SM] Call stack trace:
L 11/10/2016 - 18:21:06: [SM]   [0] CreateNative
L 11/10/2016 - 18:21:06: [SM]   [1] Line 55, D:\Libraries\Documents\Repos\Public Plugins\scripting\custom-chatcolors.sp::AskPluginLoad2
L 11/10/2016 - 18:21:06: [SM] Failed to load plugin "custom-chatcolors.smx": unexpected error 23 in AskPluginLoad callback.

Errors:
custom-chatcolors.smx ([Source 2013] Custom Chat Colors): unexpected error 23 in AskPluginLoad callback

Thank you for your help

[Simon.]

Originally Posted by Mitchell That's a link to my Custom Chat Colors for csgo, which is what Simon. would need, also Simple Chat Processor is linked here: https://bitbucket.org/minimoney1/sim...-processor/src

Well, i allready have those plugins installed on my server and it still dosent work ;P

i have changed the color codes to {01} now for the csgo and i still get errors

[MAGNAT2645]

Why one of all Keys with STEAMID in config wont work.
All Keys that parsed in config works, but one of them wont change tag.

im tried to use STEAM3 instead of STEAMID but nothing changed.

This key wont work.

PHP Code:

"STEAM_0:1:75017227"
{
    "tag"                "Test moder tag "
    "tagcolor"            "000000"
    "namecolor"        "0033FF"
} 


[Mitchell]

Originally Posted by Simon. Well, i allready have those plugins installed on my server and it still dosent work ;P i have changed the color codes to {01} now for the csgo and i still get errors

Please reread my post and install the simple chat processor that works for csgo..

[xTremo]

Pls help dont work (CS:GO)

custom-chatcolors.cfg

PHP Code:

//        Custom Chat Colors is written by Dr. McKay (http://www.doctormckay.com)
//        Simple Chat Colors (Redux) is written by Antithasys
//        The configuration is very similar, so I've stolen Redux's documentation :P
//        
//        How to edit this file:
//        "admin_colors"                                        <--    Leave this alone
//        {                                                                <--    Add all groups/steamids after first bracket (Leave this alone)
//                                                                            
//            "STEAM_0:1:1234567"                        <--    Here is a steamid example with a tag (don't duplicate steamids)
//            {
//                "namecolor"        "#RRGGBB"                        <--    This is the color for the name (#RRGGBB in hex notation or #RRGGBBAA with alpha)
//                "textcolor"        "#RRGGBBAA"                        <--    This is the color of the text
//            }
//
//            "groupname"                                            <--    This can either be a steamid for a specific player, or a group name
//            {                                                            <--    Open the group
//                "flag"                "z"                            <--    This is the flag(s) assoicated with the group.  This field doesn't matter if the group name is a steamid
//                "tag"                "[admin]"                    <--    This is the text for the tag
//                "tagcolor"        "O"                        <--    This is the color for the tag
//                "namecolor"        "G"                        <--    This is the color for the name
//                "textcolor"        "T"                        <--    This is the color of the text
//            }                                                            <--    Close the group
//        }                                                                <--    Add all groups/steamids before last bracket (Leave this alone)
//
//        NOTE:
//        If you don't enter a steamid then the group name does not matter, it's just for your reference.
//
//        For colors, either a hex notation of a color (#RRGGBB or #RRGGBBAA) or one of the supported shortcuts (O - Olive, G - Green, T - Team) is required
//
//        --------ORDER OF OPERATIONS--------
//        
//        The order in which you place items in the config file matters.  Here is what determins what color they get:
//        1. SteamID
//            If there is a steamid present, it will always override everything.  If you put a steamid in twice
//            then the first entry (top to bottom) will be used. (I think, just don't do it!)
//        2. Groups
//            The plugin will search (top to bottom) for a postitive match for the flag string.  The player' flags
//            will be compared with the group flag character (NOTE: only one flag per group! "a" is okay, "ab" is NOT),
//            and if the player has the flag, it will stop there.
//            For example. Admins with the "ad" flags and donators with the "a" flag.  If you place the "a" flag group
//            above the "d" group then the admin will get the "a" colors. Order matters.
//
//        ---------DO NOT EDIT ABOVE THIS LINE---------
"admin_colors"
{
    "STEAM_1:0:151329127"
    {

        "tag"                "[Owner] "
        "tagcolor"            "O"
        "namecolor"            "G"
        "textcolor"            "T"
        "flag"                "o"
    }
    
    "testadmin"
    {

        "tag"                "[admin] "
        "tagcolor"            "O"
        "namecolor"            "G"
        "textcolor"            "T"
    }
} 


admins.cfg

PHP Code:

/**
 * USE THIS SECTION TO DECLARE DETAILED ADMIN PROPERTIES.
 *
 * Each admin should have its own "Admin" section, followed by a name.
 * The name does not have to be unique.
 *
 * Available properties: (Anything else is filtered as custom)
 *      "auth"          - REQUIRED - Auth method to use.  Built-in methods are:
 *                        "steam"  - Steam based authentication
 *                        "name"   - Name based authentication
 *                        "ip"    - IP based authentication
 *                        Anything else is treated as custom.
 *                     Note: Only one auth method is allowed per entry.
 *
 *      "identity"      - REQUIRED - Identification string, for example, a steamid or name.
 *                     Note: Only one identity is allowed per entry.
 *
 *      "password"      - Optional password to require.
 *      "group"         - Adds one group to the user's group table.
 *      "flags"         - Adds one or more flags to the user's permissions.
 *        "immunity"        - Sets the user's immunity level (0 = no immunity).
 *                          Immunity can be any value.  Admins with higher 
 *                          values cannot be targetted.  See sm_immunity_mode 
 *                          to tweak the rules.  Default value is 0.
 *
 * Example:
    "BAILOPAN"
    {
        "auth"            "steam"
        "identity"        "STEAM_0:1:16"
        "flags"            "abcdef"
    }
 *
 */
Admins
{
    "Ego Eum Sicarius"
    {
        "auth"        "steam"
        "identity"    "steam id"
        "flags"        "bc"
        "group"        "testadmin"
        "immunity"    "1"
    }
    "??? trem0 #"
    {
        "auth"        "steam"
        "identity"    "steam id"
        "flags"        "zo"
        "group"        "root"
        "immunity"            "99"
    }
} 


[cristian20042]

Originally Posted by Mitchell Quick tip, since i didnt want to have your updater included i changed: #include "mckayupdater.sp" to #tryinclude "mckayupdater.sp" Edit: i have some good news I have made the csgo version, with passive changes! it shouldnt break any modules Try this, to use the colors make sure you do: {01} - {09}, {0A} - {0F}, {10} as the color of the tag/chat/name see the colors/example here: Spoiler Colors Example: I'm also going to attach my test plugin The CCC_GetColor will return a number 1-16 if it is a csgo chat color 01-10-0A-0F etc. The reason i had to use {} is because KvGetString would return '7' instead of "07" EDIT: i threw in an idea if {03} is used it will change the author to -1, not sure if you want to keep that idea, it so they can use the color purple. This will replace 'T' with purple though.

I take the custom-chatcolors-csgo from Mitchell and this is working fine but the CUSTOM tags dosen't work(no errors anywhere)
Also the ORIGINAL one and the same problem...
(I fixed also the warning with GetClientAuthString is decrepated and doesn't work....)

here is the custom-chatcolors.cfg:

custom-chatcolors.cfg

Spoiler

PHP Code:

//        Custom Chat Colors is written by Dr. McKay ([url]http://www.doctormckay.com[/url])
//        Simple Chat Colors (Redux) is written by Antithasys
//        The configuration is very similar, so I've stolen Redux's documentation :P
//        
//        How to edit this file:
//        "admin_colors"                                        <--    Leave this alone
//        {                                                                <--    Add all groups/steamids after first bracket (Leave this alone)
//                                                                            
//            "STEAM_0:1:1234567"                        <--    Here is a steamid example with a tag (don't duplicate steamids)
//            {
//                "namecolor"        "#RRGGBB"                        <--    This is the color for the name (#RRGGBB in hex notation or #RRGGBBAA with alpha)
//                "textcolor"        "#RRGGBBAA"                        <--    This is the color of the text
//            }
//
//            "groupname"                                            <--    This can either be a steamid for a specific player, or a group name
//            {                                                            <--    Open the group
//                "flag"                "z"                            <--    This is the flag(s) assoicated with the group.  This field doesn't matter if the group name is a steamid
//                "tag"                "[admin]"                    <--    This is the text for the tag
//                "tagcolor"        "O"                        <--    This is the color for the tag
//                "namecolor"        "G"                        <--    This is the color for the name
//                "textcolor"        "T"                        <--    This is the color of the text
//            }                                                            <--    Close the group
//        }                                                                <--    Add all groups/steamids before last bracket (Leave this alone)
//
//        NOTE:
//        If you don't enter a steamid then the group name does not matter, it's just for your reference.
//
//        For colors, either a hex notation of a color (#RRGGBB or #RRGGBBAA) or one of the supported shortcuts (O - Olive, G - Green, T - Team) is required
//
//        --------ORDER OF OPERATIONS--------
//        
//        The order in which you place items in the config file matters.  Here is what determins what color they get:
//        1. SteamID
//            If there is a steamid present, it will always override everything.  If you put a steamid in twice
//            then the first entry (top to bottom) will be used. (I think, just don't do it!)
//        2. Groups
//            The plugin will search (top to bottom) for a postitive match for the flag string.  The player' flags
//            will be compared with the group flag character (NOTE: only one flag per group! "a" is okay, "ab" is NOT),
//            and if the player has the flag, it will stop there.
//            For example. Admins with the "ad" flags and donators with the "a" flag.  If you place the "a" flag group
//            above the "d" group then the admin will get the "a" colors. Order matters.
//
//        ---------DO NOT EDIT ABOVE THIS LINE---------
"admin_colors"
{
    "STEAM_0:0:187605547"
    {
        "tag"                "Barosanu'"
        "tagcolor"            "{02}"
    }
    "Fondator"
    {
        "flag"                "z"
        "tag"                "Founder"
        "tagcolor"            "{02}"
         "namecolor"            "{0C}"
        "textcolor"            "{01}"
    }
    "Owner"
    {
        "flag"                "m"
        "tag"                "Owner"
        "tagcolor"            "{02}"
         "namecolor"            "{0C}"
        "textcolor"            "{01}"
    }
    "Mod"
    {
        "flag"                "k"
        "tag"                "Mod"
        "tagcolor"            "{10}"
         "namecolor"            "{07}"
        "textcolor"            "{01}"
     }
    "Admin"
    {
        "flag"                "d"
        "tag"                "Admin"
        "tagcolor"            "{04}"
         "namecolor"            "{07}"
        "textcolor"            "{01}"
     }
    "Helper"
    {
        "flag"                "f"
        "tag"                   "Helper"
        "tagcolor"                 "{04}"
         "namecolor"            "{07}"
        "textcolor"            "{01}"
     }
    "VIP"
    {
        "flag"                "a"
        "tag"                "VIP"
        "tagcolor"            "{02}"
         "namecolor"            "{07}"
        "textcolor"            "{01}"
    }
} 


And the admins_simple CFG :

Spoiler

PHP Code:

//
// READ THIS CAREFULLY! SEE BOTTOM FOR EXAMPLES
//
// For each admin, you need three settings:
//  "identity"        "permissions"        "password"
//
// For the Identity, you can use a SteamID or Name.  To use an IP address, prepend a ! character.
// For the Permissions, you can use a flag string and an optional password.
//
// PERMISSIONS:
//  Flag definitions are in "admin_levels.cfg"
//  You can combine flags into a string like this:
//  "abcdefgh"
//
//  If you want to specify a group instead of a flag, use an @ symbol.  Example:
//  "@Full Admins"
//
//    You can also specify immunity values.  Two examples:
//    "83:abcdefgh"            //Immunity is 83, flags are abcdefgh
//    "6:@Full Admins"        //Immunity is 6, group is "Full Admins"
//
//    Immunity values can be any number.  An admin cannot target an admin with 
//    a higher access value (see sm_immunity_mode to tweak the rules).  Default 
//  immunity value is 0 (no immunity).
//
// PASSWORDS:
//  Passwords are generally not needed unless you have name-based authentication.
//  In this case, admins must type this in their console:
//
//   setinfo "KEY" "PASSWORD"
//
//  Where KEY is the "PassInfoVar" setting in your core.cfg file, and "PASSWORD"
//  is their password.  With name based authentication, this must be done before
//  changing names or connecting.  Otherwise, SourceMod will automatically detect
//  the password being set.
//
////////////////////////////////
// Examples: (do not put // in front of real lines, as // means 'comment')
//
//   "STEAM_0:1:16"        "bce"                //generic, kick, unban for this steam ID, no immunity
//   "!127.0.0.1"        "99:z"                //all permissions for this ip, immunity value is 99
//   "BAILOPAN"            "abc"    "Gab3n"        //name BAILOPAN, password "Gab3n": gets reservation, generic, kick
//
////////////////////////////////
 
"STEAM_0:0:187605547"        "99:z"
"STEAM_0:0:93317389"       "99:z"
"STEAM_1:1:159175247"      "99:z"
"STEAM_0:1:181303448"          "abcdefgjopqrst" //"abcdefghijklmnopqrst" // owner
// "STEAM_0:1:189820030"      // abcdefgjopqrst | Admin
"STEAM_0:1:189820030"      "abcdefgjkopqrst" // Mod
"STEAM_0:0:185190190"      "abcdefgjopqrst"
"STEAM_0:1:128652801"      "abcdefgjopqrst"
"STEAM_1:0:87882302"       "abcdefgjopqrst"    
"STEAM_1:1:156695545"      "acfjopqrst"   //Helper
"STEAM_1:0:159737388"      "cfjopqrst"