Simple autoclicker

My friend asked me to make him a simple auto clicker(always the same coordinate) for some game he plays. This is what I have so far:

Code:

---

#include <windows.h>

int main(void)
{
        HWND window = FindWindow(NULL, "RSCEmulation V6");
        for(;;)
        {
                SendMessage(window, WM_LBUTTONDOWN, , MK_LBUTTON);
        }
        return 0;
}

---

Is the code, besides the missing argument, I already have ok? How do you turn the coordinate (256, 245) into an integer with the low word as X and the high word as Y?

Thanks

Quote:

---

Originally Posted by Aparavoid

How do you turn the coordinate (256, 245) into an integer with the low word as X and the high word as Y?

---

Code:

---

DWORD val = ( y << 16 ) | x;

---

Quote:

---

Originally Posted by brewbuck

Code:

---

DWORD val = ( y << 16 ) | x;

---

---

Thank you brewbuck that works well. The only problem now is the location of the mouse event follows the actual mouse instead of the third argument which is now ( 245 << 16 ) | 256.

Quote:

---

Originally Posted by Aparavoid

Thank you brewbuck that works well. The only problem now is the location of the mouse event follows the actual mouse instead of the third argument which is now ( 245 << 16 ) | 256.

---

How are you testing it? In the game itself?

I found the problem. The 3rd and 4th arguments were switched. Thanks for the help.

Quote:

---

Originally Posted by Aparavoid

I found the problem. The 3rd and 4th arguments were switched. Thanks for the help.

---

How disappointing :) I was going to speculate that the game had some anti-hacking built into it to prevent this kind of auto clicking. (It's not hard, you just ignore the coordinates in the event and query the mouse position directly, which forces the autoclicker to actually move the mouse pointer, which would probably disrupt game play)

You can also use the macros

MAKEWPARAM()
MAKELPARAM()

and the reverse

HIWORD()
LOWORD()

Quote:

---

Originally Posted by brewbuck

How disappointing :) I was going to speculate that the game had some anti-hacking built into it to prevent this kind of auto clicking. (It's not hard, you just ignore the coordinates in the event and query the mouse position directly, which forces the autoclicker to actually move the mouse pointer, which would probably disrupt game play)

---

Read the mouse coordinates before you move it, move it, click then move it back. Or just directly inject the WM_ messages into the application queue. Checkign current mouse coords wouldn't work as its possible the mouse has moved since the click was made.

Depending on app structure, InSendMessage() can be used to filter external msgs.

Quote:

---

Originally Posted by abachler

Or just directly inject the WM_ messages into the application queue.

---

SendMessage() is nonqueued, so faster and more reliable.

Using PostMessage() would require more checking for a game (as it's msg queue may be full most of the time, causing PostMessage() to fail),