If I asked a computer science professor what the difference is between black and green addresses in CE, what would he tell me?Ģ. Anyway, I'm sure that's completely out of scope for these forums (unless anyone here gets off on stuff like this - I would love to learn more.)ġ. It looks more complicated, but the ideas are the same. I looked up virtual memory layouts on Windows. black addresses are heap and stack variables, and green variables are everything else. black addresses are heap addresses and green addresses are everything else.Ģ. I know this isn't quite correct for Win32, but I'm sure there must be parallels.
I never learned the details of how shared code is stored in memory, but I assume it has its own address space which somehow gets "tacked on" to the virtual space of other processes. I also see offsets into other process's address spaces, so CE probably follows dynamically linked references to other processes. BSS segment: kernel-initialized statics/globals data segment: pre-initialized statics/globalsĢ. I know more about Linux than Windows, but if I had to take a guess at what static and dynamic means if CE were a Linux application, I would say that CE reads the following segments of a process's virtual address space:ġ. If you read CE tutorials, you'll read that black addresses are dynamic and green are static, but what does that really mean? If you followed the included cheat engine tutorial (that comes with CE) with the hackme file then you should be able to get the basics down.Posted: Fri 2:15 pm Post subject: Black vs Green Addresses
There are shitloads of tutorials for basic scanning and manipulation, don't expect anyone to make you (yet another) one for such a simple thing that's been covered so many times. If you don't understand basic scanning, then AOB scanning is probably too advanced for you at the moment. That's where you'll get your array of bytes, from that and the surrounding instructions (one line of code is usually not enough to get a unique AOB to scan for). View that instruction in the disassembler and you'll see the hex bytes that represent that instruction(s).
Then right-click it and do 'find what writes this address', (one of) the result(s) should be the piece of code (the bytes/opcode) that writes or changes the health value. Say you find the value for your health so you can change it, etc. You need to understand basic searching to find simple values. Attention to detail is important in gamehacking. Doubtful that you aren't capable of understanding it. Ryan,thats nice but im too young to understand it all, does any1 know a simpler way.
0 kommentar(er)
