-
-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] GiveNamedItem parameters are incorrect (?) #466
Comments
By "older versions" you mean pre-Fire Sale update, right? I also use that hook in one my plugins and updated the signature for CSSharp via #463. Previously the hook was not being triggered as I think we were hooking another function that also gives items (but that is not called when purchasing/receiving items on spawn). |
It was working completely fine until the latest big update that broke the signs. Since then only the item purchase and console give triggers it well. This could be possibly caused by dynohook in CSS(?), but I'm not sure |
Also I thought we were using offsets for this? |
We're using offsets for calling GiveNamedItem, but I think memory function hooking currently just works for signatures, that's why CSSharp still maintains the GiveNamedItem signature. |
Yeah I'm also not sure if this is related to DynoHook, but I'd guess it's not. |
This issue has been marked |
@K4ryuu Can you confirm if there are still issues with this? |
GiveNamedItem
function returns wrong values to theVirtualFunctions.GiveNamedItemFunc.Hook
In the older versions it also returned the classname properly.
When you purchase and item or give by console cmd with sv_cheats and you log the first three params of the DynamicHook you see this (which is correct):
But when you give an item with GiveNamedItem CSS functions, you see this (and you cannot get the classname of weapon)
In my case I want to use the classname for further validations, but its just like not exists if GiveNamedItem is being used to give weapon
The code I added at the first lines of GiveNamedItemFunc.Hook:
The text was updated successfully, but these errors were encountered: