Csgohacks – How to (indepth) paste a csgo internal cheat
I keep on seeing these people using Rat Poison, when there are MILLIONS OF BETTER CHEATS FOR FREE, that legitimately only would take a few minutes to make.
First off, you got to pick your cheat. To me this is like picking out a puppy from a store, something you will cherish for the rest of your life(or until it becomes detected and dies).
The best picks for free public sources are
Osiris – Legit MultiHack. Most stable
Sensum – Legit Cheat, lots of features but some are broken
GladiatorCheats v2.1– Rage, Legit multi cheat. Needs offset updates.
Aristois – My personal favorite Legit Multicheat. Needs smoke check fix
Aristois pasted by chozen – Aristois with some extra features. Some are broken
You can also find a lot of cheats on Void a public cheating forum, and UnkownCheats. ONLY USE UNKNOWN CHEATS IF YOU KNOW WHAT YOU ARE DOING. The forums are only good for fixing and adding new features.
Now that you have Picked out your cheat and downloaded it, you have a .rar, .zip. .7zip etc file, and a dream.
Open up and extract the files into a folder, I’m going to be using Osiris for example.
Extract the folder from the zip into another folder, or to your desktop. I prefer it to a folder because it’s clean.
Now that we have that, open up the folder and you’ll be greeted to all the MALICIOUS FILES. Hah jk, they all contribute the code of the cheat to ensure that it works properly so you can have a good time.
Double click the .sln file. Sln Files are what describe a whole project to Visual studio. Imagine it as if it was the gift wrapping of a present you got on Christmas day. Pretty serious stuff.
When you double click the sln file, you will be greeted to this. I will be teaching you some basic errors now before we get to undetection.
C:UsersuserDesktopOsirisOsiris-masterOsirisOsiris.vcxproj : warning : The build tools for (version) cannot be found. Install (version) to build using the (version) build tools.
This is a simple fix, just right-click the project file, under “Solution ‘Name'” and click properties
Once you’re in the properties menu, make sure the windows SDK is at its highest/latest version
The SDK is Highlighted in blue since I clicked it
And that the platform toolset is at the highest/latest version too.
I’m using visual studio 2017, 2019 will come with v142 installed.
Random Unexplainable errors everywhere
This goes back to the windows SDK Version. Make sure its set to the highest version to ensure that you don’t have any windows related file errors.
Any other errors ill be sure to help trouble shoot
Now, to test the source before we apply systems to make it undetected, we are going to try test compiling it.To compile it, set the version to “Release” and “(your processor type here)”. Mine is x86.
It’s at the top highlighted in yellow.
Now that those are set, go to “Build” in the tab, and click “Build Solution”. Or if you can’t find it, CTRL + SHIFT + B works just as well. (Build should be right above Release, and a little to the left.)
The build tools for (version) (Platform Toolset = ‘(version)’) cannot be found. To build using the (version) build tools, please install (version) build tools.
You did not set the platform tool set properly. Repeat the process above after doing so.
If the build is working properly, you will see something like this.
This is the code compiling into what is called a “DLL file”
Now that its compiled, we know the source is working properly.
Here comes the part where we make it undetected. There are many different ways on how to make a cheat undetected, but by far the easiest way is junk code, but first we must disable the option that gets rid of junk code.
Visual Studio Has an option that you can disable that optimizes your code. Its found under the same properties the tool set is found under, but this time you’re going to want to look at the left side bar, and click C++.
When you’re in the C++ Properties, expand it down, and click “Optimization”
Make sure everything is disabled or to the very least as turned off as possible. This will disallow from junkcode being removed in a effort to optomize it.
Junk code is code that basically changes the signature of the cheat and makes it unrecognized to VAC. Its a real lifesaver for some.
Here are some possible junk code methods
Auto Junk code – Easiest, takes little to no time, but is almost everytime detected,
Manual Junk code – Not really hard, takes more time than auto, but is not as easily detected.
For auto junk code, I use a program called “C++ Auto Junk Adder made by Peatreat and Thaisen” which can be found at Auto Junk Code. Do note you are going to need an account to download this.
Screenshot of menu
To use this, put the .exe in the folder with the .sln, run it, set type to any type you want (I use long), Var length to 70+, and Func Length to 70+.
You can put them to any variable, just know that some are better than others.
[ Scroll past if you did auto, unless you want to also do Manual ]
Now, for manual junk code im going to suggest a auto junk code running script thats hosted on this website.
Open the website, and copy all the code
This is what generated for me.
Now, go back to the project/code, and open it up
In the solution explorer, search for “.cpp”
These are the files that hold all the source code that make the cheat run.
You can close External Dependencies. They are useless. Go to hacks, and click on the .cpp files.
Now that its open, grab the code you copied from the website, and paste it into the cheat top of the cheat.
I spaced the #include “Aimbot.h” away a bit, so then i could make sense of the cheat easier for later.
Now, go back to the code page and reset/restart the website by clicking the circle arrow top left. Copy and paste as much junk code as you’d like.
I suggest 2 or three times, just dont include the #include “name” every time from it.
Do that for all .cpp files in the cheat.
Once you are done, you are free to compile. So go to the “Build” tab, as stated before, and “Build solution”, or CTRL + SHIFT + B. That works just aswell.
If you did everything properly, it should come out as it did before.
|||||| KEEP TRACK OF THE DLL, ITS YOUR CHEAT. |||||
Now, we are going onto injection. There are many different types of injectors out there, but one of our trusted handy dandy moderators of r/Csgohacks said that I should suggest Rando Injector, with the use of his “Random Byte Injector” found at Random Bytes
To use rando injector, its the same as compiling a cheat.
Extract the file from the zip.
Open the file and find the .sln, it’s buried in there.
Once you have it open, open the solution again like you did when you were adding junk code to your cheat and open Main.cpp
Now, once main is open, you only need to worry about the top code.
Don’t go any more down than this.
Change “DLL_NAME” to the name of your dll. For my instance, its osiris.dll.
Now, open up the random bytes website
And copy all the code, and paste it right under “__asm _emit 0x09 “
It’s going to be a lot, but that’s alright. The more the better. If you would like to, copy and paste a few more times but I think once will be alright. Now build the solution, as described before.
Once you are done, put the DLL and Injector into the same file, open csgo, and run the injector.
Now that you’re injected, have fun, and don’t forget, we are all here to have a good time. Thank you for reading.
SPECIAL THANKS TO REALLY COOL MOD
OR COMMONLY KNOWN IN THE DISCORD AS 2772 FOR GIVING ME SOURCES TO WORK WITH. BIG HELP!!!!