Please Help

[hacker1.6]

I hacked Maple Story, so I do know a little about hacking. I got OpSearch and .Net. I got the sig from the sticky, and put it in. So I saw:
Commander = dwBF2142Base + 0x18BAB0
I get the base part. (I think)
I got OllyDbg, and went into the executable modules (or something like that)and looked at the base for Battlefield 2142. It was 00400000. Am I supposed to run up Battlefield 2142 and then look at the base for it? Second what is the dw?
Commander = dwBF2142Base + 0x18BAB0
I was thinking dword meaning 4 bits? But what does that have to do with it? And what do I do with the code? I went to the Battlefield 2 forum and went to the sticky called
Tutorials. I looked at them all (That is, the ones that let me download. Most of them don't work)and I learned only a little bit, but sadly not enough to help me. Sorry I’m a noob at hacking Battlefield games. I understand allot, because I hacked Maple story. But Maple story seems quite different. If I can get this to work I will forever be in dept for who helped me!

Thanks big time to whoever helps me,
Hacker1.6
P.S. I am using the real game, and not the demo.

[Spontaneous]

Yes the base is 400000. And yes the dw is for dword. It just helps us using c++ that we read the base address as a dword value so in our code, we put the base address in dwBF2142Base.

There are no commander tuts available here. You can goto battlecoders.com and there is a commander tut there.

[hacker1.6]

Thanks I will look there now.
Also if any one would like to walk me through step by step through AIM (Or any Instant Messenger. I will get it) they would be like a god to me! If some one would like to say so and you will be my master.
Edit:
I enabled the debugger and then tried the auto hack for Tsearch, but the auto hack button is grayed out and not clickable. I am following this:
http://www.mpcforum.com/showthread.php?t=96339&highlight=Debuging
It says if I do it I can do the auto hack, but when I double click BF2142.exe in the process list both the cheat engine and BF2142.exe does not respond. They both lock up and I have to turn off the computer.
Big Thanks in Return,
Hacker1.6
P.S. I am following this to do the comander hack:
http://www.battlecoders.com/forum/index.php?showtopic=814

[Spontaneous]

Best way to reset the debug port is a built in feature in Winject. Do not do the cheat engine way as it is too much work. With winject, you just click 2 buttons and its reset.

[Sparten]

Best way around the debug port is to use a patch thats not allowed to be talked about on mpc, as long as PB is not scanning it shouldnt be a problem.

[dreakoth]

sounds nifty sparten, I think imho that the easiest way is to use that batch file that i found, think it was linked off the bf2 tut sticky "HelioS-Debug-Reset-v1.0" nice and simple - u make it run when u boot olly, and u never even have to think about it anymore ;)

[hacker1.6]

Hey Spontaneous may I ask what two buttons you push?
Edit:
I read the read me and found this:

[minime.dll]
Winject currently includes only one dll to inject: minime.dll
You inject minime.dll INTO target process you wish to debug.
It only does 2 things:

1) It patches Thread Information Block (TIB) which will "disable" IsDebuggerPresent() API from Kernel32.dll
and also direct TIB lookup with inline asm (thanks test0r for cleaner solution :)

2) It hijacks GetThreadContext() API from Kernel32.dll to always return fake values for debug-registers.
You can use Hardware breakpoints with your debugger (again) and they are not detected.

TIP: You might want to rename minime.dll to some random name because after a while it is easy to detect by name from loaded modules.

Should I inject it into the game? Would it finally let me auto hack? Do I inject it into the game itself while it's running or into some file?

Or should I try looking up in the procces info section and hit reset debug like this:
http://www.mpcforum.com/showthread.php?t=97627&highlight=Reset+Debug
(Look at pictures)

Thanks in Return,
Hacker1.6

[caliber1942]

run winject after you have the game running.....

select bf2142.exe as target

click the "..." button within the Target Process section

Click Reset Dbg button at bottom

close winject without injecting anything (unless you are trying to inject something)

your debug port is reset

the game will still manage to crash on you while this is reset and you are using a debugger like olly or tsearch autohack

good luck-
Cal

[hacker1.6]

Oh great another problem! I have the Commander offset. I go into single player, use Winject to reset the debug, and then when I open OllyDbg and attach it, it does not respond! It locks up.

[dreakoth]

Maybe if you try not closing winject or using the batch file i suggested. I remember i used to have problems with winject a bit, u just have to try things untill you can get it to work on ur system.

I find that if i reset the debug ports before i have spawned in a map then it will lock up when i unpause the process regardless, so i dont attach olly untill i have spawned.