[Dr. McKay]

[TF2] Humiliation Conditions

v1.0.0

Description:
Applies various conditions to players during the humiliation round. Condition codes:

1 = UberCharged 2 = UberCharge Fading (requires 1 to be set for any effect) 4 = Teleported sparkle 8 = Buff Banner (Rings + Glowing) 16 = Battalion's Backup (Rings + Glowing) 32 = Mini-Crits (Crit-a-Cola) 64 = Jarated 128 = Mad Milked 256 = Quick-Fix MegaHeal 512 = Marked for Death 1024 = Speed Buff (Disciplinary Action)

Cvars:

• humiliation_conditions_version - plugin version
• humiliation_conditions_auto_update - enables automatic updating (has no effect if Updater is not installed), defaults to 1
• humiliation_conditions_winning_team - sum of condition codes to be applied to winning team
• humiliation_conditions_losing_team - sum of condition codes to be applied to losing team
• humiliation_conditions_winning_team_admin - sum of condition codes to be applied to admins on the winning team
• humiliation_conditions_losing_team_admin - sum of condition codes to be applied to admins on the losing team

Admins are defined by the "a" flag. The admin flag can be overridden by overriding "humiliation_conditions_admin".

Plugin creates and loads cfg/sourcemod/plugin.humiliationconditions.cfg.

Installation:
Put humiliationconditions.smx into /addons/sourcemod/plugins, and reboot your server or type "sm plugins load humiliationconditions" into your console or rcon.

Auto Update:
Install Updater. The plugin will be auto-updated according to your Updater settings. It'll work without Updater.

Changelog:

• v1.0.0 (5/3/13)
  • Initial release

Download Plugin (humiliationconditions.smx)
View Source (humiliationconditions.sp)

Requires updater.inc and mckayupdater.sp to compile.

[FlaminSarge]

Doesn't ubercharge not work for the losing team?

In addition, it might be more flexible to parse a string containing a list of comma-separated cond numbers (saving the list every time it's changed so you don't have to parse it every time you want to apply conds) instead of defining a set list of conds, so any cond can be used. Naturally, you'd block unsafe conds like cond 1.

[Dr. McKay]

Originally Posted by FlaminSarge Doesn't ubercharge not work for the losing team? In addition, it might be more flexible to parse a string containing a list of comma-separated cond numbers (saving the list every time it's changed so you don't have to parse it every time you want to apply conds) instead of defining a set list of conds, so any cond can be used. Naturally, you'd block unsafe conds like cond 1.

I don't know, I didn't test über on the losing team.

I did some testing and there's actually a very small list of conditions that can be applied (and work) with TF2_AddCondition. Plus in the future I'm planning on adding "conditions" that aren't true TF2 conditions, such as merging my Humiliation Glow plugin with this one.

[FlaminSarge]

There's 65 conditions right now, and nearly all of them work with the native (in particular, the ones that DON'T are healing, overhealed, inhealradius, bleeding, onfire; cloakflicker gets added and is removed a frame later if the relevant player isn't a cloaked spy touching an enemy/out of CnD cloak; similar restrictions are on 'disguising' but not 'disguised').

At the very least, cond 43 (reprogrammed) seems like a thing that would be interesting for this plugin; however, using string parsing and identifiers for your custom conditions would be far more flexible (yes, string parsing is generally considered clunky but with cvars you don't really have much choice so why not).

[Dr. McKay]

Originally Posted by FlaminSarge There's 65 conditions right now, and nearly all of them work with the native (in particular, the ones that DON'T are healing, overhealed, inhealradius, bleeding, onfire; cloakflicker gets added and is removed a frame later if the relevant player isn't a cloaked spy touching an enemy/out of CnD cloak; similar restrictions are on 'disguising' but not 'disguised'). At the very least, cond 43 (reprogrammed) seems like a thing that would be interesting for this plugin; however, using string parsing and identifiers for your custom conditions would be far more flexible (yes, string parsing is generally considered clunky but with cvars you don't really have much choice so why not).

I'll go through the list again and take a look, but in my experience a lot of the conditions either have no effect or don't work right in humiliation. Applying the bonked condition, for example, works but causes weird graphical glitches. Similarly, applying Kritzkreiged (or one of the other crits conditions) is useless, since the losers don't have weapons and the winners already have crits. I suppose I can remove crit-a-cola for that reason.

I suppose a comma-delimited list might work better. Numbers get pretty large pretty quick when doing bitwise

[FlaminSarge]

The Crit-a-Cola one is useful mainly because it causes players to take minicrits, which takes effect for afterburn, bleeding, and sentry guns. I suppose that's a reason you can leave it in.

In addition, if random crits are disabled, then players that respawn during humiliation don't deal winning crits, as they lose the winningcrit cond on respawn but can't crit. Even in stock TF2, it's possible to respawn during humiliation by changing classes if you're on the winning team, as long as your respawn timer has expired.

[Pootisbird]

Is it possible and when yes how to us multiple Conditions? Like "humiliation_conditions_winning_team 1,1024 " ?

[Dr. McKay]

Originally Posted by Pootisbird Is it possible and when yes how to us multiple Conditions? Like "humiliation_conditions_winning_team 1,1024 " ?

Add up the codes that you want to use. For example, 1 + 1024 = 1025.

[FlaminSarge]

Valve's increased the number of conditions to 71, so that system for that cvar may not be ideal if you want to add any more conds.