Luigi Auriemma

I applied the haloloop.lpatch to halo.exe (1.00.04.0607) and it's still vulnerable. What's going on?

The haloboom.lpatch works great, but this one isn't.
If you could upload an updated .lpatch or PM me the offset to tamper with I would be very much appreciative.

Thanks.

haloloop.lpatch is specific for the haloloop1 bug, so doesn't fix haloloop2 and haloloop3.
anyway take a look to the following thread for a better idea:

/haloloop-f ... -t462.html

Wait, 2 more versions? agh.

I just want to stop this lame-ass dude constantly crashing me. It takes 10 seconds of my life to open task manager and kill it, 10 seconds I could be spending say... playing?

Any .lpatch'es for v2 and v3? or an offset table.

Thanks.

EDIT: I don't run a dedicated server.

this is a problem... first because for example in this moment the new refresh hotfix released the 30th July exists only for the dedicated server and then because modifying the server for allowing old clients to join is easy to do with the dedicated one while for the client is required a memory patcher (like a launcher for halo.exe).

anyway the only solution I have is the usage of the 1.07 dedicated server modified to allow any client of any version or of a specific version to join, which seems to work very well.

Are you saying that only dedicated servers are immune?
If so that sucks. bah

Could you atleast give me the offset in the 1.04 .exe where haloloop v2 and v3 crash it? Or don't you know?

Thanks.

http://www.bungie.net/Forums/posts.aspx?postID=24200699
Roger says that the fixed client executables will be released soon but I don't know when


it's an endless loop, not a crash
the offsets of the instructions are easy to find through a debugger since they loop in an endless cycle

Got it, thanks.

I use this tool all the time when i got kicked or banned Lol.