[thetwistedpanda]

Dependencies:

• SDKHooks - Required
  
• Colors.inc - Required (To Compile)

Description:

• The plugin was developed along side the public Player Trails plugin for my personal community, but I no longer have the time or desire to maintain two separate plugins that possess the exact same functionality. The scope of the plugin has been limited solely to CS:S; I may be able to port it to HL2M/DoD:S upon request if you're unable to do so. For those of you that wish to update from Player Trails, please note that every cvar and configuration file has had some form of change!
• Essentially, this plugin provides functionality for attaching env_spritetrails to players that will follow them around as they move.
• Unfortunately, I am unable to provide any custom materials with the release. Why not download some of these ?

Features:

• Access to Supporter Trails can be provided to everyone, or restricted to players with access to the override "Trails_Access" or the defined flag.
• Ability to enable/disable client specific tracer features, such as: color, layout, material, starting width, ending width, life time, render mode, and visibility.
• Choose the default starting values for all client settings, or have them randomized per player.
• Features that are disabled are forced to be the value selected for the client's default.
• Control what commands open the plugin menu via a simple cvar.
• Four configuration files located in /sourcemod/trails/ that control all other aspects of the plugin.
• Custom material files configured in /trails/css_trails_materials are automatically precached and added to the server's download table.
• Custom materials / colors / layouts can be restricted to overrides and/or flags per each definition.
  • Overrides: Trails_Access_Materials, Trails_Access_Colors, Trails_Access_Layouts
• Layouts provide the ability to assign multiple trails to clients, allowing for various (albeit complex) designs.
• Command (ADMFLAG_RCON): css_trails_print - Prints a list of indexes that are to be used in plugin cvars.

ConVars:

• css_trails_enabled - Enables/Disables all features of this plugin.
• css_trails_flag - If "", everyone can use Supporter Trails, otherwise, only players with this flag or the "Trails_Access" override can access.
• css_trails_commands - The chat triggers available to clients to access trail features.
• css_trails_default - The default trail status that is set to new clients.
• css_trails_default_color - The default color index to be applied to new players or upon css_trails_config_color being set to 0. (-1 = Random, # = Index)
• css_trails_default_layout - The default layout index to be applied to new players or upon css_trails_config_layout being set to 0. (-1 = Random, # = Index)
• css_trails_default_lifetime - The default lifetime index to be applied to new players or upon css_trails_config_lifetime being set to 0 (-1 = Random, # = Index)
• css_trails_default_starting - The default starting width index to be applied to new players or upon css_trails_config_starting being set to 0 (-1 = Random, # = Index)
• css_trails_default_ending - The default ending width index to be applied to new players or upon css_trails_config_ending being set to 0 (-1 = Random, # = Index)
• css_trails_default_render - The default render index to be applied to new players or upon css_trails_config_render being set to 0 (-1 = Random, # = Index)
• css_trails_default_material - The default material index to be applied to new players or upon css_trails_config_material being set to 0 (-1 = Random, # = Index)
• css_trails_default_visible - The default visibility index applied to new players. (0 = Player Only, 1 = Team Only, 2 = All)
• css_trails_config_color - If enabled, clients will be able to change the color of their trail.
• css_trails_config_layout - If enabled, clients will be able to change the layout of their trail.
• css_trails_config_lifetime - If enabled, clients will be able to change the lifetime of their trail.
• css_trails_config_starting - If enabled, clients will be able to change the starting width of their trail.
• css_trails_config_ending - If enabled, clients will be able to change the ending width of their trail.
• css_trails_config_render - If enabled, clients will be able to change the rendering mode of their trail.
• css_trails_config_material - If enabled, clients will be able to change the material of their trail.
• css_trails_config_visible - If enabled, clients will be able to change the visibility status of their trail.

Installation:

• /sourcemod/scripting/css_supporter_trails.sp
• /sourcemod/plugins/css_supporter_trails.smx
• /sourcemod/translations/css_supporter_trails.phrases.txt
• /sourcemod/config/trails/css_trails_colors.ini
• /sourcemod/config/trails/css_trails_configs.ini
• /sourcemod/config/trails/css_trails_layouts.ini
• /sourcemod/config/trails/css_trails_materials.ini

[thetwistedpanda]

Reserved

[tooti]

Dont work for me, my server is crashing on start (cs:s)

Edit: now its works xD

[thetwistedpanda]

I've had them running on my server for 8+ months, if it doesn't work, you screwed something up to put it bluntly.

[4bdul]

How can I remove some of the rendering methods?

Method 1, 2 and 4 seem to be the exact same - Method 4 and 6 are the same too.

[thetwistedpanda]

There's a configuration file, set them to 0 instead of 1. There are actually 10 or 11 render methods, I failed to provide them all. They're not the same, but they likely affect the env_spritetrail in the same manner.

[Dr. McKay]

Any chance this would work with TF2?

[thetwistedpanda]

Nupe, TF2's ban on attachments no love for trails. Some have requested a particle version which may work, but that's outside my comfort zone as I don't mess with it.

[Demented]

Is the only way to limit the duration in the menus is by editing the sp and recompiling? Would be nice if there was a config to limit the max duration to 1.0 trails that are too long are...well they're too long lol. Besides that nice plugin.

Also I found this could this be used to edit max duration? If so could you tell me how...i'm noob @ this xD

" "LifeTimes"
{
"accurate_count" "0"
"accurate_factor" "0.0"

"regular_count" "30"
"regular_factor" "0.1"

[thetwistedpanda]

That's exactly what that config file is for. If you want 1.0, you'll want a regular_count 10. (10 * 0.1 being 1.0)