Cheat Engine

[HenryEx]

I'm working on a table that heavily relies on mono features atm. And while it's a welcome change in CE 7.6 that some method invokes don't just crash the game anymore (no more tedious hooking of game functions and firing methods in asm), i've noticed that mono features are also much, much slower than in CE 7.5.

It's not just activating mono features - which was near instant in 7.5 and seems to take a good 1.5 seconds in 7.6. I automate setting up symbols to methods i use in scripts, and there's a marked increase in runtime when i test them side-by-side.

This is my setup log on CE 7.5.

[Dark Byte]

Not sure about the speed, stability does cost some performance. But you can now split up the workload in different threads without blocking, though not sure if the bottleneck here is lua or the queries. (if lua, no improvement)

for better speed, if you know the image, you can use mono_image_findClass or mono_image_findClassSlow for the ones with a + in the name, to find the specific class, and then use mono_class_findMethod to get the method

is the target il2cpp ?

[HenryEx]

The target is not il2cpp, just regular mono thankfully.

I'll have to take a look at monoscript when i'm home, at work currently. This is a little off-topic, but i'm not really a programmer, so i can have some questions that might seem basic.

As far as i understand, and from googling, Methods are game funcions and Fields are the data they work on - these are collected in Classes. Several Classes can further be grouped under a Namespace (most games don't, so it's often blank, except for external libraries used).

Then above that seem to be Images and Assemblies. I'm guessing the Assembly is the .dll that the relevant code is found in (usually Assembly-CSharp.dll, the thing you open in dnSpy etc.).
What then, is the Image? How do i find it? Is it only addressed via memory or can you find it with a string like with classes? Can i assume that all classes in a namespace share the same Image?

Would of course be cool if i could skip a few steps when bulk-processing methods like that.

[HenryEx]

Had a look at it and rewrote my script to fetch the image for Assembly-CSharp.dll, and just reuse that with manual calling of the functions you suggested. I'm hoping that image addresses don't change and that there aren't multiple images floating around for a given assembly.

That did give a substantial speed boost, for both versions. It really seems to be the monohandler, and less the Lua side of the code that slows things down so heavily. (see the test at the end)

Old CE 7.5

[Dark Byte]

It seems I released CE's lua without optimization enabled

try this dll: https://cheatengine.org/download/lua53-ce76.zip

let me know the statistics

[HenryEx]

That DLL seems to work a lot better. On the getAssemblyImage function test from above, it performs even better than CE7.5.