[Celena Luna]

Like the title said and I want to it on Ham_Weapon_SecondaryAttack since cmd_start, it mess up with moving button.

[HamletEagle]

Use pev_oldbuttons and pev_button.

[Celena Luna]

Originally Posted by HamletEagle Use pev_oldbuttons and pev_button.

I did you them on FM_CmdStart. They does work but on client side, something the holding got release while moving around.
And I as far as I know if you didn't press the button, you can't execute Ham_Weapon_SecondaryAttack => you can't detect when you release holding it.

[aron9forever]

the way I managed to detect press / hold / release is by adding a small time tolerance to the mix (something like 200 - 300ms delay and also fault tolerance)

I did this because on my crappy connection, even though I was holding a button, server would occasionally detect as not holding, so when I tried doing something like "charge while holding", it would end prematurely sometimes

checking halflife_time(or gametime), store the value at every check, and only change button state when more than 200ms passed

this happens at prethink


here the if() that is most nested is where I consider button hold being released

[Relaxing]

For -attack2
Check if oldbutton is IN_ATTACK2 && !butto = IN_ATTACK2