Bannedaga1n wrote: ↑Sun May 05, 2024 1:40 am
Feuer_Psycho wrote: ↑Fri May 03, 2024 12:25 am
![Shocked :shock:](./images/smilies/icon_eek.gif)
So I tried something with the crafting recipe thingy. If someone crazy enough wants to try it. I basically poked around after reading a post from February and was like "can it be that easy to just change some register types from what is documented in the script to what it looks like now".
It worked on my end to change the recipe outcome and ingredients.
Sadly the other tables Rubyelf has posted only work on steam by what they said but thankfully this one is working on game pass, thank you!
They actually both work on Steam, I did notice if I enable the other one and then try to enable mine it does not work. I have no idea why that is the case, but both of them do the same thing functionally. I did add theirs to my table though as an alternative for people.
Their AOB unique code is the same as mine, but their disable point is not, eg:
Both have this:
[ENABLE]
aobscanmodule(craftDataINJECT,GameAssembly.dll,48 8B 57 48 48 85 D2 0F 84 16) // should be unique
alloc(newmem,$1000,craftDataINJECT)
label(code)
label(return)
alloc(CraftData,4,craftDataINJECT)
registersymbol(CraftData)
newmem:
mov [CraftData],rdi
code:
mov rdx,[rdi+48]
test rdx,rdx
jmp return
both these parts are different:
Mine:
[DISABLE]
craftDataINJECT:
db 48 8B 57 48 48 85 D2
Theirs:
[DISABLE]
craftDataINJECT:
db 48 8B 43 48 48 85 C0
Their original code is also pointing in the wrong direction as it doesn't even point to the same area, and their disable code goes elsewhere too.
So functionally ours are the same minus that part.
You can see here I have mine enabled and it is enabling theirs without even toggling it to to do so. The issues arise when attempting to disable theirs.