[Workshop] A couple minor but powerful additions to custom statuses#61

(This was previously posted on the workshop beta noltboard.)

I understand there might be a desire to keep custom statuses light, since they can’t have netprops attached to them, but I have two suggestions that feel simple on the surface and would have greatly useful effects.

1. Currently, statuses must use their value as a timer, so we cannot have a status with both a timer and a value. It would be nice for a timer variable to be baked in - an int that can be get/set freely and automatically counts up (or down) every frame.
2. Currently, if multiple copies of the same status exist on one character, they have difficulty knowing who’s run first or whether something that should only be done once has already happened. It would be nice if there was an option for one instance of the status to “speak for the team” - perhaps a settable boolean for “has already been processed”, which is reset at the end of each hook.