WeaponMgr Signature

[R4v0r]

Since mine did a fucked up job, I'm asking you guyes IF any of you have an CANA WeaponMgr sig, via PM or whatever.
This code won't be used in pub hacks. My own PVT hack.
I know how to find the address manually but I fail this time at logging it. I can provide correct CANA weaponmgr addie as proof.

THanks!

[matypatty]

Since mine did a fucked up job, I'm asking you guyes IF any of you have an CANA WeaponMgr sig, via PM or whatever.
This code won't be used in pub hacks. My own PVT hack.
I know how to find the address manually but I fail this time at logging it. I can provide correct CANA weaponmgr addie as proof.

THanks!

if you can find it manually, just find it and compare bytes with previous patches.
For example:
Patch one
FF DD FF BB FF CC
Patch two
FF AA FF BB FF CC
Patch three
FF AA FF BB FF CC

your sig would be:
FF 00 FF BB FF CC
mask:
x?xxxx

with the ? indicating the non important bytes(ones that are not consistent throughout all patches)

bad explanation but you should get the general idea.

[R3d_L1n3]

if you can find it manually, just find it and compare bytes with previous patches.
For example:
Patch one
FF DD FF BB FF CC
Patch two
FF AA FF BB FF CC
Patch three
FF AA FF BB FF CC

your sig would be:
FF 00 FF BB FF CC
mask:
x?xxxx

with the ? indicating the non important bytes(ones that are not consistent throughout all patches)

bad explanation but you should get the general idea.

I Already made topic about that , and he did same but it aint working for him

my suggest search on ida an find other place :S

[R4v0r]

if you can find it manually, just find it and compare bytes with previous patches.
For example:
Patch one
FF DD FF BB FF CC
Patch two
FF AA FF BB FF CC
Patch three
FF AA FF BB FF CC

your sig would be:
FF 00 FF BB FF CC
mask:
x?xxxx

with the ? indicating the non important bytes(ones that are not consistent throughout all patches)

bad explanation but you should get the general idea.

Already tried like, R3d_L1n3 sed, I came up with:

"\x8B\x0D\x00\x00\x87\x37\x8D\x47\x01\x50\x89\x44\x24\x24\x8B\x44", "xx??xxxxxxxxxxxx"

but not working..

[Ch40zz-C0d3r]

https://www.mpgh.net/forum/207-combat...ignatures.html
Use that knowledge and please read my last post for an update which simplifies everything a bit!
Also make sure to use the right start offset and size, not just code size like most c&p people do..

[Skaterforeva1]

Why not just use sig maker plugin?

[arun823]

Why not just use sig maker plugin?

Why would you use a sig maker plugin when you can make the sig scan with your own brain, besides the sig maker plugins don't ALWAYS work.

Also @R4v0r, just get the WeaponMgr address from the EU version and look it up in Cshell, then make the sig scan off of the EU version.

[R4v0r]

Why would you use a sig maker plugin when you can make the sig scan with your own brain, besides the sig maker plugins don't ALWAYS work.

Also @R4v0r, just get the WeaponMgr address from the EU version and look it up in Cshell, then make the sig scan off of the EU version.

I don't think that will work, signatures from EU are different to NA - BR - RU, since they all had the awesome patch which fucked up everyone, EU didn't have it yet...

[arun823]

I don't think that will work, signatures from EU are different to NA - BR - RU, since they all had the awesome patch which fucked up everyone, EU didn't have it yet...

Wut, lmao, I got my sig scan after the NA patch from EU, works fine. You have no idea what you're talking about, just create a sig scan for the address which points to the address you want and then from there create a static offset. Not that hard.

[R4v0r]

Thanks all for the help, I fixed it. My sig was correct all the time, it was the register problem, which I fixed