Halo - Can't attach debugger? What the hell!?

[Viper666]

Ok. I want 3 things from this game, and I can't seem to do it, seeing as though 2 of them require a debugger. I've tried with 2 seperate apps and I've been able to search the RAM, but not attach debugger in order to set breakpoints.

What I want to do is

1. find the grenades address--which I did, but the address probably isn't static)--and set a breakpoint on read to get myself a place in the assembly that reads it. I would then change that to a write opcode in order to get myself Unlimited Grenades properly as opposed to being required to have some before they're infinite, like most trainers. I did this with another game before. Works like a charm.

2. Change the shield recharge so it goes to the overcharged full instead of just regular (2X Shield, basicly)

3. I want to know how the hell the Outkast trainer does that "Vertical Limits Ammo." Some of us would like to be able to turn the goddamn effect off without having to close the game and reopen!! I tried using Trainer Spy, but that didn't help me any. I turned it on, and as I started to take note of the modified addresses and values, it was still adding more. So I dunno what the hell that's doing.

[caki]

Halo for PC is protected by Safedisc 2.70.30. I am assuming you are trying this on the original uncracked exe. One of the features of safedisc is to fill portions of the code with int 3's, and then have a debugger run parallel to the game process and replace the int 3's with the original game code. Since this safedisc debugger is running with the original exe, you cannot attatch another debugger because 2 ring3 debuggers cannot debug the same process. I think you may have some more success with Softice, which is a ring 0 debugger.

I think that this may be the problem. Try coding the trainer using the cracked exe. I think that the memory locations and all that other crap are the same in the original and the cracked exe, so a trainer for the cracked exe should work on the original exe and vice versa. I am not sure about this, as I do not have a lot of exeperience with game training.

Hope this helps :)

[DRAGoN.X]

Use latest version of Cheat Engine (5.2) and use Kernal Debugger. It gets around all know protections except Starforce :mad: DAMN YOU STARFORCE. (and also it can't get around stuff that overwrites debug resistors since thats what the Kernal Debugger Uses, i.e. RTW:BI 1.6 <-I think)


But hell theres even a patch for that all though it's highly unstable and max's out CPU and crashed game since it overrites something so many times (apparently faster than stareforce can)

PM/E-mail/IM me if you want any more help.

-DRAGoN.X :cool: