After learning the basics is c++

I have a quick question,After I have grasped the basic's of c++,varialbles,data types,functions,arrays,classes,pointers,memory managment, and structs, argument's and all the basics,I was wondering where I would move on to learn more if I wanted to move into making game hacks.

The tutorial that I was following ended after polymorphism and I now think that I have the basic lining to move on,but I'm not quite sure how to go about it.

I see alot of hacks are made using the windows api,with types such as HWND and DWORD,but how do I get knowledge of these and what they do,is there any tutorials on it?

Any suggestions as to what I should do, and where I should go to learn new c++ concepts,is much appreciated,Thanks

In-line Assembly.
Although i have never successfully made a Game Cheat (Cheat no hack -.-) I know Assembly will be a vital key part of it.

Yeah, I know a bit about asm and reverse engineering programs already, I'm not the best but I was more looking for an answer to where I branch out to in c++,

I mean I havn't been taught what alot of things I commonly see are, such as HWND and DWORD and WriteProcessMemory, Where are some references with good explainations to such things, is there any tutorials on using those that are similar to the ones that teach basic c++?

NO, Don't learn asm yet. You will be confused and then you will quit programming as a whole. You must start on the Winapi. Once you finish the WinApi you will be ready for asm. Trust me, if you start asm now it will be so confusing that you won't continue programming. Here is a good book by Charles Petzold, it is the best book on WinApi ever made:

PDF & Compiled HTML: http://www.media fire.com/?iy2ytiqazzn

Get competent at C++ before you try anything else.

Originally Posted by Auxilium

Get competent at C++ before you try anything else.

Thats what he is trying to do...
2.2 Common Data Typesⓘ
That website is your friend ^^

So I just started reading the book by charles on windows api programming, I'm about half way through and it said that,Most programmers don't memorise the code for making a window,that they just usually copy an exsisting window and make the appropriate changes, Is this true?

Because it's alot to remember and I doubt I could remember all that's there,so I guess my question is,is it acceptable not to remember or should I try my best to memorise it?

Originally Posted by I.P

So I just started reading the book by charles on windows api programming, I'm about half way through and it said that,Most programmers don't memorise the code for making a window,that they just usually copy an exsisting window and make the appropriate changes, Is this true?

Because it's alot to remember and I doubt I could remember all that's there,so I guess my question is,is it acceptable not to remember or should I try my best to memorise it?

it's true. You don't need to memorize it or retype it every time you make win32 application. What i do is save the code that just makes the window in a text file so that every time i make a window app i just copy and paste it.

Originally Posted by 258456

it's true. You don't need to memorize it or retype it every time you make win32 application. What i do is save the code that just makes the window in a text file so that every time i make a window app i just copy and paste it.

No it surely is not.
Forgetting partial code syntax is fine but you should never C&P code you don't know.

Originally Posted by VirtualSia

No it surely is not.
Forgetting partial code syntax is fine but you should never C&P code you don't know.

There is a difference between not knowing and being lazy.

Although, I gotta agree that C&P isn't really a solution, unless you know your own code and you feel like a lazy ass to re-type (practice).

Originally Posted by VirtualSia

No it surely is not.
Forgetting partial code syntax is fine but you should never C&P code you don't know.

Well, you would obviously have to know what your code does, and since I don't want to waste like five minutes just typing what i could be pasting (window code), i paste the window code then i start coding.

Well I guess that's a bonus ;P

I mean I sort of understand what the code means now when I'm reading it,But remembering all the stuff involved? LOL

I can pretty much only recall what the main function looks like
int WINAPI WinMain(HINSTANCE hIstance,HINSTANCE hPrevInstance,LPSTR lpCmdLine,int nShowCmd)

and then I remember that a message box has like 4 parameters,the first one always being NULL and the second the text,the third the Caption and the 4th,The button.

but if people did it, I wouldn't understand how the hell they would remember the rest like wndclass.style, Gah the win api is crazy to learn its like a whole new language,and I'm having a hard time understanding it -.-

Inheritance, polymorphism, function pointers. Read Sam's C++ in 21 days. I think after reading it and understanding it I think you will have a solid understanding of C++.

I think it's okay to copy code the way you're describing it. As long as you understand it.

For windows forms in C++, I understand how everything works, but the only thing I can't remember is the WNDCLASSEX/WNDCLASS structure & all the parameters for CreateWindow. But that doesn't mean I don't understand everything, I can simply look up the parameters and members of the structure on MSDN. But once you feel you understand everything I guess it's okay to take a shortcut. Don't kid yourself here, if you start copy pasting without understanding it you're only hurting yourself. :P

Remember: there's a clear difference in knowing the C&P code and actually understanding it.

After learning the basics is c++

Post a Reply

Tags for this Thread