bSendPacket broken (19/02/22 CS:GO update)
codecheck01 opened this issue · 12 comments
bSendPacket is no longer on the stack.
The proper way should be to set the value directly in the EBX register.
I fixed it by following the csgosimple , but the createmove is void now, and I::Prediction->SetLocalViewAngles(pCmd->angViewPoint) is executed when createmove is true, should i directly execute it ?
https://github.com/aydenli530/qo0-base_learn/blob/main/qo0%20ebx%20hooks.cpp
I fixed it by following the csgosimple , but the createmove is void now, and I::Prediction->SetLocalViewAngles(pCmd->angViewPoint) is executed when createmove is true, should i directly execute it ? https://github.com/aydenli530/qo0-base_learn/blob/main/qo0%20ebx%20hooks.cpp
You dont need to set viewangles in chlclient createmove
does not work update the database please
just hook CHL createmove
just hook CHL createmove
This is not the proper way, just a dirty workaround.
This is not the proper way, just a dirty workaround.---- What do you mean?
Because why changing the place to hook CreateMove, when the actual one is still working perfectly and only requires a minor change.
What should you change? They legit removed bSendPacket from the stack. I don't see how hooking CHL Createmove is ghetto...
What should you change? They legit removed bSendPacket from the stack. I don't see how hooking CHL Createmove is ghetto...
And so what you look like you have no idea about everything, why do you try to act like I'm talking shit.
I said we can keep using the same CreateMove hook, no longer on the stack doesn't mean we cannot access it.
It should even be simpler than before, the only problem is dealing with the compiler optimizations.
Yeah, go ahead and mess with your compiler settings, hooking CHL createmove is so ghetto 😢 I think I'm gonna go cry because all my choking features works without having to mess with compiler optimizations 😢
What should you change? They legit removed bSendPacket from the stack. I don't see how hooking CHL Createmove is ghetto...
And so what you look like you have no idea about everything, why do you try to act like I'm talking shit.
I said we can keep using the same CreateMove hook, no longer on the stack doesn't mean we cannot access it.
It should even be simpler than before, the only problem is dealing with the compiler optimizations.
you're right, but probably u will still need to wrap hook with naked proxy fn to get/set register safe without compiler optimizier shit. so both ways is proper and aint ghetto at all