(adsbygoogle = window.adsbygoogle || []).push({}); So I am having trouble finding an addresses bytes. I jumped to an address in IDA Looked in Hex view then i opened up Ccapi Debugger I put the address in "Debugging" And i found the address from that specific Hex thing is. I do not know what to do to test this in Ccapi debugger.. What do i press/Click to test the address given by the hex i found with it?
Also I need to know which bytes would be OFF and ON for example 0x00 0x00 (ON) 0x00 0x00 (OFF). I attemped to press 41 and put SET and GET in the "Offset" part of This debugger
but it freezes me after 5 minutes of GamePlay. If anyone can explain how can i tell which bytes are off and on also if someone can tell me how can i test an address in ccapi Debugger after i found the Hex in the ccapi Debugger. Heres a picture

You must login or register to view this content.

#1 don't use that shitty "debugger" as people call it.
#2 it's been explained to you
#3 what is this for? We might be able to shed some light apon it.

1# Beach was able to use this Debugger to find an address and its bytes
2# It hasn't been explained to me specifically on which would be ON And which are OFF
3# This is for Battlefield 4 , not going to say what its for because these addresses were given to me but I can tell you when I place the 1.17 bytes for this address in an rtm it would turn on another thing when I didn't even Enable it in my rtm

are you grabbing the bytes which are used to set the data in IDA

Yes. As picture shown above.
But in this address its 1.19 bytes compared to 1.17 bytes
Are similar. As the Disable part.
1.17 0x60 0x00 0x00 0x00 - Enable
1.19 - no clue.
1.17 - Disable bytes are in 1.19 as shown in the picture

that is hex, that doesn't show us the PPC. we want to know if you're grabbing the right section of it

You must login or register to view this content. 1.19


You must login or register to view this content. 1.17

In Hex View they both have the same hex.

if you look down, you'll notice there's a few changes between the two functions. This is what I'm trying to explain here but you don't seem to understand that things can change between updates

But that 1.19 address was given to me it has to be right...

You must login or register to view this content.

This also writes the same Hex ^

I'm going to explain this to you like you're a fuckwit

    

void SETHABBIBSHIT(int num) {

    habbibshit = num;

}

let's say this fucking crap is 1.17

    

void SETHABBIBSHIT(int num) {

    illfuckyourmother = true;

    writehabbibshit(num);

}

and this is 1.19. A change happened. make sense? (this isn't what it actually looks like btw, just an example of "CHANGE")