Project! Lets port sph4ck's pyexternalbox to MW3

[c0z3n]

Also c0z3n, it would be greatly appreciated if you removed the link to the document with the offsets or at least, remove where you got the offset from because it is against the rules to post links to another hacking forum.

My bad, i'll remove the link to the offset table from this thread. Although, I would argue that citing sources in a resource is far different from just posting links to another forum's threads.

Also, the SENSITVITY_PTR_16 offset can be found by first finding the sensitivity DVAR address (eg. changing the sensitivity and scanning for values) and then checking what writes to the address. Click on More Information and it will come up something like this:
mov [edi+10],eax

Do a 4 byte scan for the value stored in the EDI register and the pointer you are looking for is in the 0xA00000-0xAA0000.

Wow, thanks for the info! sensitivity was one of the ones I was having trouble with. We'd love to have you join us, if you're up to contributing to the code at all =)

Also, while we're kinda on the subject, what scanner are you using? I've got Tsearch and CE, but I'm guessing there might be others available. Also, has anybody had any issues with VAC bans using CE or Tsearch?

[aIW|Convery]

Also, while we're kinda on the subject, what scanner are you using? I've got Tsearch and CE, but I'm guessing there might be others available. Also, has anybody had any issues with VAC bans using CE or Tsearch?

I'm pretty sure Twitter claimed that VAC was searching for CE in his rank hack release thread. So I'll just make my own in 5 min that just outputs the results to a file rather than a GUI, sooo much faster :3 (got to love the high IOPs on SSDs <3)

[[MPGH]master131]

Also, while we're kinda on the subject, what scanner are you using? I've got Tsearch and CE, but I'm guessing there might be others available. Also, has anybody had any issues with VAC bans using CE or Tsearch?

Not using any scanners. I haven't run any tools/hacks on MW3 yet apart from Olly. :3 And that example was from MW2 but since the Engine is pretty similar (or the same really) then it should be the same. And sure, I'll be happy to join the team. I don't know alot of Python though but I still understand the syntax sorta.

[[MPGH]master131]

Guess what? I'm doing it already.

Thanks to the structs/offset thread, I already have a version working, but not all features yet. I merged both MW2 an BO versions.

My only concern is that VAC now knows how to scan it. So I will be publishing no more than sources.

Sph4ck

Looks like sph4ck is already working on this :3

/bump

[c0z3n]

Affirmative. He was quick to respond on that other thread.
And as long as we're on the subject, here's the reply I posted on that same thread two days ago:

This reply literally made me laugh out loud, you're the best.

I was going to try to contact you last night when I posted this thread, but I decided to wait until the morning, and you bloody beat me to it!

If you're up for it, I would be absolutely honored to contribute. Just tell me what you've got left to work on. I'm pretty familiar with the code from the mw2 version at this point, and would be excited to get a mw3 version going. If you'd prefer, I can set up a private repo, so the source won't be available just yet.

Seriously though, you're awesome.

I've also pm'd him with some code implementing more features i'm willing to contribute, but have yet to hear back from him on that front.

I'd link to that thread but I'm not allowed.

[[MPGH]master131]

I'd link to that thread but I'm not allowed.

Doesn't matter, at least I know what thread you're referring to anyway.

[c0z3n]

True enough, but I'm the kind of person who likes to cite a source with more than a name whenever possible, so anybody who comes along can inform themselves as well as they see fit.

[c0z3n]

Just wanted to post a quick update, so people don't think this has died.

I have been in contact with sph4ck and we're trying to get a version working. we're currently using a private repository, because as long as i'm working on his hack with him, i'd like to respect his plans for it. The reason I mirrored the code in the first place was because I had been led to believe that he wouldn't be very active in working on it, which is clearly not the case.

As such, I personally won't be releasing any code on the google code page I set up, at least until after the source is released anyways.

More updates will follow as more news is available

[yearzero21]

Hi there, just wanted to check in on this project. Any developments? Best of luck.

[DrFifty]

Bull crap there are heaps of hacks out there, i was playing with a guy (DEV PLEX) 4 days ago and he was hacking bad, the red boxes were just jumping from player to player even through walls. Its gonna be just like MW2 im afraid.

[aIW|Convery]

the red boxes were just jumping from player to player even through walls.

Daaamn.. that sounds exactly like the hack I was going to post on MPGH.. creepy..

[weed-star]

why do you even want to change that phyton version to mw3 ??????

i already tried it with the the older mw2 c++ version to adapt it to mw3 but i'm not the kind of programmer that can solve all problems...

here u have how far i came:

[trenth]

Sph4ck said that his hack was "undetected" if you used older versions of Python.

Good luck,

[chickychickson]

i would not recommend to use this old c++ file. it has been sent in a few 100 times for sure. and i dont know if adjusting a few offsets and maybe the classes and rpm would be enough to go for sure its safe for a few weeks....

i wouldnt bet on it. but hey you are free to do it. its not that hard to do, if you know anything about programming you should be able to bring it to work.