mouse_event is deprecated, use SendInput instead. (lol doesn't matter much anyway) 
Lobby? What are you talking about? Why did you set dwExtraInfo to 1? Just leave it to 0. 
One more thing, you need to set the MOUSEEVENTF_ABSOLUTE flag aswell:
[highlight=vb.net]Public Const MOUSEEVENTF_ABSOLUTE As Integer = &H8000
Public Const MOUSEEVENTF_LEFTDOWN As Integer = &H2
Public Const MOUSEEVENTF_LEFTUP As Integer = &H4
Private Sub DoCrap()
mouse_event(MOUSEEVENTF_LEFTDOWN Or MOUSEEVENTF_ABSOLUTE, 0, 0, 0, 0)
Sleep((Rnd() * 50) * 100) 'Shouldn't you be using Threading.Thread.Sleep(number) instead?
mouse_event(MOUSEEVENTF_LEFTUP Or MOUSEEVENTF_ABSOLUTE, 0, 0, 0, 0)
End Sub[/highlight]
Originally Posted by MOUSEEVENTF_ABSOLUTE
http://msdn.microsoft.com/en-us/libr...(v=VS.85).aspx
Lobby? What are you talking about? Why did you set dwExtraInfo to 1? Just leave it to 0.
An additional value associated with the mouse event. An application calls GetMessageExtraInfo to obtain this extra information.
[highlight=vb.net]Public Const MOUSEEVENTF_ABSOLUTE As Integer = &H8000
Public Const MOUSEEVENTF_LEFTDOWN As Integer = &H2
Public Const MOUSEEVENTF_LEFTUP As Integer = &H4
Private Sub DoCrap()
mouse_event(MOUSEEVENTF_LEFTDOWN Or MOUSEEVENTF_ABSOLUTE, 0, 0, 0, 0)
Sleep((Rnd() * 50) * 100) 'Shouldn't you be using Threading.Thread.Sleep(number) instead?
mouse_event(MOUSEEVENTF_LEFTUP Or MOUSEEVENTF_ABSOLUTE, 0, 0, 0, 0)
End Sub[/highlight]
Originally Posted by MOUSEEVENTF_ABSOLUTE
The dx and dy parameters contain normalized absolute coordinates. If not set, those parameters contain relative data: the change in position since the last reported position. This flag can be set, or not set, regardless of what kind of mouse or mouse-like device, if any, is connected to the system. For further information about relative mouse motion, see the following Remarks section.
