Cheat Engine

[DeadlySoul]

Lets see where to start..

I'm trying to make a monster vacuum hack for the game "Secrets of Grindea".

So far I have:
-the base address for the coordinate of 1 monsters x and y position
-the base address for the coordinate of my characters x and y position
-the base address that accesses every monsters position (i think)

I searched for the base addresses via pointer scan since the addresses change every 10 - 20 minutes/the game is restarted or by re-entering the map.

I stumbled on a cheat template from someone else that has a monster vac and tried to change the values to my own but I'm getting an error.

Here is what I have so far:

[DeadlySoul]

After reading through a few threads and tutorials about 'Auto Assembly' and the 'Memory Viewer', I now understand more than I have when I first started this thread (especially about Memory Viewer). I'm also going to take a few steps back and start small instead of jumping to something that I'm not that good with (yet).

So instead of making a 'Monster Vac' that teleports every enemy on the current map, in front of me, I'm first trying to 'Vac'/teleport only the X-position of every enemy to a position I specified. Once it's working, I'll do the same with the Y-position, then finally after I got that working, I'll try to 'Vac'/teleport the enemies to the chars current position (+/- a few coords off, so that they get vac'ed directly in front of me).

But for some reason the Auto Assemble script I have isn't doing anything ):
I'm pretty sure I have the right instruction/opcode, unless I have to dig deeper (which I'm not sure how to do).

Here's an Imgur album of the steps I take to get the (what I think is) right instruction/opcode: imgur . com/a/jX4wO

And here's the AA script I have that I puzzled together from SteveAndrew's Plants vs. Zombies 'Zombie Vac':

[++METHOS]

I would recommend starting over. The FIRST thing that you should do is find one of the coordinates for your hero player. When you have narrowed down your results, you should CHECK them, one by one, to make sure that you are working with the correct set of coordinates. The way I check them:

1. Change the coordinate value to make sure that the hero character will actually teleport to that location and stay there.
2. Teleport across the map a couple of times to make sure that this particular set of coordinates will allow the hero character to teleport through objects (not all of them will). A good way to check this is by changing the coordinate value and seeing if it actually changes to that inputted value (or very close)...if the value changes, but only half-way, for example, then it's no good.

Once I have determined that I have the correct coordinate (X), I will add the other coordinates (Y & Z) to my cheat table by copying the first coordinate (X) and pasting it back in to the table two times (giving a total of 3 addresses), then, renaming the two added addresses and adjusting their offset accordingly since they are usually all just 4 bytes apart.

Now, once you have done that, THEN you can proceed to 'find what accesses' for your base coordinate (X).

Note: If you prefer to look for your (Y) coordinate first, you can do that, instead. Just remember, when you check 'find what accesses', you only need to do that for your base coordinate (X).

In the debugger window, if you check, you may see that several instructions are accessing multiple addresses. You will also see that some of the instructions are being accessed many times per second (some more than others). What we want to do is use one of the instructions that is being accessed the most, that also accesses other addresses (enemy coordinates). Once you have chosen one, you can check it in memory viewer to ensure that the addresses that are being accessed are ONLY coordinate addresses and not mixed with coordinates AND non-coordinate addresses that could crash the game if altered. In your game, you could see that ONLY coordinate addresses were being accessed because of the value and how many addresses there were relative to the characters in-game.

From here, you can write a simple script to test if this instruction is going to work well for you, or, you can just NOP the instruction to see what happens. This can give you some idea about whether or not this particular instruction is going to work or not. You may also find some cool effects that you can utilize for making other cheats. Once you have determined that the instruction will work, you may proceed with writing your teleport/vac script. I can help you with that. If you determine that this particular instruction will not be suitable, move on to the next viable instruction in your debugger list and repeat the steps above.

I can tell you, that, unless you are able to find instructions that are exclusive to your hero character and/or exclusive to enemy characters, you WILL have to use a filter to separate your hero character from the enemy characters and vice versa. That being said, if you are not familiar with how to dissect data structures, you WILL need to learn.

[DeadlySoul]

Alright so I have the address of my characters X/Y(/Z) coordinates. When I change the Value, my character teleports and I can move. I can even teleport outside some of the boundaries or borders and just walk on air or on water, but I can't teleport directly onto some objects. It will push me directly besides them.

Gif example: gfycat . com/MajesticGrotesqueHamadryad
Note: You can resize the gif by dragging it

Now when I right click the X-Address of my character and select 'Find out what accesses this address', I get the following instructions:

[++METHOS]

[DeadlySoul]

[++METHOS]

[lamafao]

Is that how it looks now? I have ce6.3 but it doesn't look like that for me, maybe i have an older version.

Did you try looking at the instructions with 4321 or 1243+ count? I think that's what you want?

[DeadlySoul]

[++METHOS]

[DeadlySoul]

[++METHOS]

Yes...but like I said, you can change the instruction.

I did not spend much time on it, but it is good for a reference and to tackle structure dissection.

[lamafao]

[++METHOS]

Yes. You can check the register values by setting a breakpoint on the instruction (even better, set up a filter first and set a breakpoint in your codecave). You can use a secondary instruction that is exclusive to hero and compare the value of that register in your primary script for filtering. You can compare against pointer addresses. You can use data structures, look inside pointer trees, compare multiple values, compare multiple structures with structure spider and even create your own ID etc..

[DeadlySoul]

Data/Structure Dissection seems to be pretty simple, at least when it's something basic. I'll still have to look into the more advanced stuff like the ones you listed:
-comparing against pointer addresses
-looking inside pointer trees
-comparing multiple structures with structure spider
-creating my own ID
For now I'll concentrate on the more simpler stuff. I'm afraid I'll get confused and forget something or screw something up if I try to learn too much at once, but then again, screwing up is part of learning :D

1 thing I never checked is if something else accesses the instruction besides hero and enemies.. well I did somewhat, but after checking out your script I noticed that even some skills get vac'ed which I never considered checking..
It's actually pretty convenient but would probably be better to filter out/use a different instruction and make it a separate code entry.