| PegPeregoGaucho | yes |
| Deleted User | do you know a little C or C++? |
| yarnfang | Basics. |
| Deleted User | structs? |
| Deleted User | or classes |
| Deleted User | because it depends on how they store it |
| yarnfang | You mean arrays and such? |
| yarnfang | Yeh. |
| Deleted User | what i'd do is just look for the code that changes the address. it's 'find what writes this address' or something along those lines |
| Deleted User | but then you'd have to figure out how to find a static address based on the x86 assembly code |
| yarnfang | Yeah, that's what I have no idea how to do o__o |
| Deleted User | the thing is that they might not store a pointer to the helmet count directly but to a structure that contains the count |
| Deleted User | ```cpp
struct {
int health;
int helmet_count;
}
``` |
| Deleted User | these two things would be directly after each other in memory |
| Deleted User | and if they only store a pointer to the object then you wouldn't find a pointer the helmet count directly |
| yarnfang | Oh, and I assume that's connected to why the addresses always are 030??178 for helmets? |
| Deleted User | might be |
| Deleted User | yeah |
| Deleted User | so it looks like it's a huge structure where the helmets would be at an offset of 0x?178 from the beginning |
| Deleted User | but you can't really tell it just from the address |