FearLess Cheat Engine

It is possible it gets garbage collected yes. The default behavior is that for each command the mono data collector .net thread attaches, does something, and then detaches. Detaching will release all objects assigned to that thread, including created objects It's possible that between two instructio...

use readmem to store the original bytes { Game : pcsx2.exe Version: Date : 2023-12-25 Author : Pc This script does blah blah blah } [ENABLE] aobscan(MoneyZa,0F 88 ?? ?? ?? ?? E9 ?? ?? ?? ?? 8B 0D 30 9F ?? 01 81 C1 60 0B 00 00 89 C8 C1 E8 0C 8B 04 85 30 ?? ?? ?? BB ?? ?? ?? 30 01 C1 0F 88 ?? ?? ?? ??...

it could be it's this game or an il2cpp issue. But have you tried that code I posted and did it ever not timeout?

And how long does it take between the first mono_object_new and the error?

a jmp far is 14 bytes long so the code that gets relocated to the script needs to be longer as well, and disabling the script and restoring the bytes will require at least 14 bytes as well Also, in cheat engine you can check as template 14 byte jmp and then generate the script, and it'll do most of ...

ok, so it's not normal mono but il2cpp. Likely it's taking more time due to the symbol enum still being done try adding this code first: local timeout=getTickCount()+60000 --1 minute, just making sure you're not freezing forever (adjust if needed) while monoSymbolList.FullyLoaded==false and getTickC...

about mono_object_new crashing, are you sure there's no other functions you're calling inbetween? And is the handle correct ? easiest way to test: in .net info select the class you're interested in and do: a=xxx.CurrentlyDisplayedClass.Handle printf("classhandle=%x",a) b=mono_object_new(a) return pr...

check out [Link]

webroot closes it

in the processlist, select tutorial-i386 or tutorial-x86_64, NOT Cheat Engine 7.5

Which windows version and try different versions of dbghelp

also operating system used and if you compiled it yourself or not, etc...

Tomorrow.
(and the compile it yourself version is always there)

Nerdy: Aaactually.... will result in invalid code as the value in `mov [memoryaddress],value` can only be 32-bits

you'd want to do: or

it's fixed

does the error occur in a newly created thread or in an old thread?

there was a bug where new threads would get the wrong context set on exception