Best method for external GUI

What is the most perficient method of creating a external gui for my cheat. My code is written in C++ and I would like not to change that. Create a GUI in VB then use a DLL to call code?

Any suggestions?

Many thanks,
Buttars<3

Originally Posted by Buttars0070

What is the most perficient method of creating a external gui for my cheat. My code is written in C++ and I would like not to change that. Create a GUI in VB then use a DLL to call code?

Any suggestions?

Many thanks,
Buttars<3

Hello I recently had the same problem as all my code was written in c++ and I wanted something that I could simply add to my code rather than change everything that was already there. Qt makes you move your stuff from std types to Qt types, most of the other libraries kill std::thread. I ended up using a library called nana and it works great. Keep in mind there is no easy-mode editor like you'll find with Qt, and I ended up with 2000+ lines of code specifically for gui for my cheat. Another alternative I looked at was CEGUI. CEGUI does have an editor. Another suggestion I seen was JUCE. Hope one of these does what you want.

You can use dx framework, create a overlayed window and then initialize a dx::Window instance with the HWND.

I created a simple editor for dx framework, it can be found here.

Preview:

Originally Posted by Yemiez

You can use dx framework, create a overlayed window and then initialize a dx::Window instance with the HWND.

I created a simple editor for dx framework, it can be found here.

Preview:

Wow looks good. Does it work in full screen?

Originally Posted by Yemiez

You can use dx framework, create a overlayed window and then initialize a dx::Window instance with the HWND.

I created a simple editor for dx framework, it can be found here.

Preview:

Looks great, could you answer goochguys question, does it work fullscreen? Thanks for such a damn good response though :P

Originally Posted by Buttars0070

Looks great, could you answer goochguys question, does it work fullscreen? Thanks for such a damn good response though :P

Originally Posted by goochguy

Wow looks good. Does it work in full screen?

It depends on the implementation, the developer can create a base class of dx::BasePainter, that way they can possibly use something like the engine renderer, hence working however you'd want it.

The only thing that is default available is a normal window and a DirectX9 renderer, you'd have to create the window using dx::Window and retrieve the native_handle and use WINAPI calls to modify the handle to have a transparency key/layered. (Would only work if csgo is in Fullscreen windowed)

Why no just go internal hook PaintTraverse and ez win ez lyfe???? Why does everyone think internal is so much harder... It's not lmao

Originally Posted by d4rkW

Why no just go internal hook PaintTraverse and ez win ez lyfe???? Why does everyone think internal is so much harder... It's not lmao

I just like working externally, I've made internal cheats but find it far more fun to create external hacks. Well I used to, I dont make cheats nowadays.

Originally Posted by Yemiez

I just like working externally, I've made internal cheats but find it far more fun to create external hacks. Well I used to, I dont make cheats nowadays.

It was directing my message toward the OP, but i got you :P I, on the other hand, prefer to make internals as imo injecting code is much more sexy

Originally Posted by d4rkW

It was directing my message toward the OP, but i got you :P I, on the other hand, prefer to make internals as imo injecting code is much more sexy

I don't think it's necessarily harder, there are just more sources, examples, support, community, ext. for external. Internal is definitely the way to go although I enjoy external for it's simplicity.

Originally Posted by Buttars0070

I don't think it's necessarily harder, there are just more sources, examples, support, community, ext. for external. Internal is definitely the way to go although I enjoy external for it's simplicity.

Its simple since you can just copy and paste memory classes and other code that have been posted.

Injecting your DLL gives you direct memory access, without any necessary code. You can literally inject your DLL and access a pointer inside your Dll_Main, where external you'd have to iterate through the processes first, grab a handle to the process you want with the rights you need, create a wrapper ( not necessary ) for ReadProcessMemory / WriteProcessMemory.

All you have to do to read an address internally is written in one line, where you need much more code to even be able to read one address externally. And the logic is the same externally as internally.

Using engine functions is a whole different topic.

Originally Posted by kenuking83

ikr all the skids can't reverse shit dude.

Add something useful or leave the thread dude, no one is here to complain about people trying to learn. Get some respect and either add to the thread or show yourself out.

@WasserEsser, If you would like too PM me and help me out with getting base concepts (differences) with coding externally, I'm open to learn (and won't just ask for c+p ;D)

If you don't know how to help the OP out with the issue he's facing, then don't bother posting in this thread in the first place. Thanks.

1 week has passed and no further replies have been made by the OP. Assuming solved.

/Closed.

Best method for external GUI

Similar Threads

Tags for this Thread