DirectX Overlay Menu (ComplX Multihack)

[ImWhacky]

Ok so i said that i was going to be releasing the source code to my menu in this thread. So here it is
Image

Requirements
DirectX 9 SDK (June 2010) - check here
Knowledge of c++
C++ IDE
Dank Memes
Q&A
Q: Why U Release This?
A: @Hunter is my dad and he thinks my gui is sexy
Q: How 2 Use?
A: Learn C++

Virus Scans
https://www.virustotal.com/en/file/f...is/1464162115/
https://virusscan.jotti.org/en-US/fi...job/1jvvpak6uv

[diamondcoding]

Very cool, hopefully not to many C&P.

[Hunter]

So I have a new son. Welcome to the family.

/Approved. Post back results and as always, use at your own risk.

[iTzCode]

Good worke !

[ImWhacky]

Very cool, hopefully not to many C&P.

This menu was made using grab's external base only. I made some custom directx drawings and every part of the menu is made 100% by me from scratch

- - - Updated - - -

So I have a new son. Welcome to the family.

/Approved. Post back results and as always, use at your own risk.

Thanks dad //2short

[F4DE]

Thanks for sharing! Design looks awesome, clean / modern

[ImWhacky]

Thanks for sharing! Design looks awesome, clean / modern

No problem

[diamondcoding]

This menu was made using grab's external base only. I made some custom directx drawings and every part of the menu is made 100% by me from scratch

- - - Updated - - -



Thanks dad //2short

Not C&P from you good sir. I mean people leeching your source. The menu is clean and sexy. The source is clean as well.

[ImWhacky]

Not C&P from you good sir. I mean people leeching your source. The menu is clean and sexy. The source is clean as well.

Ah, well Idc if they copy pasta, that's what the source is for. Hopefully they credit me and grab tho if they do use it to make it public

[Yemiez]

Some thoughts...

First of all, I don't see you freeing/releasing your data, nor do you check for D3D device losses.

The only part in this entire project that is C++ style is DirectX, which isn't even yours, really start using OOP (Your code looks like it was written in C...).

Some improvements...
You use GetAsyncKeyState/GetCursorPos when you could just grab the events that are sent to the WindowProc, you are wasting alot of resources and cpu loops doing this.

Do you know why classes exist?
So you dont have to write this youself for every single item or such, this just looks horrible and is close to unreadable..

 

if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 76 && p.y < menuy + 96))
				{
					TeamCRed = true;
					TeamCGreen = false;
					TeamCBlue = false;
					TeamCYellow = false;
					TeamCOrange = false;
					TeamCPurple = false;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 96 && p.y < menuy + 116))
				{
					TeamCGreen = true;
					TeamCRed = false;
					TeamCBlue = false;
					TeamCYellow = false;
					TeamCOrange = false;
					TeamCPurple = false;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 116 && p.y < menuy + 136))
				{
					TeamCRed = false;
					TeamCGreen = false;
					TeamCBlue = true;
					TeamCYellow = false;
					TeamCOrange = false;
					TeamCPurple = false;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 136 && p.y < menuy + 156))
				{
					TeamCRed = false;
					TeamCGreen = false;
					TeamCBlue = false;
					TeamCYellow = true;
					TeamCOrange = false;
					TeamCPurple = false;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 156 && p.y < menuy + 176))
				{
					TeamCRed = false;
					TeamCGreen = false;
					TeamCBlue = false;
					TeamCYellow = false;
					TeamCOrange = true;
					TeamCPurple = false;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 176 && p.y < menuy + 196))
				{
					TeamCRed = false;
					TeamCGreen = false;
					TeamCBlue = false;
					TeamCYellow = false;
					TeamCOrange = false;
					TeamCPurple = true;
					TeamCWhite = false;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
				if ((p.x > menux + 11 && p.x < menux + 80) && (p.y > menuy + 196 && p.y < menuy + 216))
				{
					TeamCRed = false;
					TeamCGreen = false;
					TeamCBlue = false;
					TeamCYellow = false;
					TeamCOrange = false;
					TeamCPurple = false;
					TeamCWhite = true;
					TeamCMint = false;
					TeamCSkyBlue = false;
					TeamCHotPink = false;
				}
[...]

Second of all, your use of rand concerns me.

rand() is considered harmful, use the standards implementation which will actually distribute numbers correctly, using modulus for distribution is bad, it's extremely simple to use std's rand implementation:

std::random_device seedgen; // random_device is expensive to call, but it generates a random seed. (You dont nnecessarily need it)
std::mt19937 engine{ /* Input the seed here, you can use random_device or a static seed */ seedgen() };
std::uniform_int_distribution<short> distrib{ 1, 255 };

// now just call the distrib function passing the engine when you wanna generate a number
auto rand = distrib( engine );

// ALSO VERY IMPORTANT:
// random_device and mt19937 are COSTLY to construct, only construct them once.

Offsets.h is bad, you do not want to create global variables like that, use extern and initialize them in a source file, otherwise if you include them in multiple source files there will be a collision in symbol names.

[SpyLegion]

Nice copy pasta

[ImWhacky]

Nice copy pasta

lol, its not copy pasta i made it myself

[SpyLegion]

jkjk, take it easy boy

[Napalony]

Not working ;/