Home › Forum › MultiPlayer Game Hacks & Cheats › Other Semi-Popular First Person Shooter Hacks › WarRock - International Hacks › WarRock Tutorials › The secrets to succes.
The secrets to succes.
The secrets to succes.
First of all im going to introduce myself since some of the members may not know me.
Index
0.1 - Introduction
My name is Alex_Agnew / AeroMan.
Im a coder for over 4 years.
0.2 - Some of my work
I started back in the olden glory days of the game.
Back then in '08 i coded my first hacks.
In that time my nomenu that i did not even code all alone (i had like 5 credits for a hack with 3 functions) it gave me 500+ downloads.
Those days my menu hack gives me only 10%-20% of it.
The more i advanced in coding and the more i learned i found out with alot of help (i think i did nothing looking back at it) i finally managed to make a first nomenu!
There was actually not sush thing as 'coding' at that time for me, i mostly copy-pasted thinking that would get me further and easier to what i wanted to become. A succesfull coder!
Looking back at that period of time its a waste of time, i copy & pasted all sorts of stuff togetther not knowing what it did or how it worked.
I had to ask for help every 5 minutes again and again.
So after a while i achieved this copy-pasted hack: http://img714.imageshack.us/img714/3740/hach3.jpg
It also had more credits then functions.
I was lucky that after 5 months of trying to find detours someone finally posted a bypass.
Else i would have never succeeded how i was going!
But as time passed i finally saw that this was NOT the way to go!
Every update i worried alot, "is my hack going to work?", "How am i going to find addies?","What if the bypass is patched?","What if i crash?".. you get the point
So i decided i wanted to actually learn how to code instead of copy-pasting stuff togetther like a moth without brains.
It took me untill the bypass got patched and the directx version updated before i actually realized i was not a coder, but a leecher.
So i started to study real hard like it should, reading and writing codes, studying directx.
after alot of months i finally managed to update it and i started to become a coder. At this point i was 1-2 years later.
Screens: one, two
but then after a while i was devastated because my girlfriend broke up with me, so i was kind of depressed all the time and i felt like quiting coding every 5 minutes, i belive i took like 4 brakes of coding and i always returned.
Because that is how being a coder should be, its kind of a lifestyle.
Now 4 years later, i managed to become a succesfull coder.
0.3 - The recipe to success
0.4 - What coding languages you need to master
- There are 3 languages you need to master: Assembly (Reversing, dissasembling, ..), DirectX, C++.
- The languages are needed for:
0.5 - What if you have an issue?
- There are alot of problems that you can have, but how do i solve them?
-- The best way to solve this is by visit the Microsoft Developer Network.
--- Those people are the best in their business, it is Microsoft so..
-- You can also ask on forums like those.
- Or you can simply google it
0.6 - The problem with Copy & Pasters, Leechers
* Copy & Pasters *
- This are the people that make you lost huge amounts of profits, downloads, likes, ...
This is because coders that know how to code or accidently by luck find a way to fix hooking, functions, etc.
They share this on a website and before you know it the whole game is fucked up by 1 person.
- People like this often have bigger hacks then yourself;
And how does this come? Simply because they copy paste stuff togetther with a pre-made base that someone has coded and released on the internet.
You can make a hack like this with all the functions in less then 4 hours.
Just because you can take a function of certain sites and then paste it in the base you downloaded (which often gets renamed to the 'coders
' name) and its done.
- Its also this people that give coders a bad reputation.
* Leechers *
- Those are the people that are even worse then copy pasters.
Those are the people that take the stuff you made and don't give you credits for it.
Because 'they' coded it, which we all know is not tru.
I often see a function or source of me being used without credits.
Or wrong credits, then i see my code with another name on it.
0.7 - Quantity vs Quality
- When creating cheats it is extremely important to think about Quality.
You often see a cheat that is made for 'Quantity'.
What i mean by this is that they have a shitload of functions, but as soon as you startup one of those functions the hack crashes, laggs, ..
- You can instantly notice which ones that are made for Quality and which ones that are made for the Quantity.
A high quality hack may be smaller then a quanity hack, but those hacks are often the best.
You wont get stuck in a lagg, a freeze or even a crash.
0.8 - Rechecking your hack before releasing it
- ALWAYS recheck your hack before you release it.
What i do: after a update of HackShield, WarRock, .. after i updated my hack i ALWAYS check the functions ingame to see if they function properly, if not i fix them or let them out.
Its always a good trick to stay ingame for atleast 12-15 minutes, to double-check that there is no detection.
Skipping those processes (like i do somethimes) can give you unexpected crashes, bugs, and all that sort of malfunctions.
And those will ofcourse cost you downloads, members, and if you are coding VIP hacks it can even cost you CASH!
0.9 - Crypting vs Packing
- Packing is probably one the most important things you always have to do.
Packing is basicly protecting your hack so people cannot steal stuff out of your hack for their own benefit.
- Crypting is also very important, you can make simple functions based on logics that can save your stuff from being leeched.
Combining those two tricks togetther will make it harder to crack your hack.
Ofcourse it can always be done be a better coder.
1.0 - Giving credits
- Giving credits is very important!
By giving credits you are giving the credits of a function, source, .. to the coder who made it.
Imagen you making a function, then someone else uses it without you in the credits.
But YOU are the one who made it, so he basicly stole it.
1.1 - Special thanks
- By ending this 'secrets' im willing to thank all the people that helped me over the year by learning to program, ..
Goodluck, by any questions feel free to ask them.
Im not a good writer, i hope it makes sence!
Index
- 0.1 - Introduction
- 0.2 - Some of my work
- 0.3 - The recipe to success
- 0.4 - What coding languages you need to master
- 0.5 - What if you have an issue?
- 0.6 - The problem with Copy & Pasters, Leechers
- 0.7 - Quantity vs Quality
- 0.8 - Rechecking your hack before releasing it
- 0.9 - Crypting vs Packing
- 1.0 - Giving credits
- 1.1 - Special thanks
0.1 - Introduction
My name is Alex_Agnew / AeroMan.
Im a coder for over 4 years.
0.2 - Some of my work
I started back in the olden glory days of the game.
Back then in '08 i coded my first hacks.
In that time my nomenu that i did not even code all alone (i had like 5 credits for a hack with 3 functions) it gave me 500+ downloads.
Those days my menu hack gives me only 10%-20% of it.
The more i advanced in coding and the more i learned i found out with alot of help (i think i did nothing looking back at it) i finally managed to make a first nomenu!
There was actually not sush thing as 'coding' at that time for me, i mostly copy-pasted thinking that would get me further and easier to what i wanted to become. A succesfull coder!
Looking back at that period of time its a waste of time, i copy & pasted all sorts of stuff togetther not knowing what it did or how it worked.
I had to ask for help every 5 minutes again and again.
So after a while i achieved this copy-pasted hack: http://img714.imageshack.us/img714/3740/hach3.jpg
It also had more credits then functions.
I was lucky that after 5 months of trying to find detours someone finally posted a bypass.
Else i would have never succeeded how i was going!
But as time passed i finally saw that this was NOT the way to go!
Every update i worried alot, "is my hack going to work?", "How am i going to find addies?","What if the bypass is patched?","What if i crash?".. you get the point
So i decided i wanted to actually learn how to code instead of copy-pasting stuff togetther like a moth without brains.
It took me untill the bypass got patched and the directx version updated before i actually realized i was not a coder, but a leecher.
So i started to study real hard like it should, reading and writing codes, studying directx.
after alot of months i finally managed to update it and i started to become a coder. At this point i was 1-2 years later.
Screens: one, two
but then after a while i was devastated because my girlfriend broke up with me, so i was kind of depressed all the time and i felt like quiting coding every 5 minutes, i belive i took like 4 brakes of coding and i always returned.
Because that is how being a coder should be, its kind of a lifestyle.
Now 4 years later, i managed to become a succesfull coder.
0.3 - The recipe to success
- Be confident. if people say you can't do something proof them wrong.
- Be yourself - Don't act diffrent around coders that are 'more' respected.
- Stick to it - If something is not working, make it work. Don't quit meanwhile -> its one of the biggest mistakes you can do.
- Study - Study the coding languages needed.
- Don't let you put down - If people say your a bad coder, don't belive it. Go for what you and only YOU want.
0.4 - What coding languages you need to master
- There are 3 languages you need to master: Assembly (Reversing, dissasembling, ..), DirectX, C++.
- The languages are needed for:
- C++ - Writing your own functions, bases, ...
- Assembly - This will keep you undetected, not mastering this part will kick your ass in the end.
- DirectX - You want te be able to draw text, boarders, .. etc ingame for a menu, this is 'all' done with DirectX
0.5 - What if you have an issue?
- There are alot of problems that you can have, but how do i solve them?
-- The best way to solve this is by visit the Microsoft Developer Network.
--- Those people are the best in their business, it is Microsoft so..
-- You can also ask on forums like those.
- Or you can simply google it
0.6 - The problem with Copy & Pasters, Leechers
* Copy & Pasters *
- This are the people that make you lost huge amounts of profits, downloads, likes, ...
This is because coders that know how to code or accidently by luck find a way to fix hooking, functions, etc.
They share this on a website and before you know it the whole game is fucked up by 1 person.
- People like this often have bigger hacks then yourself;
And how does this come? Simply because they copy paste stuff togetther with a pre-made base that someone has coded and released on the internet.
You can make a hack like this with all the functions in less then 4 hours.
Just because you can take a function of certain sites and then paste it in the base you downloaded (which often gets renamed to the 'coders
' name) and its done.- Its also this people that give coders a bad reputation.
* Leechers *
- Those are the people that are even worse then copy pasters.
Those are the people that take the stuff you made and don't give you credits for it.
Because 'they' coded it, which we all know is not tru.
I often see a function or source of me being used without credits.
Or wrong credits, then i see my code with another name on it.
0.7 - Quantity vs Quality
- When creating cheats it is extremely important to think about Quality.
You often see a cheat that is made for 'Quantity'.
What i mean by this is that they have a shitload of functions, but as soon as you startup one of those functions the hack crashes, laggs, ..
- You can instantly notice which ones that are made for Quality and which ones that are made for the Quantity.
A high quality hack may be smaller then a quanity hack, but those hacks are often the best.
You wont get stuck in a lagg, a freeze or even a crash.
0.8 - Rechecking your hack before releasing it
- ALWAYS recheck your hack before you release it.
What i do: after a update of HackShield, WarRock, .. after i updated my hack i ALWAYS check the functions ingame to see if they function properly, if not i fix them or let them out.
Its always a good trick to stay ingame for atleast 12-15 minutes, to double-check that there is no detection.
Skipping those processes (like i do somethimes) can give you unexpected crashes, bugs, and all that sort of malfunctions.
And those will ofcourse cost you downloads, members, and if you are coding VIP hacks it can even cost you CASH!
0.9 - Crypting vs Packing
- Packing is probably one the most important things you always have to do.
Packing is basicly protecting your hack so people cannot steal stuff out of your hack for their own benefit.
- Crypting is also very important, you can make simple functions based on logics that can save your stuff from being leeched.
Combining those two tricks togetther will make it harder to crack your hack.
Ofcourse it can always be done be a better coder.
1.0 - Giving credits
- Giving credits is very important!
By giving credits you are giving the credits of a function, source, .. to the coder who made it.
Imagen you making a function, then someone else uses it without you in the credits.
But YOU are the one who made it, so he basicly stole it.
1.1 - Special thanks
- By ending this 'secrets' im willing to thank all the people that helped me over the year by learning to program, ..
- Pixipixel - you will always be a legend brother!
- Unknown PK - Thanks for all the help
- R3D_L!n3 - Thanks for all the help bro, i know i can be a bitch im sorry about that.
- N4N033 - Thanks for all the support brother, i hope to work with you much longer
- IHelper - Thank you man for helping me in the old days!
- Th3 Reaper - I miss you brother, i hope to see you again one day.
- Alen - Thanks for all the good times!
- Tony - I miss you brother, thansk again!
- MaxyLopez93 - Thank you bro for all the help, i hope one day you come back to coding!
- Hell_Demon - I know you never liked me but you helped me alot :P
- Dreamgun - Thank you for all the good times back in the old days
- Cronor - Thank you for helping me with understanding detouring!
- TheCamels8 - I hope you come back one day! Goodluck in the military!
- SF_Sharef - I don't know where you are those days but i miss you.
- DuoCoder - I know we fight somethimes, but i never mean it. I hope for alot of good times to come
- Oompa loompa - Thanks for helping me with my first hacks!
- BMW_M3 - Thanks for helping me in the old times!
- BigBangBaby - For the good times!
- Liz - For everything
- Mike Shinoda - For all the good times, i dunno where you're at those days.
- Pagn - I tought you where cool untill you became a little better and became a bitch and scammed me
- Terrel - for the good times
- xXTylerXx - For the good webcam talks xD to bad your in prison
Sorry if i missed someone, <3
Goodluck, by any questions feel free to ask them.
Im not a good writer, i hope it makes sence!
Similar Threads
- 0Last post
- 1Last post
- 47Last post
nice master @