Page 5 of 5
Re: Modifying chat with sayfilter but SayCommand doesnt "register"
Posted: Sun Apr 09, 2017 9:45 am
by Ayuto
I think SM was allocating fake buffers. Those buffers seem to be allocated without RTTI data. That's similar to the issue we had here:
https://github.com/Source-Python-Dev-Te ... -232789719
Re: Modifying chat with sayfilter but SayCommand doesnt "register"
Posted: Sun Apr 09, 2017 11:58 am
by decompile
How would that look like?
Re: Modifying chat with sayfilter but SayCommand doesnt "register"
Posted: Sun Apr 09, 2017 12:59 pm
by Ayuto
Maybe something like this will work:
Syntax: Select all
from memory import get_object_pointer
buffer = ProtobufMessage('CCSUsrMsg_SayText2')
args[3].copy(buffer, buffer.byte_size)
# Do you stuff here
get_object_pointer(buffer).copy(args[3], buffer.byte_size)
But I can't really tell you more without doing tests on my own.
Re: Modifying chat with sayfilter but SayCommand doesnt "register"
Posted: Sun Jun 18, 2017 2:18 pm
by decompile
CS:S received an update 2 days ago, and looks like some signatures changed.
Could someone please update that?
UTIL_SayText2Filter = server[SAYTEXT2_FILTER_IDENTIFIER].make_function(
ValueError: Could not find signature: 558bec2a2a2a2a2a2a2a2ae8c05ff1ff
Re: Modifying chat with sayfilter but SayCommand doesnt "register"
Posted: Sun Jun 18, 2017 7:24 pm
by iPlayer
New signature is
Code: Select all
\x55\x8B\xEC\x68\x2A\x2A\x2A\x2A\xFF\x75\x08\xE8\x2A\x2A\x2A\x2A\x8B\x45\x0C