Feature Request: Cooldown API and forfeit votes about get5 HOT 5 CLOSED

I'm fine with them being added, but don't plan on doing it myself. Some thoughts:

• having cooldowns like that only makes sense to me if there is a ready up system for each client instead of anyone on the team being able to ready up
• both features would need to be disabled entirely by default

from get5.

Alright, if I implement it soon, should I do it within the base plugin or through a third party?

from get5.

If it's going to create get5 forwards it should be in the base plugin.

Get5_OnClientCooldown should also use the steam64 id rather than AuthId_Engine since that's what the plugin stores everywhere internally. I'm not entirely sure what the purpose of the disconnectiontime timestamp either.

I would imagine the plugin should be tracking total time disconnected since match start, and when that total time reaches some cvar get5_client_cooldown_threshold (or something like that) seconds it would fire the forward.

I think to make this useful there may have to be a separate mechanism checking if clients originally connect when the match is loaded. Aka #7. Only checking leavers and not someone never connecting would be an incomplete feature imo.

from get5.

FYI: these features are only useful for a pugging system, which means they are pretty unlikely to be implemented anytime soon.

from get5.

I'm going to close this since I don't plan on ever implementing it, as it's not very useful for competitive plan (only for pugs/matchmaking systems).

from get5.