cap point decay speed

If there's no straightforward way to do it, I'd probably have two cap zones and a trigger_multiple. The moment someone touches the trigger_multiple, it enables capture1, which has a cap rate of 10. The moment all blu players leave, the trigger_multiple would disable capture1 and enable capture2, which has a cape rate of 5. These outputs would have to be OnStartTouchAll and filtered for blu, though.

That's the best way I could think to work it.

Decay rates

Decay rates are inversely proportional of the base capture time. This means that the shorter the base capture time is, the longer the decay rates are. During overtime the Control point times decay at an expedited rate.

Click to expand...

From the tf2wiki.

Ezekel said:

quite a few people have mentioned that you can do this so that the decay speed will not be related to the cap time

Click to expand...

From the OP.

I'm pretty sure you can't do this. I don't know who these "people" are you speak of, but in my years I've never come across any such method. Bringing it up gave me one idea to try (differing combinations of playerstocap and captime) but that didn't have any bearing on the decay rate.

Just for the heck of it I tried yyler's idea since I had Hammer open, but I as I expected it didn't do it either, and only resulted in the screwed up progress indication on the HUD that always occurs if you have multiple cap zones with differing rates (doesn't matter if they are enabled and/or in use).

If you really really want it, your best bet would be to email valve and ask for a decay rate multiplier key/input.

lmbo @ asking Valve for anything

Why? Are you not aware they have added numerous keys, inputs and whole new entities at the request of mappers?

A Boojum Snark said:

Just for the heck of it I tried yyler's idea since I had Hammer open, but I as I expected it didn't do it either, and only resulted in the screwed up progress indication on the HUD that always occurs if you have multiple cap zones with differing rates (doesn't matter if they are enabled and/or in use).

Click to expand...

Would this also happen if, instead of disabling the cap zone, Killing it completely? And using templates to spawn new ones? (Id try it out, but have no source sdk where i am at the moment)

I'm fairly sure it would. All templated entities exist at the same time during map load, before they are eaten up by the templatizer.