Cheat Engine

[cooleko]

I had to change lines of code to find a unique AOB. The AOB I found is here:

[++METHOS]

First of all, why are you wanting to do this?

As you say, just using an offset will work:

[cooleko]

The instruction i want to inject on doesnt generate an AOB. It just happens that the instruction a few lines up is unique and generates an AOB.

The game is also mono, so I tried to inject at "Weapon:UpdateCharging+67", which always points to my instruction I want to inject at, but the script doesnt load for new games, so I guess mono doesn't work that way (even though I can search memory for "Weapon:UpdateCharging+67" and find it every time).

This script works for the game I loaded, but wont work for any other games. even though the generated script is 100% the same for each game load, it doesn't carry over, which leads me to believe that a symbol is getting registered for an address rather than "Weapon:UpdateCharging+67" generically

[panraven]

Try
1) use a label to adjust the offset in the long (in order to be sure it is unique) aob pattern case:

[++METHOS]

[cooleko]

Thanks for the advice. However, I still don't know how to physically implement the Symbol offset. I was able to get the script working using the AOBScanRegion using the mono feature symbols.

Is there a way to force the table to activate mono features, so the user doesn't have to do it?

To assist me in understanding the Symbol offset procedure
Can you explain the relationship between the AOBScan symbol which places the symbol at the address of the first byte, the code that is overwritten by the Registersymbol(code), and the required bytes in the disable.

Then, can you explain how the relationship between those three changes when the symbol is referenced with an offset?

I think my biggest hurdle is I'm not 100% sure on the relationships and have been simply relying on the template to ensure that the relationships are established correctly.

[++METHOS]

It's pretty straightforward. The AOBScan/AOBScanModule that contains your AOB signature is used for the sole purpose of locating the proper segment of code where you want your injection point to be. But, since your signature will be slightly off because it starts above your actual injection point, you'll have to jump over the necessary amount of bytes so that CE injects your code at the proper location. You only have to specify this difference at two locations in your script, as I noted in my previous post.

All you have to do is highlight your desired instruction that you want to manipulate, and let CE build a script for you, automatically, as you would normally do. Then, after you see that it has failed, expand on the signature by adding the necessary bytes like you have shown above. After you do that, it's just a matter of adding the +19 offset (or whatever it is) to the two spots that need it and you're done.

You can check your AOB signature by scanning for it in CE to make sure that it is unique. Be sure to change your scan settings to array of byte and make sure that the 'writable' box is filled-in with a square block. Do this while your script is NOT activated. After you scan for your signature, you'll be able to see if it is unique if you have only 1 result show up in the list.

It is also good to make a habit of incorporating wildcard entries in to your signature for the reasons explained in my previous post. Be sure to check your signature for uniqueness again, after adding any wildcards.

Does that answer your question? I don't want to just write your script for you because it won't help you as much. It's much better for you to do it yourself so that you understand what you are changing and why.

[panraven]

For this

[cooleko]

I greatly appreciate all of the help. I now understand how to use mono features to narrow down a scan region (using aobscanregion) as well as use an offset aob scan to catch a unique aob scan that is at a different address than the injection point. I also got the auto activate mono features script to work. So for all of the learning I did with great assistance, I thank everyone.

One last question, if the offset was negative, would Symbol-Offset work? I know in cheat engine, sometimes negative offsets are okay, and sometimes they are not. I'll test when it occurs, but until then I would still like to know just for completeness!

To recap, in case anyone finds this thread later and doesnt understand the exceptional explanations provided above without an example, I will show how I applied their advice to my specific problem to reach a solution.

First things first, the code:
I wanted to reset reload timers for missiles, because they were 30 seconds, and that is just too long! The instruction "movss [rsi+0000009C],xmm15" writes the accumulated time since last shot fired.

[mgr.inz.Player]

[++METHOS]

cooleko-
Good work.