MPGHThe Dark Arts
RegisterLog in

memcpy? lol wut.

Posts 1–9 of 9 · Page 1 of 1
memcpy? lol wut.
Hey guys, it's kinda wierd for me to be here but I was wondering what this does.

memcpy((PBYTE)addSuperBullets, "\x33\xC0\x90", 3);

What does "\x33\xC0\x90" do? Like I know it's a 3 byte array and memcpy copies an array of bytes to an address but why those values?
#1 ·
These r the default bytes i think (im EU and idk which addy u mean).
When u use memcpy to HACK than u usually use the bytes x90. This is called NOP which stands for NoOPeration. This means when the Bullet is hit the wall do NOTHING. So u shoot trhough. I hope i could help u.
#2 ·
I know what NOP means. I have done reverse engineering before :3 Alrighties, thanks.

But I still don't understand this:
memcpy((PBYTE)addSuperBullets, "\x33\xC0\x90", 3); //ON
memcpy((PBYTE)addSuperBullets, "\x0F\x94\xC0", 3); //OFF

The byte arrays are completely different values.
#3 · edited ·
Than its adifferent addy than mine in EU sry IDK. This works different.
#4 ·
Hmmm, alright thanks for helping anyway. *cough* Where is ᴺᴼᴼᴮ when you need him.
#5 ·
Ask @mmbob, He's the one who found super bullets. The fact that you can NOP the three bytes and still have the same result is just by chance.
#6 ·
\x33\xC0\x90 are the bytes for "xor eax, eax; nop"
You need to return 0 from the intersect callback function to tell the engine that the object it gave you is not one that you want to hit. xor eax, eax makes eax (the return value) zero.
#7 ·
Quote Originally Posted by mmbob View Post
\x33\xC0\x90 are the bytes for "xor eax, eax; nop"
You need to return 0 from the intersect callback function to tell the engine that the object it gave you is not one that you want to hit. xor eax, eax makes eax (the return value) zero.
So when u NOP it it must return 0 too or?
#8 ·
Oh so they're assembly bytes. I was thinking that they might've been when I woke up this morning. :3 Thanks mmbob.
#9 ·
Posts 1–9 of 9 · Page 1 of 1

Post a Reply

Tags for this Thread

None

Talk with us