Clickforlife

At the moment there isn't a way to use both Snapchat AND tweaks. There are SOME methods that will let you use it for a moment, but eventually kick you out again AND they usually only work for a handful of users that try

Post looks good

i did though the post was still on preview thats why

fixed it

shit gotta fix it lol fixed

MADE BY A GOOD FRIEND OF MINE GOOD STUFF HERE Basics of a C++ Cheat Note: Sorry if I have some mistakes, also you should read everything so you'll be able to fix stuff in case of errors. [code] #include <iostream> #include <windows.h> [/code] This is pretty much all we're going to need for a simple console program, even if you want to add some other stuff, it's probably already in one of these two. Also, you will need to also include "stdafx.h" if you're using visual studio. [code] int main(){ [/code] We're using this because we will eventually have to return some integer values too, else we would just use void main. [code] SetConsoleTitle(L"Whatever_You_Like"); [/code] This is used to set the title of our console program (that means the name you see at the top) to something else. The L before the string is there for compatibility reasons and as long as you don't use any numbers, everything should go well. [code] HWND Window = FindWindow(NULL, L"Game"); [/code] With this code, we are getting the handle of a specific window, which is "Game" (you can of course change it with whatever your game's window name is) and remember, it's not case-sensitive (If your window says "Battlefield" you can use "battlefield" too). [code] if (!Window){ return 0; } [/code] If the window (the one used above) has not been found (that's why the '!' is there), it closes the console (return 0); [code] else{ DWORD Pid; GetWindowThreadProcessId(Window, &Pid); HANDLE ProcessHandle= OpenProcess(PROCESS_ALL_ACCESS, FALSE, Pid); [/code] Pretty understandable from the code itself, we are getting a handle on the process itself to be able to edit its memory, of course. [code] if(!ProcessHandle){ return 0; } [/code] Again, if the program can't attach to it or maybe the process is stopping this from happening it will close your program. [code] else{ [/code] This is where the actual hack begins, if all goes well. [code] for(; { [/code] This is a not-so-very popular way to create a loop, while(0){ can be used too. A loop basically means it will keep running trough the code and see if anything change or actually change something. Basically think it as freezing an address in cheat engine (though that's not the only thing we'll use it for. [code] if(GetAsyncKeyState(VK_F2)){ [/code] This check if a key has been pressed, in this example we're using the F2 key. The added & 0x8000 you probably have seen before refers to the key being held, as far as I know, but it's really just useless in this example, you just want it to be pressed. [code] UINT_PTR FByteAddress= 0x01182A74; float FloatAddress = 0x011A5B90; int ValueForReading = NULL; double DoubleAddress = 0x00FDB0F0; [/code] It's not very common that I see people use UINT_PTR, but it's basically a replacement for stuff including DWORD and is made especially for the 64 bit addressing and also able to hold more information. We also declared the integer 'ValueForReading' to hold the value for ReadProcessMemory (what's below) [code] ReadProcessMemory(ProcessHandle, reinterpret_cast<void*>(FByteAddress), &ValueForReading, sizeof(ValueForReading ), nullptr) [/code] We are basically reading 4ByteAddress' or 0x01182A74's value and storing it in the ValueForReading integer. You may also be un-familiar with nullptr which can also be overloaded, which you can use NULL (which is an integer with the value 0), but sadly if you use an old compiler, you may actually need to use NULL. [code] std::cout << "Value of 4Byte: " << ValueForReading << ".\n"; [/code] Here we actually print ValueForReading's value just to check. Also, the "\n" is an alternative to std::endl or endl. [code] UINT_PTR Offsets[] = {0x4c, 0x3b}; [/code] Here we're defining the offsets of our address (let's pretend we have offsets) and remember to write them in reverse of how they are in cheat engine (bottom to top). [code] WriteProcessMemory(ProcessHandle, reinterpret_cast<void*>(FByteAddress), &Offsets, 2, nullptr); [/code] Here we wrote the value '2' to that address basically, but let's move onto something like writing bytes. [code] WriteProcessMemory(ProcessHandle, reinterpret_cast<void*>(FByteAddress), "/0x90/, 1, nullptr); [/code] Here we wrote a nop which translates into 90 bytes (This shows into the Memory Viewer in Cheat Engine). That is where you will get your bytes from. I won't go too much into detail on Assembly as it's not what I wanted to focus on. A full code can be found down below. [code] #include <iostream> #include <windows.h> int main(){ SetConsoleTitle(L"djihjninjinjmu"); HWND Window = FindWindow(NULL, L"csgo"); if (!Window){ return 0; } else{ DWORD pID; GetWindowThreadProcessId(Window, &pID); HANDLE Hproc = OpenProcess(PROCESS_ALL_ACCESS, FALSE, pID); if(!Hproc){ return 0; } else{ std::cout << "Press F3 to activate.\n"; for(; { if(GetAsyncKeyState(VK_F3)){ float Crosshair; UINT_PTR CrosshairAddress = 0x44ABC04; UINT_PTR Shoot = 0x5C4BB; ReadProcessMemory(Hproc, reinterpret_cast<void*>(CrosshairAddress), &Crosshair, sizeof(Crosshair), nullptr); if(Crosshair == 0){ WriteProcessMemory(Hproc, reinterpret_cast<void*>(Shoot), "0x32/0x8B/0x90/0x20/0x01/", 5, nullptr); //This writes a special asm code that makes it shoot (it's just like changing its value from 0 to 1 but I preffer using this) } else if(Crosshair == 1){ WriteProcessMemory(Hproc, reinterpret_cast<void*>(Shoot), "0x32/0x8B/0x90/ [/code]

next time man you will be ready

you can download the free version by sliding the screen

i was working on one too lol

good job

good job

yes sir

Prize: Spotify PREMIUM Account 3 Months 3 WINNERS Instructions: Rep+Comment down below for an entry. - 2 weeks old member -20 minimum posts End date/time: 1 Week from now (12/21/2016) WINNERS WILL BE GIVEN AN ACCOUNT WITH 3 MONTH OF SPOTIFY GOOD LUCK

asuhh dude

test

t

check

t

test

k

test

test

test

test