Messed up starcraft's screen

[hellinsect]

I was hacking starcraft's screen data and made a mistake. This what happened. It works perfect except for the size and the mini-screen in the corner. Usually it crashes, but this time I couldn't believe my eyes.

[K? Pŕo?ćtiόnŹ]

Neat

[Sheppard]

What's so cool about hacking such a old game, I seriously don't understand why you keep hacking it. Isn't it dead yet?

[OmegaMatrix]

That was a pretty stupid thing to say, if it were dead, nobody would play it, so nobody would be hacking it.

Anyway, nifty screen fux up, what are you planning on using it for?

[Sheppard]

Originally Posted by OmegaMatrix

That was a pretty stupid thing to say, if it were dead, nobody would play it, so nobody would be hacking it.

I'm just curious. I, for myself, don't see any motivation in hacking starcraft because this game is basicly reversed. Every kind of hack has been out for this game. However, I didn't try to offend anyone, I am just a bit confused. ;)

[ViperSRT3g]

Every hack has not been out yet. Have you ever seen many of these?
Clicky

And I've done something similar to that with unit sprites, which goes to show, it definitely is possible to change the game's resolution. But my sprite thing made the sprites get stretched out sideways like they were getting torn apart.

[Avalon[FR]]

Originally Posted by Sheppard

What's so cool about hacking such a old game, I seriously don't understand why you keep hacking it. Isn't it dead yet?

That has to be the stupidest thing to say in a StarCraft hacking forum.

[hellinsect]

Originally Posted by OmegaMatrix

That was a pretty stupid thing to say, if it were dead, nobody would play it, so nobody would be hacking it.

Anyway, nifty screen fux up, what are you planning on using it for?

It will make it possible to write whatever you want on the screen without overwriting the mouse. This hack will double the system requirements as far as printing the screen.

I finished the screen data hook and now my functions print the screen. I just need to plug the correct data into the discrepancy arrays.

[Sheppard]

Originally Posted by Avalon[FR]

That has to be the stupidest thing to say in a StarCraft hacking forum.

Actually, we are in the "Reverse Engineering". I am only here because this forum has the most active warcraft 3 hacking board. However, nevermind what I said. I wasn't aware that you guys would end up getting rough.

Just by the way, why don't you call starcraft's own draw routines? Even better, why don't you write your own Starcraft client?

[hellinsect]

Originally Posted by Sheppard

Actually, we are in the "Reverse Engineering". I am only here because this forum has the most active warcraft 3 hacking board. However, nevermind what I said. I wasn't aware that you guys would end up getting rough.

Just by the way, why don't you call starcraft's own draw routines? Even better, why don't you write your own Starcraft client?

LOL, been there tried that, too hard. I find it much easier to call API functions and lock the data on the screen. Besides, I will have to anyways to restore screen under the mouse.

[Sheppard]

Originally Posted by hellinsect

LOL, been there tried that, too hard. I find it much easier to call API functions and lock the data on the screen. Besides, I will have to anyways to restore screen under the mouse.

Well, what about just hooking at a location before the mouse gets drawn? And why is it harder to call starcraft's draw functions? Isn't like all info you need public already?

[hellinsect]

Originally Posted by Sheppard

Well, what about just hooking at a location before the mouse gets drawn? And why is it harder to call starcraft's draw functions? Isn't like all info you need public already?

Like I said, hooking the mouse is a given. However the some of starcraft's ddraw functions are way out there and have 10 locations that print stuff that has invisible surface locks and have about 9 arguments.

However by changing 2 pointers the screen is all configured in my off-screen array and the rectangle that is being updated at the time is mine.

One of starcraft's ddraw functions was written in ASM by hand. This function stops the game play screen from writing over the command bar. I am basically using it a as blue print.

[K? Pŕo?ćtiόnŹ]

Starcraft is good practice.

[hellinsect]

Here is a basic structure of how my hacks will print stuff on the screen.

void MakeHackScreen()
{
if(!FindWND) 
{
hWnd = FindWindowA(TheClassName,TheWindowName);
GetClientRect(hWnd,&ClientRect);
FindWND = TRUE;
}


// ADD to screen.
hDC = GetDC(hWnd);
// printing fuctions go here
DrawTextA( hDC,"hey",-1,&ClientRect,(DT_CENTER | DT_TOP | DT_SINGLELINE));// Must be called 2 times to lock.
LoadAndMark_Screen(&ClientRect); // Loads data to array2 and ORs the lowest red bit.
// printing fuctions go here
DrawTextA( hDC,"hey",-1,&ClientRect,(DT_CENTER | DT_TOP | DT_SINGLELINE));// Must be called 2 times to lock.
TestAndUnMark_Screen(&ClientRect); // Marks everything equal in discrepancies1 and ORs the lowest red bit.
ReleaseDC(hWnd,hDC);


// DELETE from screen.
Reset_UpdateScreen(&ClientRect); // Removes hack data from the screen.

return;

[SC_Modder]

Originally Posted by hellinsect

Like I said, hooking the mouse is a given. However the some of starcraft's ddraw functions are way out there and have 10 locations that print stuff that has invisible surface locks and have about 9 arguments.

However by changing 2 pointers the screen is all configured in my off-screen array and the rectangle that is being updated at the time is mine.

One of starcraft's ddraw functions was written in ASM by hand. This function stops the game play screen from writing over the command bar. I am basically using it a as blue print.

The new compiler they are using makes it appear that the assembly is written by hand. But really they are just really good compiler optimizations. Don't forget that Starcraft is a cross-platform game. Writing any function purely in assembly would be stupid.

[hellinsect]

Starcraft DEFINES all of its colors in the graphics card. The way they are defined is very wired. Like I was going down the list printing each one, a lot of the blue ones blink. This is for the water believe it of not. API calls work, but the colors are all out of whack and you have to play with them until you get the correct colors you want. Apart from that, the locking code works great.