geode
geode copied to clipboard
vtable hooking
Geode Version
v4.x
Related Problem
this one is scary
the reason we dont have it right now is that its not easy to implement it in a foolproof way
windows recreates gd vtables macos and ios recreates every vtable android recreates vtables too i think im not exactly sure about android
but what this means is that there are multiple vtables for a single class we cant possibly find addresses for every single one of them and patch every single one of them
thats the main issue we have right now
if we decide to compromise on lets say only hooking the vtable inside gd we need to explicitly specify it in docs and let people know of the side effects of that behavior (there are a shit ton and they are not intuitive at all)
this also requires exposing the handler in tuliphook directly but thats the easy part
one of the big side effects is that this table hooking will not affect superclasses :D
anyway ramble over this might possibly spill to v5
Your Solution
.
Additional Information
No response