Re: Monster Hunter World (Steam)
Posted: Thu Jan 09, 2020 9:53 pm
So, just to understand exactly what's going on... we can edit values for health and such? Does that mean we can lock them for god mode?
Community Cheat Tables of Cheat Engine
https://fearlessrevolution.com/
NOt your active health no, you will be kicked out of the network. You can't do anything that edits your active player.Lord Blade wrote: ↑Thu Jan 09, 2020 9:53 pmSo, just to understand exactly what's going on... we can edit values for health and such? Does that mean we can lock them for god mode?
I'm not good with lua to do that. Don't know if that will solve the script problem either.fearlessrevolution wrote: ↑Thu Jan 09, 2020 10:49 pmThe game is constantly calling SetThreadContext to reset all hardware break points. You can hook SetThreadContext and check for the return address, if the return address is within the game's main module, do nothing and return immediately, then you can use VEH debugger as usual.
Thank you so much for sharing that info! It helped out a lot!
fearlessrevolution is talking about this function here:
Code: Select all
<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
<CheatEntries>
<CheatEntry>
<ID>19021</ID>
<Description>"Allow VEH"</Description>
<LastState/>
<VariableType>Auto Assembler Script</VariableType>
<AssemblerScript>[ENABLE]
aobscanmodule(debugthreadret,KERNELBASE.dll,48 83 EC 28 48 FF 15 35 C6 0A 00)
alloc(newmem,$1000,debugthreadret)
label(code)
label(return)
registersymbol(debugthreadret)
newmem:
code:
ret
jmp return
debugthreadret:
jmp newmem
nop 6
return:
[DISABLE]
debugthreadret:
db 48 83 EC 28 48 FF 15 35 C6 0A 00
unregistersymbol(debugthreadret)
dealloc(newmem)
</AssemblerScript>
</CheatEntry>
</CheatEntries>
</CheatTable>
this won't resolve the scripts crashing games though due to checksums right? That will be another issue. Thanks wil ltry that, What is SE?Squall8 wrote: ↑Fri Jan 10, 2020 12:26 amThank you so much for sharing that info! It helped out a lot!
fearlessrevolution is talking about this function here:
[Link]
A simple ret at the beginning of the function will do. You can write an AA script for that:
You can use that when debugging. Then continue on with SE after. If you still need that info let me know.Code: Select all
<?xml version="1.0" encoding="utf-8"?> <CheatTable> <CheatEntries> <CheatEntry> <ID>19021</ID> <Description>"Allow VEH"</Description> <LastState/> <VariableType>Auto Assembler Script</VariableType> <AssemblerScript>[ENABLE] aobscanmodule(debugthreadret,KERNELBASE.dll,48 83 EC 28 48 FF 15 35 C6 0A 00) alloc(newmem,$1000,debugthreadret) label(code) label(return) registersymbol(debugthreadret) newmem: code: ret jmp return debugthreadret: jmp newmem nop 6 return: [DISABLE] debugthreadret: db 48 83 EC 28 48 FF 15 35 C6 0A 00 unregistersymbol(debugthreadret) dealloc(newmem) </AssemblerScript> </CheatEntry> </CheatEntries> </CheatTable>
No, it does counteract it.
So I tried your VEH but it doesn't enable, my guess its not a perfect aob?
Oof, overlooked that. It'll be different per system. But its a good thing to use wildcards there as it may change upon restarting your PC.