Chat-Processor-Tags

Processes chat and provides colors and longer optionally-multicolored tags for Source 2013 games

To compile your own build, or to run the plugin on your server, you will also need to download/install Chat-Processor by Redwerewolf.

If you already have a copy of colorvariables.inc in your "scripting/includes" folder of wherever you write your plugins, be aware as this plugin comes with its own version of colorvariables.inc that has been updated to new 1.8 syntax by Redwerewolf that it requires to compile. If you do have an older copy, you can either remove it, or just back it up elsewhere if you plan on modifying this plugin.

Commands

sm_reloadtags - Reloads the config file

ConVars

sm_cpt_version - Standard version ConVar, do not touch.

About This Plugin

• Chat-Processor Tags was created by 404 (abrandnewday on AlliedMods)
• Chat-Processor Tags started life as a copy of Custom Chat Colors by Dr. McKay (http://www.doctormckay.com)
• Chat-Processor was created by Keith Warren (Drixevel) (redwerewolf on AlliedMods)
• Chat-Processor started life as a copy of Simple Chat Colors (Redux) by minimoney and updated to new 1.8 syntax by 404

Converting custom-chatcolors.cfg entries for use in chat-processor-tags.cfg

Here's a list of named colors within ColorVariables that you can use in the "tag" lines of the config . You can also just take a hex color code (i.e. #FF5365) and wrap it in brackets and use it like this: {#FF5365}. And yes, you can intermix the hex color codes and the named color codes like this:

"tag" "{#FFC000}[{valve}PLUGIN DEV{#FFC000}] "

This depends on if you want to have multiple colors in your chat tags.

If you want to use multiple colors in a tag

1. Copy the contents of your original custom-chatcolors.cfg file and paste them into chat-processor-tags.cfg
2. Change "admin_colors" at top of the entries to "chat_processor_tags"
3. Edit the "tag" line for each of your config entries and add the proper color codes to that line
4. You can remove the "tagcolor" bits if you want. The plugin now detects if there's color codes in the tag string, and if there are, it'll use those colors.

You can use any hex color code you want simply by putting it inside brackets, like this: #FFC000 would be changed to {#FFC000}

For example:

"tag" "{#FFC000}[{community}ADMIN{#FFC000}] "

If you don't want to use multiple colors in the tag and you just want to keep your old setup

1. Copy the contents of your original custom-chatcolors.cfg file and paste them into chat-processor-tags.cfg
2. Change "admin_colors" at top of the entries to "chat_processor_tags"
3. You're done. You don't have to change anything else. Everything should work as normal.

CS:GO Usage

-This might be entirely untrue. I'm not 100% sure because I haven't tested this plugin in CS:GO yet. Someone really should test it out and then get back to me. As far as I know, colors you define in the "tag" entry may not show up in CS:GO because of how it handles colors. I might be entirely wrong. If I am however correct, and CS:GO supports colors poorly, then there are some engine colors that you can use._

For CS:GO, you will need to format your entries a little differently:

"STEAM_0:1:1234567" // Here is a steamid example with a tag (don't duplicate steamids)
{
  "tag"			"[ADMIN] " // This is the text for the tag. Do not add any colors into this field.
  "tagcolor"		"G" // This is the color for the tag. Choose from T (teamcolor), G (green), or O (olive)
  "namecolor"		"T" // This is the color for the name. Choose from T (teamcolor), G (green), or O (olive)
  "textcolor"		"O" // This is the color of the text. Choose from T (teamcolor), G (green), or O (olive)
}

Yes, I know, CS:GO really sucks for chat color support right now. Deal with it. And FYI, I was originally planning on adding in an APLRes check to prevent this plugin from running on CS:GO. However I would've had to deal with hordes of people asking/demanding for CS:GO support, so this was the next best solution.

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
2. If there is a Steam ID present, it will always override everything.
3. If you put a Steam ID in twice then the first entry (top to bottom) will be used. (I think, just don't do it!)
4. Groups
5. The plugin will search (top to bottom) for a postitive match for the flag string.
6. 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.
7. For example: Let's say that Admins have the "ad" flags and donators have the "a" flag. If you place the "a" flag group above the "d" flag group then the admin will get the "a" colors. Order matters.

Example config file setup

"chat_processor_tags"                      // 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)
    {                                      // Open the steamid
        "tag"        "{community}[ADMIN] " // This is the text for the tag. Include color values for your tag here
		"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
    }                                      // Close the steamid
 
    "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. Personal preference of mine is to add a space after 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)

NOTES:

1. If you don't enter a steamid then the group name does not matter, it's just for your reference.
2. If you want to use multiple color strings in the "tag" field, go right ahead.
3. Here's a perfect example for you to try. It results in a tag that says [HOT] and looks like it's a fireball:
4. "tag" "{red}[{orange}H{yellow}O{orange}T{red}] "
5. If you want to use symbols and alt codes and unicode shit, try saving the chat-processor-tags.cfg file in a different Unicode format.
6. For a list of colors, download the "colorvariables.inc" file and view it in Notepad
7. For name/text colors, either a hex notation of a color (#RRGGBB or #RRGGBBAA) or a supported shortcut (O - Olive, G - Green, T - Team) are required