In this case for css, here are screenshots where I demonstrate what I do:What game, and what are you searching for?
- And what have you set the pointerlevel to be?
In this case for css, here are screenshots where I demonstrate what I do:What game, and what are you searching for?
- And what have you set the pointerlevel to be?
In the screenshots that I linked I used health as an example, but I got this issue with most stuff.What are you looking for? Health, Ammo?
Does it explain tho why i get 0 results using a pointer scan after several retries?Make sure that health is interger not float, which I saw you used on your screenshot.
Alright I have made another attempt at this.Sorry for asking... And yes it does.
OKay I see, So if I am to do as you describe then I would check in cheatengine what accesses that address. then open olly, attach it to the process, go to that address by pressing ctrl + g. But after that I dont know exactly what to do. What will I be looking for to find the real address? I guess I would be looking for mov's most of the time but how will I know what instructions to look for exactly and how do i know when I have found the real address.Automatic pointer scanning will not always yield results for you. If I were you, I'd breakpoint the memory address see what accesses it, run a debugger and trace back where the static gets set and where offsets get added
Okay thanks, back to olly it is then. Would you say olly is more reliable for finding addresses than CE? Also, would you be able to find ANY addresses in olly, such as all enemy coordinates etc?When you hit a breakpoint, and execution is paused, the address of the health (or whatever), is in the stack and accessed. Now you are going to go backwards. You'll look what register held the address and see how it got there. Practise and play around with olly in those matters and you'll get the hang of it.
Yes, you can search for values in memory the same way you can with CE. Ollydbg is just more of a personal preference for me, although I'm aware of CE has a debugger aswell, with olly you still have tons of more options in that field.Okay thanks, back to olly it is then. Would you say olly is more reliable for finding addresses than CE? Also, would you be able to find ANY addresses in olly, such as all enemy coordinates etc?
How would you go on about finding enemy coords in CE? I am not asking for a step by step tutorial but just general guidelines.Hmm... Depends. I use OllyDBG when I need to make classes that I can use ReClass. You could find enemy cords in OllyDBG I would use CE though.
So I checked it out and it seems you are entirely correct."client.dll"+0076EA9C -> 086C1F00
[086C1F00+C] -> 1F579A48
1F579A48+154 = 1F579B9C
struct PlayerInfo
{
char name[32];
int team;
int hp;
float x;
float y;
float z;
float ang1;
float ang2;
float ang3;
};
size: 64 bytes.
Offset between players structures: 140.
Okay, cant wait !That is because the engine doesn't render / send you the position of the enemies if their not visible or too far away.
[EDIT]: Oh and yeah i can show you how i did it tommorow probably just respond to this message with a quote and I'll definetly remember it.
Okay thanks, sounds good. Is there any reason you set pointer level to 2? How do you set it anyway, is it the "Max Level" field that you are talking about?Ok so basicly the first thing i did was search for my own HP, and then i would play around with the values, and trying to hurt myself etc etc, restarting the round etc. Trimming the addresses abit down.
- Now you'll have multiple addresses pointing to your health.
Then i basicly do a pointerscan on all of those addresses one by one, most of them will not return any pointer paths (set your pointerlevel to 2.)
Then when i find an address that has multiple pointer paths I'll simply double-click all of them, so that Cheat Engine stores the pointer paths. I store all pointer paths leading to the address (without restarting the game). I do that with all the addresses pointing to the health.
Then when i restart the game I'll see all the pointers still pointing to my own HP. And I'll simply cut the rest out. - Think logical when adding pointer paths. Example your HP is prolly not shaderxapi.dll + offset. It's more likely to be something in the client.dll , or engine.dll or matsystem.dll. Depending on what you're looking for.
I hope this helps, it's hard to explain or recreate as it takes some time but it's worth it in the end.
[EDIT]:
Woops and when I've found these addresses you add that address to a program called ReClass, then try making it like 1024 bytes bigger. It'll give you a bigger overview, and try using your calculator to go a few bytes back and add to ReClass from that address. Then it's basicly just puzzling around untill you find something that makes sense. E.g you see an address having the value 1.293993 it's probably not an integer but a float, you'll get the idea trust me.