The changes in 5790a3c020 will throw all players into spectator if the lb_afk cvar is flipped on midgame. This was the reason for iterating and setting the afkTime, even when disabled. Using a CV_CALL is sadly not fast enough for preventing this.
I would like a revert or a fix before merging.
(Thumbs up emoji)
The changes in 5790a3c020 will throw all players into spectator if the lb_afk cvar is flipped on midgame. This was the reason for iterating and setting the afkTime, even when disabled. Using a CV_CALL is sadly not fast enough for preventing this.
I would like a revert or a fix before merging.
to be honest, i dont care. like who would turn the akf on in the middle of a race and not on server start.
i think this is better than wasting a full iteration on a feature that you might not want on.
to be honest, i dont care. like who would turn the akf on in the middle of a race and not on server start.
i think this is better than wasting a full iteration on a feature that you might not want on.
I agree it's not desirable, but I value consistent expectation of functionality over this negligible performance penalty. You shouldn't question why someone will do something but rather be prepared for it.
I'll apply a fix myself.
Thank you.
I agree it's not desirable, but I value consistent expectation of functionality over this negligible performance penalty. You shouldn't question why someone will do something but rather be prepared for it.
I'll apply a fix myself.
Thank you.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
(Thumbs up emoji)
The changes in
5790a3c020will throw all players into spectator if the lb_afk cvar is flipped on midgame. This was the reason for iterating and setting the afkTime, even when disabled. Using a CV_CALL is sadly not fast enough for preventing this.I would like a revert or a fix before merging.
to be honest, i dont care. like who would turn the akf on in the middle of a race and not on server start.
i think this is better than wasting a full iteration on a feature that you might not want on.
I agree it's not desirable, but I value consistent expectation of functionality over this negligible performance penalty. You shouldn't question why someone will do something but rather be prepared for it.
I'll apply a fix myself.
Thank you.
Pull request closed