Pointers Guide
Why your address stops working after restarting the game, and how pointers fix it. See the Scanning guide and Value types to find values first.
Why addresses change
When you scan and find an address like 0x12345678, that is where the value lives this run. After you close and reopen the game, Windows may load it at a different base address (ASLR) and the game may allocate data differently. So 0x12345678 might no longer hold health—it could be unused or something else. To get a cheat that works every time, you need a path to the value that stays valid: a pointer chain.
What is a pointer?
A pointer is an address that holds another address. The game might store “health” at an address that is computed from a base (e.g. module + offset) plus one or more pointer levels. CE’s “Pointer scan” finds these chains: base + offset → next address + offset → … → final address where the value is. That chain is usually stable across restarts.
How to do a pointer scan
Find the value’s address with a normal scan and add it to the list. Right-click the address → “Pointer scan for this address.” Set options (max level, max offset; start with defaults). Save the .PTR file when asked. When the scan finishes, you get a list of pointer paths. Restart the game, re-attach, and use “Rescan pointerlist” (or load the .PTR and rescan) to see which pointers still resolve to the correct address. Keep the ones that work and add one to your table as a pointer.
Adding a pointer to the table
When you have a valid pointer from the scan, add it via “Add address manually” → check “Pointer” and enter the path (or from the pointer scan window, add to address list). The table will show the pointer and the current address it resolves to. When you load the table next time and attach to the process, CE will resolve the pointer again—so the same cheat works across restarts.
Tips
Pointer scans can produce huge files and take time. Use a reasonable max level (e.g. 4–5) and max offset. Prefer pointers whose base is the main .exe or a main DLL so they’re less likely to change. See Tips and Troubleshooting if the pointer scan fails or no pointers survive rescan.