Cheat Engine

user5594 · Last edited by user5594 on Sat Sep 12, 2015 10:46 pm; edited 1 time in total

I made a Lua script in the previous version of Minecraft simply by nopping the line "comiss xmm6,[rbx+0C]" which accessed some sort of function that decided how close a block was to breaking.
This method no longer works in the newest version but I have a solution (not 100% how to implement it though).
Basically there's a FLOAT value that's "0" when the block isn't touched, and as you start smacking it that value counts up. When it reaches "1" it breaks.

How exactly can I set that value equal to 1 using a Lua script?
I've tried to use the mov register on [rdi+0C] but it always seems to crash the game or not do anything. Also, what's this about getting the correct amount of bytes? Do I always have to count how much each register takes up? It's a little confusing.

Thanks!

Zanzer · Posted: Fri Sep 11, 2015 9:41 pm Post subject:

Not entirely sure why you're using Lua to NOP or change assembly bytes...
You want to replace both the instruction and the one before it.
Those currently contain the bytes: F3 0F 58 5F 0C F3 0F 11 5F 0C
You should replace those bytes with: C7 47 0C 00 00 80 3F 90 90 90
In case you're wondering, those bytes represent:

user5594 · Posted: Sat Sep 12, 2015 12:11 am Post subject:

Rydian · Posted: Sat Sep 12, 2015 1:28 am Post subject:

So that movss [rdi++0C],xmm3, do an AOB injection template on it.

Then in the script, have it do this.

movss [rdi++0C],xmm3 //Original move, which is untouched.
mov [rdi++0C] (Float)1.0 //Overwrite the result with 1.0.

CE will understand (Float)1.0 and convert it to the hex equivalent for you, so you'll be moving that hardcoded float into that address every time right after the block's damage value is added.

I still haven't upgraded to W10, but that should work and it's how I'd approach it nowadays. You may need to set it to like, 0.999 instead depending on how the engine works though. Not sure.

user5594 · Posted: Sat Sep 12, 2015 2:34 am Post subject:

Rydian · Posted: Sat Sep 12, 2015 2:50 am Post subject:

In this case you can do that since movss doesn't modify the stack, it won't really matter anyways since even though the address will be set to the normal value, it will get overwritten before anything can check on it.

(I just can't make a template for it since I'm not on W10 yet.)

user5594 · Posted: Sat Sep 12, 2015 1:12 pm Post subject:

OK, Instant Dig is working with that code (thanks guys) however when the script is disabled, it doesn't replace with the original code (the line with (float)1.0 remains under the 1st line in the disassembler)

Zanzer · Posted: Sat Sep 12, 2015 1:32 pm Post subject:

Did you give mine a go?

user5594 · Posted: Sat Sep 12, 2015 2:38 pm Post subject:

Rydian · Posted: Sat Sep 12, 2015 9:28 pm Post subject:

Are your sure yours was using the template correctly?

As in start from the cheat table and then AOB injection templates and then insert the line I said for ease of use.

user5594 · Posted: Sat Sep 12, 2015 9:42 pm Post subject:

Rydian · Posted: Sat Sep 12, 2015 10:31 pm Post subject:

With the AOB injection template you don't need to count nops or anything.

it really looks like you didn't use the AOB injection template, because it includes more than you had there.

With the AOB injection template it puts a copy of the original code at the injected location (code:) and you can add/remove as you see fit without worrying about counting bytes because the template takes care of that in the injection section for you.

user5594 · Posted: Sat Sep 12, 2015 10:34 pm Post subject:

Rydian · Posted: Sat Sep 12, 2015 11:18 pm Post subject:

Sometimes the code: section will have more than what you targeted because it needs a certain number of bytes for the jump, so it may need to copy a few shorter instructions instead of just one longer one.