Cheat Engine

[justa_dude]

Howdy,

I've been playing w/ CE's Mono stuff a bit the last couple of days, and I have some questions. I can understand why CE might not automatically enable Mono features when it detects a mono game.... the process could potentially be detected, etc. But could we perhaps add a flag attribute to the table files to indicate that they depend on Mono and enable automatically or something? I'm sure it could be scripted in the table's lua script, but I pretty much always click no when CE asks me if I want to run a table's Lua script.

Also, I find myself having to do stuff like:

[Dark Byte]

the mono features are intrusive and when used incorrectly can cause the target to crash.
e.g. using structure dissect on an address not belonging to a class, will often cause a crash (when it's enabled)

about the label thing nit sure, i thought call Someclass:SomeFunc should just work. Tried putting it between quotes like call "Someclass:SomeFunc" ?

Mono features will temporarily disable themself as long as there is a chance of a reakpoint. (when the game is running and all breakpoints are gone the features will work again)
the reason for this is because the mono features inject a running thread in the target and communicate with it. When an address is converted to string, that thread is called to return a string for it(e. g in the disassembler or other code related functions) and ce will then wait for the result
when a breakpoint hits, that thread is frozen and can't respond. so when ce would ask for a string, it'd wait forever.
and due to multithreading you can't predict when a breakpoint hits. e.g. when a string is half transfered to ce a breakpoint could trigger, making ce wait for the rest of the string

ctrl+space is the sbortcut you need

[justa_dude]

Thanks, DB. You're the best.

Wrapping names in quotes did the trick. Going to tattoo ctrl+space to my wrist so I don't have to ask a third time.