That is odd, but tap() function seems to work well, so I'm asking is a difference between holdingbutton() and tap() other than its obvious differences or is this simply a result of the underlying Valve problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
holdingbutton is a retriever function and has no side effect ;)
The tap button fundtion just makes the bot press the button for one frame.
It has no effect as I have forced the primary attack button on/off using the rcbot_flipout command, and it didn't help the medic bug.
The only way the medic bug is fixed is by using the tf_medigun_autoheal 1 cvar, which means the bots now should not hold the button and instead just tap the button .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Medic fixed for now
Is this an issue with holdbutton function? tap() seems to work fine on medic (haven't tested it on pyro).
It is an underlying Valve problem,
The problem was fixed by using "tf_medigun_autoheal 1" CVAR on bots
the attack method had no effect with the bug..:s
That is odd, but tap() function seems to work well, so I'm asking is a difference between holdingbutton() and tap() other than its obvious differences or is this simply a result of the underlying Valve problem?
holdingbutton is a retriever function and has no side effect ;)
The tap button fundtion just makes the bot press the button for one frame.
It has no effect as I have forced the primary attack button on/off using the rcbot_flipout command, and it didn't help the medic bug.
The only way the medic bug is fixed is by using the tf_medigun_autoheal 1 cvar, which means the bots now should not hold the button and instead just tap the button .
That's good. Will the cvar be just a temporary fix?