Assembly tutorial

[iago]

So, I've done up to the end of making a functional hack for Starcraft.

Is anybody still reading? Are there any tough parts/bottlenecks that I should go back and work on?

Are all the explanations clear enough?

I'm going to stop here for awhile till I get some feedback and inspiration.

One major question is: what more do you want? What should I add, or work on? What interests you?  I'm willing to teach!


<Edit>
Here's a screenshot of the hack I made in the walkthrough:

[rabbit]

I'd really like to know the offset for the current version.  I thought it was 0x5031B0, but it's not working.

Also, your link to the Injector is broken (it points to skullsecurity.com).

[iago]

I'd really like to know the offset for the current version.  I thought it was 0x5031B0, but it's not working.

Also, your link to the Injector is broken (it points to skullsecurity.com).

What do you mean by "offset"? There are a lot of offsets.

I had trouble using TSearch with the current version, plus I don't want to stir up legal trouble, but if you follow my guide you should be able to find any of the same functions on the newest version.

Oops @ the link -- I have to run right away, can somebody fix it?

[rabbit]

I mean in the final bit of code

Code: [Select]

int fcnDisplayMessage = 0x469380;I was so sure I had the right address, but it didn't work :\

[iago]

It may be because Blizzard is being more proactive on anti-hacking stuffs. Can you link me to the latest Starcraft.exe?

<edit> Thanks to Deuce for fixing that link.

If anybody wants to learn how to do files nicely (with thumbnails) and wants to do screenshots for some of the tutorials, I'd appreciate it.

[iago]

I mean in the final bit of code

Code: [Select]

int fcnDisplayMessage = 0x469380;I was so sure I had the right address, but it didn't work :\

Well, the "Injector" program doesn't seem to work on the latest version of Starcraft, I'm going to have to re-write it or something. Perhaps that's your problem?

<edit> this can be fixed by running the programmer in a debugger, breaking immediately, finding advapi32!SetSecurityInfo, and setting the first 3 bytes of that to c2 1c 00. Then run the program, and you can load whatever you want.

I wrote about that here:
http://www.skullsecurity.org/wiki/index.php/Example_8#Removing_Protection

[Warrior]

After reading it, I suggest maybe it could be edited to include links to the relevant sections in parenthesis.

For example when you talk about fastcall calling conventions you could provide a (see: Calling Conventions) next to it so if people want to fully understand it before going on they can.

[iago]

After reading it, I suggest maybe it could be edited to include links to the relevant sections in parenthesis.

For example when you talk about fastcall calling conventions you could provide a (see: Calling Conventions) next to it so if people want to fully understand it before going on they can.

That's a good point. I thought about doing that before, but once I'm on a roll it's hard to stop and find a link, it breaks the chain of thought.

If I get around to proofreading, I might go back and do that.

But if anybody else wants to do it, the syntax is [[SectionLink|texttodisplay]]

[Warrior]

I'll see if I can do it